steve_v

I know plenty of people still running 1.3.1. For myself, I'd really just like to be able to enjoy the game I backed in alpha, with both of the DLCs I purchased, with my HOTAS, and without a bunch of ridiculous bugs. <1.6.x has no Breaking Ground. I'd like to play the DLC I bought. 1.4.x - 1.7.x has broken joystick support. I fly planes a lot, and I want the functionality the game used to have to actually work. 1.8.x fixed joystick support, but settings are reset every time you start the game and the atmosphere shaders are all screwed up. 1.9.x fixed the atmo, but didn't fix settings not applying. It also introduced various exotic mod-borking bugs relating to prefab resources and symmetry. 1.10.x still didn't fix settings not applying, and additionally borked resource transfer. All of the above still have craft sliding around, wheels bouncing all over the place, parts displacing on restarting the game, and other ancient and infuriating bugs to numerous to list. So, which release of this lovely, polished, not at all perpetual-beta game should I play? Should I wait for the next release, get all my mods sorted out, then discover there's yet another new and idiotic regression? Oh, the suspense, what will be broken this time?

Uhh, yeah... Good luck with that. KSPs performance scales rather badly with single-vessel part count. It's not magical, it's the single-threaded Unity PhysX implementation doing rigidbody physics on the CPU. Your framerate goes up when paused because physics is paused, and your CPU usage also rises because the parts of the game that are multithreaded are no longer waiting on it.

It would, wouldn't it.

Oh, I get that. It's the nested /KSP_x64_Data/KSP_x64_Data, /KSP_Data/KSP_Data, /Music/Music and /Playlists/Playlists, along with 4 copies of the mpeg decoder library and 2 copies of the playlist and every audio file that I'm wondering about. The files are identical, and the 1.7.x release archive contains exactly half as many copies of everything... Surely that much duplication isn't necessary?

