steve_v

When the adjustments make the broken behaviour slightly less broken but fail to fix it, it's a bug. Wheels have been a disaster since 1.1, and adding knobs hasn't fixed anything, just introduced more variables. There are more, of course there are more. The bugs I mentioned are only those I personally encountered in the first half-hour or so after spinning up 1.9.0, without even going to space. If I spot them that quickly without actively trying to find bugs, what kind of testing is Squad doing?

Manoeuvre node editor is broken, graphics are borked on GNU/Linux, wheels are as bad as they ever were, kerbals randomly remove their helmets or phase into terrain and die, scatterer/eve/restock/texturereplacer/etc. still beat squad's visual overhauls. Performance I like, visuals I don't care much about, and enough new bugs and regressions can overshadow any improvement. 1.4-1.7.3 I wasn't going to touch, because a cheeseburger (spaceflight sim) with no cheese (joystick support) is simply not a thing. I went elsewhere instead (X4, DOS2). 1.8.0 got the basics right (joystick support fixed), but added several dead mice (e.g. fairing occlusion again, various ridiculous new ways to kill kerbals), a clump of hair (extreme message spam), and dyed the whole thing a nasty shade of puce (opengl borked again). Thinking I'd finally got what I ordered, I took one look in the bag... and gave it to my dog. The dog didn't want it either. 1.8.1 removed the hair and the largest of the mice, but kept the colouring. It's edible, and it actually tastes okay... It just looks like vomit and gets a bit crunchy now and then. I'm not hungry any more, but I'm not exactly writing up a rave review either. 1.9.0 added one enormous rat, no extra charge (node editing borkage). Just no. That's one too many vermin in my dinner. Oh, and through all this wheels are still bung as a bung thing. Did I mention the wheels? My thoughts exactly. I thought 1.8.1 was close, and 1.8.2 might be the one... then they blew it. Again. Just like last time we got close to a properly playable infuriation-free release.

I'm pretty sure nothing on the bugtracker means anything any more. Squad seems to have stopped caring a while back and be looking at only DLC problems and extremely low-hanging fruit.

I know. Had I known back in 2013, I wouldn't have bought the game. I won't be buying anything else from them until this improves. Squad advertised their product as running on GNU/Linux, and GNU/Linux as a supported platform. It is quite reasonable to expect them to honour such statements. It may be better for us to reserve our financial support for game studios that actually give a monkeys about their customers and their product quality. I don't pay for games so buggy I have to run them through an API compatibility layer.

Is from KSP 1.3.1, and Is from KSP 1.8.1. I'm going to assume only the second one is applicable. Indubitably. Checking that all your mods are compatible before updating the game is a whole lot more your job than mine though. I did check a few, and most of them were either horribly out of date or not compatible with KSP 1.8.1. Expect to encounter all kinds of borkage in-game until you sort this out. I suggest using CKAN. A cursory grep of your logfile indicates that scatterer, textures unlimited, b9partswitch and planetshine are all throwing exceptions. The latter is the most likely to interfere with the GUI and/or camera system as you describe, but I doubt it's the only problem you have.

Here you go. Read, then report back with log file. My crystal ball is away for polishing right now, so unless you list the mods you have installed and their versions I'm going to have great difficulty telling you anything.

That looks very much like a broken scatterer install. Scatterer is not currently compatible with 1.9.0. Stock bug #24840. IMO this one is pretty gamebreaking, so I am still running 1.8.1. 1) Read the sticky and link your log file. 2) Don't update the game (or let steam update the game) until you have checked that all your mods are compatible. 3) "I've removed my visual mods" means absolutely nothing to me unless you specify exactly what constitutes a "visual" mod. Better to just list the mods you do have installed (with versions), as the sticky suggests.

To cover the basics first: Are we talking about an input lock here, and if so, who grabbed it? You'd be looking for this tab in the debug window (Alt/RShift + F12), here showing an input lock from "DebugToolbar" because the mouse is over the debug window itself: Aside, that doesn't look like a complete log to me. IIRC dpaste has a limit somewhere around 250KB, KSP logs often run to 10MB+ so it might be wise to upload them to a real filehost rather than a pastebin.

Indeed, with 1.8.0. Which is to say: Waited for unity to fix it.

Uhh, what? 1.9 you say? What happened to 1.8.2? Bugs from the last major release still not fixed? New parts horribly broken? New bugs introduced? Yawn. Unexciting. Art is nice, really annoying bugs are not.

There's only one ModuleCommand here AFAIK, and so there should be only one MechJeb module. Possibly, insofar as debris is inactive.

Sure.

Well, waiting for notepadqq to compile only to find that it doesn't have plugin support was rather disappointing... And running notepad++ in wine is hardly deserving of (Linux) in the title... or something I'm going to do. Oh well, it looked kinda handy. Nevermind then.

