DeliriumTrigger

Despite the small inconvenience of waiting, I'd prefer to have it done right instead of having it done right now. So thanks for putting in the work to eliminate all of those annoying bugs that make troubleshooting a new modded install such a pain in the rear. I'm glad these bugs are being caught in testing instead of out in the wild. Edit: Just realized I'm not in the Kopernicus thread. And I don't know how to delete a post. Ah well, sentiment stands.

Did you ever find a solution for this problem? I'm encountering the same issue. Works fine under DX9, but when I try to use -force-opengl or -force-d3d11 everything gets super dark like this. The game is *playable* under DX9 but I'd really love to get it running under DX11 for the reduced memory footprint.

Mod key for Windows is Alt. On Linux it's right Shift. Just replying to save someone the effort of figuring out why Alt doesn't work if they're using Linux :)

I have a feature suggestion, not sure how easy it would be to implement or if it's even possible but if it is I think it will make the tool a bit easier to use. When setting up RCS for translation, there's a large arrow that extends in the opposite direction of the thrust that moves as you rotate the thrust with a smaller stationary arrow that you should align the larger arrow to. My suggestion is to make the larger arrow change colors when it is perfectly aligned. I often find it difficult to get everything just right, especially since the arrows are semi-transparent and it can be difficult to see. Having a color shift to indicate when I've got it just right would be a big help. I'm sure you've got a lot on your plate, but if its possible to do someday when you have the time, that would be wonderful!

I don't think the clouds.cfg edit works anymore. Don't know what changed but I tried it and it doesn't appear to work. Using latest versions of all the same mods as you.

And yet here you are, whining about whining. Funny that.

So because things were bad at the moment they stopped being an early access game, that excuses them dropping the ball now? This isn't an argument. I wasn't here for the 1.0 release and I didn't buy the game in early access. I don't care about how rough it was back then. I said that Squad should release an official fix for the landing leg bugs. Apparently its such a minor issue that they are content to let it be solved by a modulemanager patch, so why shouldn't they release it? I can't tell if you're being willfully obtuse or disingenuous or what. I'm trying to be charitable here. Squad stated that the reason they're holding up the fixes for a bug that impacts a huge portion of the game is because they want to fix some problems with content that doesn't have a huge impact on the core gameplay and isn't even in the game yet. Apparently this is okay with you, and that's fine, but can you really not understand why others might have a problem with that? Why they might be inclined to come on the forums and voice their disapproval? And your answer to that is... well you guys should have been here when the game first left early access. How is that even relevant to now, when they've been bought out by a major publisher and are releasing DLC? I think some people on this forum are so wrapped up in modding and how things were done "back in my day" that they forget that this is a product that is being sold as a finished, released game. There are expectations that come with that. Sitting on a fix for a freaking month so they can work on airfields isn't acceptable anymore. Maybe it is for you. Maybe it is for modders who are too busy worrying about the impact rapid bug fixes would have on their own workload to care about anyone else. Maybe you bought in before it left early access so you're fine with this state of affairs. But some people don't want to spend money on half finished products and provide unpaid labor as QA testers. And frankly I don't care about the impact on modders because I didn't buy mods, I bought a game that was presented as complete, not early access. And it hasn't worked properly for a month. The solution I get from Squad and the people who feel some kind of duty to vigorously defend anything they do is "keep backups, look in the forums for unofficial fixes. Who cares about your time or your hard drive space because we're too busy trying to sell DLC to care about your problem." I know Squad cares about this game and I know that they aren't doing this maliciously. I know software development is difficult. But I refuse to accept that because it's hard, that means paying customers should just accept pee in the face because they tell us its rain. I want them to do better. As far as "fix things now and break something else" I already presented a solution to that. And said solution would have certainly caught this stupid landing leg bug before it made it to the stable release branch, but according to you it's completely unworkable because reasons.

That doesn't even make sense. An overload of complaints that the latest version does not work? Want to point me in the direction of all those complaints for 1.3.1? Do you think releasing exploding landing legs to the entire installed userbase resulted in more or less noise? Why is it my problem again? As opposed to a bunch of unwilling participants and Squad being subjected to the exact same thing anyway because Squad broke everyone's landing legs? The bug tracker has logins. Ban people who abuse it with useless bug reports if efforts to guide them toward utility prove fruitless. This is a moderation issue, and again, not my problem. Why should I care? First, landing legs exploding isn't a minor bug. This is a game where you explore other planets, and a huge part of that is landing on them. Second, you're trying to create a strawman of my argument and it's not appreciated. I don't expect every bug in the game to be dealt with now or else I'm going to scream about it. That's unreasonable and unrealistic. What I'm complaining about is that my game that I paid for was working and is broken now. Not the airfields that aren't in it yet, but the product that I already have. And instead of getting an official fix for the problem, a problem that can apparently be fixed well enough by a simple user applied patch that it was left to linger for a month, we're waiting around for it so that they can work out some final issues with content that isn't even in the game yet. And if you can't respond to people without distorting what they said and throwing in a bunch of snark, maybe you should stop arguing and go take a walk, get some air or something.