I "held in there" all the way from 1.4 to 1.8 waiting for them to fix the input regressions, only to find they'd gone and broken another piece of basic application functionality, namely the ability to save and apply graphics settings, of all ridiculous things. Were now at 1.10.1, and It's still not fixed. This isn't a "pet bug", it's being systematically treated like a third-class citizen and left to put up with a broken product for purchasing the game on one of the officially supported platforms. It's the same crap treatment console customers keep getting, and it's simply not good enough. These are not obscure corner cases, and they're not third-party porting problems. They're regressions in basic functionality that Squad completely ignores, in the last case for over a year and a half, while releasing multiple major content updates. The fuel transfer regression is another matter (largely because it's a new regression), and you'd be hard pressed to play the game for any length of time on any platform and not be screwed over by it. It's not just a minor irritant either, and releasing a hotfix that doesn't even try to address that one is properly incomprehensible.

Check the last few pages of the relevant release thread on the forum, someone always asks... Or try it yourself, test out all the functionality and look for any exceptions in your log, then if everything looks good you can be that helpful person who posts in the release thread that it appears to still work. Parts only mods are usually fine through many KSP releases. KSP 1.8.0 - 1.10.1 all run on the same unity version, so plugins should at least load without needing to be recompiled. As for functionality, the bigger the gap the more likely the problems. The vast majority of mods for 1.10.0 should work fine on 1.10.1. In the case of 1.9.x vs 1.10.x, again, most mods are okay. Mods with fairings are a notable exception. 1.8.x mods on 1.10.x gets a little more sketchy, so you'll want to do some testing on a throwaway save, or at least make a backup.

@linuxgurugamer Bumping this one, as it makes things kinda confusing to install: The 1.8.x archive sure looks like it has duplicated directory structure to me: The 1.7.x archive doesn't include those duplicates, and it's ~1/2 the size... Presumably this is a packaging error?

So do I, I'd just much rather have working fuel transfer and settings that actually set. All three of those things need programmer hours, no prizes for guessing which ones I'd like to see them spent on.

It's free for personal use, and that's all you need. You'll want version 2019.2.2f1, as that's what the current game version was built with.

Lol. We've been asking for a bugfix-only no-new-stuff release for years. What we get, every single time, is a release with a bunch of SNS and a bunch of new bugs, a hotfix or two that almost but not quite get it into a reasonable state, then silence until the next major release full of unasked-for new stuff and more new bugs. So throw some new textures in there if that's what needs to happen, just don't introduce broken new features, and don't break existing ones. Put the programmers on the bugs, not implementing half-baked new mechanics or facilitating glow in the dark suits. The only reason people ask for a buxfix release is because major releases have been, for several years now, consistently introducing as many (or more) bugs as they fix. Stop dropping obviously broken and inadequately tested .0 releases and stop walking away from regressions (fuel transfer anyone?) to wait for more shiny content, and people will stop asking. When we say "stop with the new stuff, just fix the bugs", what we mean is "bugs clearly aren't getting the priority we think they should, please focus on them". That's with the unwritten assumption that Squad actually has competent programmers who could fix the bugs, but are being diverted to other things or rushed into introducing technical debt. If that diversion is supporting some other aspect of the team, then somebody needs to look closely at the composition of their workforce and the tasks they are being assigned to, because product quality is suffering for it. If there truly is a lack of manpower or time, then releases need to be delayed until they can be tested and the bugs fixed. It's not rocket science, it's project management. Game settings have not applied properly on startup on GNU/Linux since 1.7.3, and joystick support was broken for a similarly ludicrous length of time. Fuel transfer looks like it isn't going to be fixed before the next major release, despite it being a longstanding and much-used core feature. Is this situation because "not all the devs are programmers" too? It seems to me far more likely someone cares more about shiny new stuff than about fixing regressions, but then I can only judge from what I see, no? What I see is comets, which nobody asked for, old bugs going unfixed, and new bugs now also going unfixed.

You might want to make it a little more obvious with a smiley or summat next time... Tone doesn't translate to text well, especially for those who don't speak English natively.

This ^. Also customer reviews are pretty worthless in general, particularly the mindless "good price works good" ones that tend to push ratings up. Prebuilt and PSU are two words that make me cringe when found in the same sentence. Off the shelf PC builders have a long history of installing the cheapest nastiest PSUs they can find. A good 400W PSU will be fine. A cheap "400W*" PSU won't. I've never heard of "Apex Gaming", so I won't comment on that particular unit. I can't find any teardowns or any information on the OEM either (ed. probably Solytech, yuck). Personally, I wouldn't trust it anywhere near as far as I could throw it. If you're buying a PSU, find a real review by someone with a proper test rig and some electrical engineering knowledge. Like this guy for example. If they didn't take it apart and they didn't post any scope captures or put it in a hot box, the "review" is worthless. Don't cheap out, and don't judge anything by the shiny box or RGB fans, it's the design and build quality of the (usually made by someone other than the name on the box) board inside that matters. The return on that higher price tag is that a good quality PSU will last you many, many years, whereas a cheap one might cost you a motherboard when it dies, or even a house. FWIW, I have personally experienced a PSU fire... As in proper flames. As in crispy fried PCB and copious smoke. Smoke alarms at 4am and all that jazz. It was a 4 year old lightly-loaded 750W from a well known name brand, a brand I had had excellent reliability from in the past... But they "refreshed" their line and switched from Delta internals to some unknown Chinese crap, and they did it quietly. Shame on me for making assumptions based on box brand, I was in a hurry when I bought it and didn't follow my own advice... And it was suspiciously cheap.

T2 EULA is irrelevant for original material they have no claim to, and that includes most KSP mods. Licencing of mod code and assets is largely at the discretion of the author. "Stolen" is an emotional translation of "copyright infringement". If the mods licence allows redistribution and that redistribution happens in compliance with the licence terms, then there's no problem. If it doesn't then it's copyright infringement, plain and simple. There are apparently special extra "rules" restricting perfectly-legal redistribution and forking on this forum, but those don't matter whatsoever anywhere else.

Biplanes work fine at low speed, but they suck camel-balls if you're trying to break the sound barrier. Even if you could get one up to such speed without it tearing itself apart, the drag would be horrendous. There is a theoretical design floating about somewhere, but IIRC nobody has actually built one. In KSP it doesn't matter in the slightest, since stock aero models neither supersonic wave drag nor wing interaction. For that you need FAR. All stock does is add a magic drag-multiplier at the sound barrier. TBH this is probably the thing that annoys me most about the games aero model - there's no penalty for stacking wings, or even clipping them inside other parts. There's also no area ruling, no shockwave modelling, no drag occlusion for anything but cargobays and fairings, and a ludicrously forgiving stall mechanic. Even horribly unrealistic designs (like WW1-esque biplanes) can reach hypersonic speeds in KSP, and many realistic ones fly like bricks due to counter-intuitive artefacts of the simplified drag system like the uber-drag from open nodes.

Yeah, zippyshare is pretty nasty. It's more manageable with a good adblocker, but still. I grabbed the file earlier, here's a non-horrible link.

The only solution I would go near, at least for debugging purposes, is to disable RTSS altogether. Once you know whether or not it's causing the problem, then you can try mitigating it.

Indeed. I'd consider dropping a 3 ton (really? why?) rover on Eve with a parachute, but a large ISRU, a big cargobay with a fat-ass rover, robotics, multiple engine types, all in an Eve SSTO spaceplane when you're new to planes in general? It's basically self-flagellation. Most people consider it an achievement to get off Eve at all, let alone hauling that amount of junk.

Looks to me like DangIt! is having a very bad time. Remove it and see if your problems go away. If they do, congratulations, you've found a bug. Go annoy @linuxgurugamer about it in the Dangit! thread. If not, remove it anyway and link a fresh log. Miscellaneous self-help advice: Searching your log for the word "exception" will often identify a problem mod, or at least give you a starting point to narrow it down. In this case Dangit was the last to do something before it all exploded, so that's where we start. Always link a log. Link it in your very first post, and we won't have to waste time asking for it. If it's huge, compress it, preferably with 7zip. Zippyshare is an obnoxious hellhole. Dropbox and google drive are less so. Youtube videos, imgur albums and most offsite images embed in the forum automatically. You want the direct link to the image file for the latter. Checking "show all log exceptions on screen" in the games debug window (mod-f12) will alert you to borkage on the fly, possibly even before it ruins your day. So will ExceptionDetector, only with more detail. KSP.log contains a list of mods installed, assemblies with versions, and directories under gamedata. The CKAN output might be useful for (maybe) more accurate version information, but a screenshot of a folder is both completely redundant and a waste of bandwidth. FTFY. Large walls of text (e.g. logfiles) pasted into the forum make it extremely slow, especially on mobile. The joys of this "reactive" javascript-infested modern website design we apparently have to put up with. This is why we ask people to use a filehost.

Possibly a long shot, but: Has been known to crash KSP. It's kinda old advice, but may still be relevant. The same goes for anything else that hooks the graphics stack.

That's a Windows username. If one is sensitive about one's name, one shouldn't use it as a username or login... But then why would one be, there are likely thousands of other people with the same. ¯\_(ツ)_/¯ MiniAVC -> Executing: MiniAVC - 1.3.0.3 Again? Really? Nuke that thing from orbit, then try again.

LF2... *shudder*

They're not gone, they're just hidden. Unhiding them again with Modulemanager is trivial.

Here. Pretty much the same as ever: fly station, undock lander, land, eva, launch & return to physics range of station, splat. A save/reload before entering physics range seems to prevent it, at least until the next landing. Switching craft clears it up post-bork too. Ed. So far, only happening if there are kerbals on both craft when returning.

Only by your exacting standards, maker of pretty things. From a player perspective, and compared to the stock offerings of the time (sans ReStock), they were glorious.

Cool, which virus was it? ...Or did you just assume "virus" because your browser/OS said "untrusted file/site"... Yeah... Sounds like his mouse just slipped onto the download button, those things have a mind of their own. To be fair though, I occasionally download uber-suspicious things so I can spin up a disposable VM and see what's in them, for "research". Viruses are pretty interesting things. FTFY. People do things for all sorts of reasons, and it'd be both pointless and extremely time-consuming to try and explain all the reasons people might pirate games. A better question might be: Why do people make drama out of finding yet another pirated copy of the game for download, instead of just quietly PMing a moderator?