Well whaddya know... No icons even without symlink silliness. Became a little caught up in another mod that was borking on symlinks, so kinda assumed that would have something to do with it. More coffee would undoubtedly have helped with the trying of obvious things too, but I obviously didn't think of that either. Of course. I think this one is yours after all.

As I see both problems in that reddit post you linked, I think at this point we can say that both this one and yours are nothing to do with GPU drivers. IME they're likely just another borked GNU/Linux build from @SQUAD, the undisputed champions of QA testing and bugtracker management. These people either don't test or simply don't care, GNU/Linux release quality went right down the crapper as soon as 1.0 was out.

I suspect the same. You are running an Nvidia card with the proprietary drivers, right?

No, but I see it too. Logsnip system info: OS: Linux 4.19 Gentoo 2.6 64bit CPU: Intel(R) Core(TM) i7-4960X CPU @ 3.60GHz (6) RAM: 32064 GPU: GeForce GTX 1070/PCIe/SSE2 (8192MB) SM: 50 (OpenGL 4.5.0 NVIDIA 440.44) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGB64, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8, ARGBInt, RGInt, RInt, BGRA32, RGB111110Float, RG32, RGBAUShort, RG16, BGRA10101010_XR, BGR101010_XR, R16 ^^ Bug report posted.

Yup.

Hey @linuxgurugamer, I have some QuickFeedback for QuickSearch 3.3.0.7, in that I have no icons appearing on the search buttons in R&D. Everything else (toolbar etc.) is okay. I see you changed the way relative paths are determined in this release, my guess is it's no longer cooperating with my slightly unusual setup, namely where GameData is a symlink managed by a silly little launcher I wrote: Then again, it may have nothing to do with it. Just guessing. Player.log No biggie, just a heads-up, I can deal with missing icons.

Just in case you're you're talking to me, "bud", I think I should perhaps point out the presence of "Kerbal Space Program - 1.8.1.2694 (LinuxPlayer) en-us" and "OS: Linux 4.19 Gentoo 2.6 64bit" in that there log snippet I posted... As I appear to be running Gentoo GNU/Linux, I find it highly improbable that I would have a Windows crash dump to post, an "AppData" directory anywhere, or use "\" as a directory delimiter. That post was intended only as an indication for whoever is looking into this that it may not be platform specific, and as another data-point if someone wants to try to cross-reference installed mods. I haven't investigated any further or tried to get a backtrace as yet.

Erm: There be no GNU/Linux builds at that URL...

Uhh, guys, I'd kinda prefer suggestions over likes... Not trying to be ungrateful or anything, but this all has gone and upped the reply counter on this thread without adding any useful information.

That's very hospitable of you @Vanamonde I must admit I'm getting a little irritated by the lack of progress on this one, and I may have taken some of that out on the poster of the first, only, and not very useful reply. Do you have any idea what's going on here? The bug report has been open for 3 months now, and there's been nothing useful there either, bar a single uninformed and unhelpful "try turning it of and on again". This is clearly a regression in 1.8.x, and there's at least one other person experiencing it... The lack of any interesting comments whatsoever is beginning to chafe a little.

While I am no expert on the matter, I do know what a shader is. This is fairly obvious, is it not? I see that you are new here, and that's cool... But your response reads like something intended for a five year old. As you may see by hovering over my username, I have been on this forum for some ~6.5 years. That would make me at least seven, and even if I had not already been aware of the things you explained above, I could easily have discovered them by spending a few minutes with a search engine. The questions here are two: a) Is this new ugliness introduced with 1.8.x related to the message regarding an incompatible shader. b) How do I fix it. Do you have any light to shed on these questions?

It's tolerated though, and even quietly endorsed. I don't see the moderators stepping in to say "please DBAD" when a mod author kicks up a massive fuss over someone exercising the rights granted to them by the licence. I do see moderators making comments along the lines of "don't upset the modders, it's just the culture here" and repeatedly appealing to people to ask nicely or wait months for an AWOL author to okay their legal and perfectly reasonable interim release or fork. Anywhere else FOSS development takes place, an author who kicked up such a fuss about someone forking their code (or threatened to change the licence to spite people) would be immediately dogpiled by most of the forum, and find many of their users moving to the forked version just to show their disapproval of such a petty, possessive and backwards attitude. Yes, having multiple versions floating about can create support problems, but if you want to play the open-source game that's just what you have to deal with. Anything else is the proverbial having your cake and eating it too. In the case of the @R-T-B saga, at least one of the mods he forked was released under the GPL, a licence specifically designed to encourage forks and modifications. In this weird place it seems that certain people, mods included, are so keen to keep their army of unpaid developers on-task that they'll back them up even when they go entirely against both the letter and the spirit of the licence they chose. Sure, it's polite to ask. It's also polite to reply with "of course, that's why I licenced it GPL" (or any of the other open licences people are using). There seems to be a bit of a disconnect as to which part of that you are backing here... In fact it's almost as if you are granting certain users of the platform special being-impolite privileges.