Brian444444

Just what the title says...after a time warp, almost always with drill in ground, the ship will leap off the surface to an altitude of 200 meters give or take. My drills are not positioned in such a way that the ship teeters when deployed too low. I would GREATLY appreciate any explanation as to why. I am running some mods. Probably too many to really list. But if you know what causes this please let me know. Running 1.3.1 but this has been happening for years... Is it a KSP thing or a mod thing?

OK, so I am using version 1.2.2 64-bit. My addons are as follows: Chatterer Community tech tree Hanger extender Kerbal Engineer Redux Kerbal Joint Reinforcement Kerbal Research and Development Kittopia Tech Kopernicus Planetary System Modifier MechJeb and Engineer for all Modular flight integrator Module manager Real scale boosters Real scale sea dragon Real solar system textures 2048X1024 RSS My system has 24gb of RAM, i7-5930k CPU, GTX 980 video card. Using the non-RSS version, with most of the aforementioned add-on running as well, I run full 4k graphics with all settings pretty much maxed out and its smooth as silk. The frame rates do vacillate some under those settings but it is never noticeable to the naked eye. Using the RSS version I cut the resolution down to 2560x1440, really dumb down the terrain details, render and texture quality as well as most other settings and whenever near landing on a non-earth body I get a slide show. In and around Earth its pretty smooth with no issues. Go to the moon and orbit is OK but when you get about 300 meters above the moon I start to get really crappy frame rates. Its not a slide show but its only marginally better than that. When I went to Mars... Good God. As soon as I entered the atmosphere I got a slide show. As it currently sits it is unplayable with RSS. I want to add other addons but don't dare until this RSS issue is resolved. Does anyone have any ideas of what I am doing wrong or suggestions? The obvious answer is stop using RSS...but I'd like to try it to shake things up. Any help would be appreciated.

Print screen in Windows and Shadowplay from Nvidia.

Yeah...well something I learned is if I don't set my shortcut to windows 7 compatibility then its a total crashfest. But in compatibility mode its not as good if I were running 7. I run 10 fwiw. Anyway, I think Unity is 99% of the problem. They try to be a jack of all trades with their code and are essentially masters of none. I mean come on... how long has windows 8 been out and what version of Unity did squad pick to build 1.1 on?

What O/S?

Is Kerbin finally being hit by the big one? Is this as result of our fracking? Are the Gods angry? Joking aside...wth is this? Anyone ever seen this before? It will literally shake like that for 2 hours if I let it and never explode... Scarrrrrrrrrrrrrrrrrrrrrrrrrrry....

Most likely it is because there is an instability in the design somewhere. For instance not enough support struts in the right places. That being said however, I have reverted flights before and they launched fine initially coming out of the VAB and after reverting they just blow up all over the place on the pad. That surely seems like a bug to me.

And this vacation.... Wouldn't it have made more sense for them to take their two weeks prior to release so they could be refreshed and responsive to create patches/fixes once it was released?

Oh the Kermanity! Those poor dudes walking around in the VAB are extra-crispy!

I guess the only thing I would add here is that it has become the norm across all software, games, O/S's, whatever really to release without solid testing. Now we can argue the definition of "solid" testing, but that is what the norm has become. As consumers of these products its HIGHLY frustrating after YEARS of this practice to not be irritated when you sit down with all these great promises and its only 25%-50% functional and the expectation is that the consuming public essentially acts as beta testers. This isn't a shot at Squad but everyone that makes software. I can't tell you the last time I saw a release of software that was for all intents and purposes bug free or even close for that matter. While Squad isn't doing anything different than anyone else in the market place in this regard that doesn't make it any less frustrating for us the consumer. But if Squad is at fault anywhere here in my mind its that they didn't resist the community pressure to release something that wasn't ready. People who are "hating" are just frustrated and everyone expresses themselves differently. But I do agree that we need to do our best as the community to chip in and work with squad to get these issues resolved. It is what it is and just complaining isn't going to help the situation one bit. I have entered a bug report. Yes it is time I could have spent doing something else, but if I don't tell them they aren't going to know its a problem. There are too many O/S's, too many differences in hardware, too many mods, etc..., etc... for a realistic expectation of thorough testing without the cost of the game being outrageous. Patience grasshoppers.

Don't you mean a caucus?

Your thyroid is acting up again... Consult your physician.

This is no rub on how you prefer to play but I prefer the challenge of career. Want to use the fancy smacy parts? Earn them. But that's just me.

That actually never worked for me... IDK why

I made a thread about this a while back and ultimately opened a bug report in bug tracker. They are still working on that I guess but I found out today with some playing how to "work around" this issue. This is what happens: I can be playing along doing whatever leave game and come back and this happens. It now appears to be directly related to UI scale setting. I normally play with a 110% UI scale because I play the game in 1900x1220 rez and its just hard to see at 100% UI scale. After going into settings on a hunch and altering the UI scale back to 100% the load screen is magically back to normal. Strangely at 120% scale it doesn't have the problem.... I updated the bug tracker to reflect this discovery but wanted to share with everyone so if you are having this problem and want a work around to it until it is fixed in a future release.