No, it's even simpler: Implement future testing procedures that insulate the entire installed user base from the worst bugs by utilizing a public beta/prerelease testing phase after the internal testing is completed. Then crap like this current situation has a much smaller likelihood of happening again. Then when you don't immediately know where a bug is among thousands of lines of code next time around, that's okay because it's a beta/prerelease and you haven't broken the stable release of your customer's already working game. When a bug breaks a core gameplay loop and someone in the forum manages to do your job for you and fix it with a text editor, maybe consider releasing an official patch with that bug fix to all the thousands of users whose game you broke, instead of making people dig for the fix on their own or wait for it while you work on an airfield that isn't even in the game yet

This is at the core of what bothers me about this situation. It's not that it's difficult for me to keep separate installs and work around the bugs. It's that at this point we simply shouldn't have to. This isn't an early access game and while new features are certainly appreciated they should not come at the cost of introducing new bugs to the already established product. They should not be used as an excuse to hold up a major bug fix that is apparently so simple it can be solved with a text editor by users. The problem isn't in the addition of new features/bugs, but in the way they are released to the community at large to deal with until 'soon". There should to be a public beta/prerelease branch where new features/patches are released after the internal/closed testing. The current way is absolutely unacceptable. Expecting every customer - new, veteran, technical or not - to deal with bugs by applying mods, patches for those mods, and keeping multiple copies of KSP on their drives just to ensure that Squad's haphazard release procedures won't break a core gameplay loop is ridiculous. It shows a complete lack of care, concern, or respect for the people who bought this game. I don't care if its hard. Why should I care? Why should I have to dig through forum threads and apply modulemanager patches? What if that's hard for the customers? Squad wants to call their game released and sell DLC, why should they get to sell me a game under false pretenses and then treat me like someone who bought an early access product? Woe is me, coding is difficult, well then put a big banner on your Steam page telling everyone that you're still in early access. Sure, caveat emptor applies but presenting this as a complete product while pulling crap like this - crap that could be avoided - is being willfully misleading. I'd just like to point out, again, that 1.4.2 was released on March 28th. In three more days it will have been a month that the entire installed user base has been waiting for an official fix for exploding landing legs.

Being a machinist is hard too but I don't get to give my customers products that don't meet specification because it's hard. This isn't an early access game, we paid for a finished game and we deserve better. The landing leg bug is game breaking, and if it can be addressed by a work-around then said work around should have been pushed out as a patch instead of making people break out a text editor to do Squad's job for them. I sympathize with their struggle but they don't deserve a pass on this. We can still support the game, be fans of it, and state that this is unequivocally unacceptable. 1.4.2 was released on March 28th. That's nearly a month with a major bug and we're still waiting for a fix.

Even for veteran players, it's still unacceptable. I shouldn't have to keep backup copies of previous versions around and go without using DLC I bought for weeks just to have a playable version of the game. We're not beta testers, we're paying customers. I bought this game after it left early access for a reason, early access sucks and I want no part of it.

Certainly a practical solution but really not acceptable for a game that's supposedly out of early access and selling DLC now. How do I downvote on ksp forums

Yeah they're probably damned if they do and damned if they don't in this case. The idea of having different tech trees available to choose from in the stock game would be nice but I'd bet the chances of that happening fall somewhere between getting a built in dV/TWR readout and friggin never.

I like it over there. It's like the picture book version of the forums. Everyone shares screenshot galleries of their successes and failures, they do a weekly challenge. I imagine the overlap is pretty substantial, but just as you never bother with reddit there are plenty of people who just use reddit as a catch all forum for everything they're interested in and don't venture out very often.

Lol. The pie was pretty yummy before. This is more like the bakery advertising some new DLC cherries to put on top of your pie only to find that they filled the cherries with pubic hair and added nitroglycerin to the pie crust (landing legs).

Well to be fair, there are plenty of people playing this game with mods that don't post here. I had the game for two years and played with mods almost the whole time but only made an account here a few months ago so I could submit a bug report for a mod. The game has a pretty large and active community on reddit so I just never bothered before then.

Three weeks and four days. Almost a month. And apparently the fix is done, but we have to wait so they can fix a new launch site. smdh I don't think anyone here has a problem with them adding new parts. It's mostly the whole rushing the release and introducing a bunch of new bugs in the process that make it so you can't even use the new parts without either dealing with aero and landing leg bugs, reverting to a previous version, or breaking out a text editor and applying a half-assed fix. I happily paid for the DLC because the less mods I have to install and wait for updates for, the better. But it's pretty crappy having all these shiny new parts to play with and not being able to use them in anything but sandbox because I don't want bugs interfering with a career game.

Now for the obligatory question... does KSP djent?

If I pushed out all my forum posts to a grammar prerelease channel would you help test for me? lol

This will probably fall on deaf ears, but it's worth a shot anyway. I am a huge fan of this game and appreciate all the effort that goes into it, including the new content, even if it isn't always stuff I'm interested in. However, objectively the 1.4.x release has been a mess. It's okay, these things happen, but when they do it's a good idea to look at why and how they happened so that they can be avoided in the future. Clearly there is some kind of issue on the testing front that is leading to bugs slipping through. And clearly there is some kind of push to get new content out, which is why the game is in the current state it is in. The problem is that all the new content in the world doesn't mean much of anything if the game is riddled with fairing aero bugs and collider bugs that make it impossible to land on a moon without busting out a text editor. And it's made even worse by the fact that the bulk of this new content is DLC, meaning many of us paid for this content and have serious impediments to actually using it. What I propose is that you create a beta/prerelease channel. Make it available on the website for people who bought it from you directly, or in the betas tab for Steam users. Take advantage of the many members of the community that would be willing to test new builds and submit bug reports. And make a stable release your primary concern going forward. New content should always be secondary to the stable, released build actually being stable and bug fixes should not be held up by unforeseen issues in new content releases. This would be useful for everyone. You will get bug reports for new content from technical users that are willingly choosing to use potentially unstable builds, instead of noise and complaints from the community at large that are frustrated that their game isn't working. Mod creators will get an opportunity to address issues before they make it into the stable channel, which should make transitioning to new releases a much smoother experience for them and for everyone that uses mods. And players like me will no longer be stuck waiting around for weeks for their fully released game to be playable without having to roll back to a previous release. This game is no longer in early access and there is literally no excuse for release builds being in this state. Again, I sympathize with the struggle but this is a serious problem that needs to be addressed going forward. Paying customers deserve a product that works. Edit: To be clear, I'm not suggesting nightly builds. I'm suggesting that before a release is pushed out as stable and finished, that it gets pushed out to a beta/prerelease channel first, for wider testing. I understand all the arguments against nightly builds, makes perfect sense to me. What doesn't make sense is that releases with major, show stopping bugs are being pushed out to everybody whether they want to be a tester or not. That may have been acceptable when this was an early access game but it's not anymore.

The lack of surrounding infrastructure around the new launchpad/runway really detracts from it. I appreciate the effort to add more content, but frankly if this is what is holding up the bug fix for landing legs and fairings then I'm pretty disappointed. Especially since I already paid you for more content and I can't even use it until those things are fixed. The bug fixes should be released ASAP and the new locations should be released later, when they're thoroughly tested and you're sure they won't introduce any more new bugs. I'd really like to play with the DLC I paid for now, not "soon".

I know, that wasn't directed at you. And @steve_v wasn't being especially awful about it either. I was just trying to keep the discussion constructive, not trying to wag my finger or make anyone feel bad.

I'm not so sure that releasing a patch that introduced a game breaking bug was a business decision. Pushing the 1.4 release before it was ready to get the DLC out? Sure. But this landing leg thing feels more like typical code debt that piled up well before Take Two ever got involved. They probably need to do a bunch of refactoring because the code base is getting sloppy and fixing one thing breaks 2 other things. It's a common problem.

Fair enough. I share your suspicions that the directive to release in this state probably came from on high somewhere, and that the developers wouldn't regress in this way if it were up to them. Hard to say what's going on behind the scenes. I just hope that whoever is making the decisions listens to feedback. I'd happily do what I could to run prerelease builds through the paces and submit bug reports if it meant stable releases were truly stable and mod updates wouldn't get scattered across point releases, and surely there are plenty of other people here willing to do the same. It's a waste to not take advantage of that going forward.