PSA - 1.01/1.02 Temperature Gauges/Overheating Display Causes Massive Memory Leak

[problemecium]

For anyone interested, I too have observed odd FPS-related phenomena in 1.0.2.

In 1.0.0, the performance when looking away from the ground was pretty great, but the FPS would drop tragically whenever I dared to look down. I solved this by disabling SM3 terrain shaders, which sadly detracted from the aesthetics a bit but boosted my FPS dramatically.

In 1.0.2, I observed that the FPS was significantly higher most of the time, including looking at the ground (although I haven't tried turning SM3 back on), but every few seconds KSP seems to "hiccup" and experience low FPS (less than 10) for a second or two before returning to full speed.

Also, I was pleasantly surprised at the lightning-fast scene transitions in 1.0.0, but those seem to be gone in 1.0.2, and they seem to gradually get worse as time passes until after a few hours I find myself staring at the loading screen for a good ten seconds or so when trying to revert flights or return to the Space Center. All in all this seems symptomatic of a memory leak.

[smjjames]

I didn't find anything like that but i create a small mod that does this

Can be found here if you don't want all the other mods in there you can just remove their dll's

Thanks, I want to avoid that too.

Squad shoulda tested the hotfix a bit further, heh......

[KandoKris]

oh dear and to think I was upset at myself for not knowing about 1.01 & .02.. seems I'll stick with 1.0 till 1.03 maybe

I have been wanting a temp gauge to tell me when things will blow-up but not at the cost of gameplay so yeah I'll stick with 1 for now.

[Temeter]

oh dear and to think I was upset at myself for not knowing about 1.01 & .02.. seems I'll stick with 1.0 till 1.03 maybe

I have been wanting a temp gauge to tell me when things will blow-up but not at the cost of gameplay so yeah I'll stick with 1 for now.

Those things are indeed ultra-useful and nice-looking, but yeah, sadly not really usable atm. If you want to check heating of your ship try the heat context and saturation in the debug menu. While nice, they're more something for specific situations compare to the gauges which only get visible when they're needed.

[Levelord]

Between my initial annoyance with 1.0.2 soup-o-sphere, I can and do get my SSTOs into LKO. The problem now is that the game is virtually unplayable because it ALWAYS crashes once I go above 70km due to the memory leaks. Every single SSTO I bring up into orbit crashes the game because it can't handle the heat display.

Honestly, I think 1.0.2 is a joke and the people who are defending this update are complete shills.

[Tarheel1999]

So hit F10 to disable the gauges.

[spinomonkey]

Honestly, I think 1.0.2 is a joke and the people who are defending this update are complete shills.

A bit harsh. Yes, the memory leak needs to be fixed. But even with a memory leak I'm running to the Mun and back without as much of a shutter from the game. Sounds like part of the problem is your system.

[Temeter]

Between my initial annoyance with 1.0.2 soup-o-sphere, I can and do get my SSTOs into LKO. The problem now is that the game is virtually unplayable because it ALWAYS crashes once I go above 70km due to the memory leaks. Every single SSTO I bring up into orbit crashes the game because it can't handle the heat display.

Honestly, I think 1.0.2 is a joke and the people who are defending this update are complete shills.

Or you just press the button to deactivate the heat gauges and continue playing. Really, are you so utterly and pathetically obsessed with being enraged on an internet forum that you torture yourself in a game?

Helps to know the most basic things about a game before judging it.

[Cdr_Zeta]

Hello,

Also I havnt got that far yet but...I think the game is fine so far; I havnt built a ssto dont even know what that stands for - shuttle? Use more engines?! Watch the aerodynamics? They say now, just like I have always done, to go to APO before going to circ burn; actually in real life this isnt true because at 45deg you lessen the aerodynamics; so now we all circ burn like I have been doing which isnt realistic !

Zeta

[wossname]

Between my initial annoyance with 1.0.2 soup-o-sphere, I can and do get my SSTOs into LKO. The problem now is that the game is virtually unplayable because it ALWAYS crashes once I go above 70km due to the memory leaks. Every single SSTO I bring up into orbit crashes the game because it can't handle the heat display.

Honestly, I think 1.0.2 is a joke and the people who are defending this update are complete shills.

I only payed £22 for my copy, this is very cheap for such an excellent game (in my no doubt dubious opinion as a complete shill).

You, however are complaining like someone who, either paid a lot more for it, or has no other difficulties in their life. It's just a game, lighten up, go play something else.

[FunnyBunny14]

For anyone interested, I too have observed odd FPS-related phenomena in 1.0.2.

In 1.0.0, the performance when looking away from the ground was pretty great, but the FPS would drop tragically whenever I dared to look down. I solved this by disabling SM3 terrain shaders, which sadly detracted from the aesthetics a bit but boosted my FPS dramatically.

In 1.0.2, I observed that the FPS was significantly higher most of the time, including looking at the ground (although I haven't tried turning SM3 back on), but every few seconds KSP seems to "hiccup" and experience low FPS (less than 10) for a second or two before returning to full speed.

Yeah, I have those too...

On another note, it would seem that the grass around KSC gets messed up after using the temp gauges.

[locustgate]

I thought I was noticing something wrong with the memory again...

I have to start over because my space plane suddenly causes the game to crash, I can't revert.

[Renegrade]

I hope Squad gets back from skydiving (in one piece) soon to patch this. I've been turning the indicators off, but I'd like to play with 'em on at some point~

[r4pt0r]

I hope Squad gets back from skydiving (in one piece) soon to patch this. I've been turning the indicators off, but I'd like to play with 'em on at some point~

hopefully they take a few days with no pressure to methodically comb through 1.0.2., find things like this memory leak, and then leave us with 1.0.3 before settling in for the long haul to the next big update.

[waterlubber]

What exactly happened with the aero? I know the cubic struts occluding 3.5m tanks was fixed, but why are people calling it a soupisphere? Also, what's the difference between them? I'm pretty dissapointed in Squad for this.

[klgraham1013]

What exactly happened with the aero? I know the cubic struts occluding 3.5m tanks was fixed, but why are people calling it a soupisphere? Also, what's the difference between them? I'm pretty dissapointed in Squad for this.

They increased drag and lift by ~30%.

[Renegrade]

hopefully they take a few days with no pressure to methodically comb through 1.0.2., find things like this memory leak, and then leave us with 1.0.3 before settling in for the long haul to the next big update.

Actually their performance under pressure is better and cleaner than their normal "when it's ready" mode, based on what we've seen. Or at least, no worse than normal. They added a metric (yes, metric) buttload of stuff to 1.0, and I'd say that the bug rate is, at worst, equivalent to previous releases, or even slightly better, in terms of bugs / feature*complexity.

(which is totally bizarre and doesn't make sense but .. there it is..)

[problemecium]

I had a dream last night that I woke up this morning and checked for a 1.0.3 patch and discovered they had not only fixed these bugs, but had moved on all the way to 1.0.5 while I wasn't looking xD

[Levelord]

A bit harsh. Yes, the memory leak needs to be fixed. But even with a memory leak I'm running to the Mun and back without as much of a shutter from the game. Sounds like part of the problem is your system.

I don't think my system suddenly became inadequate between the 1.0 and 1.03 update. You're speaking from a rocketry perspective though, and while I enjoy playing with rockets, SSTOs are are particular enjoyment for me. I doubt that SQUAD would have spent so much time overhauling the atmosphere as it is if planes and SSTOs were not an important part of the gameplay to them. Currently, the memory leak effectively blocks out an entire mode of gameplay and it really needs to be addressed urgently.

Or you just press the button to deactivate the heat gauges and continue playing. Really, are you so utterly and pathetically obsessed with being enraged on an internet forum that you torture yourself in a game?

Helps to know the most basic things about a game before judging it.

You can press a button to deactivate anything, but it's

1) A workaround.

2) Not a fix.

3) Needs to be reset with every new launch of the game.

4) Willfully trying to ignore a problem that needs fixing in the first place.

I've been beta testing this game since 0.16 and never once asked for a release date, or asked that the game be rushed to a deadline. All I did was find bugs and reported them. But at every turn I find moronic sycophants who had some irrational emotional attachment to the game that they try to defend, cover up and hide the every bug/problem the game had. It's frustrating, annoying, hinders progress, wastes time and is outright dishonest. I'm sorry, but trying to downplay a bug isn't honest to me. A bug is a factual statement and not a matter of opinion. I'm sick of people telling me that every bug should be compensated by the player and implying that it's not worth fixing.

I only payed £22 for my copy, this is very cheap for such an excellent game (in my no doubt dubious opinion as a complete shill).

You, however are complaining like someone who, either paid a lot more for it, or has no other difficulties in their life. It's just a game, lighten up, go play something else.

I paid less in real money for the game, and I paid more in contributing time to helping the game become the best I could be by testing it and making sure it's polished. Whether SQUAD wanted to use us as a community to help test the game is another topic, but I at least reported any game issues to make sure they see it and know it's a problem. Unfortunately, people don't like the fact that the game is going to have bugs in it's beta state and keep trying to hinder any sort of bug reporting by pretending it's not an issue. Now it's in a released state and these people are still going about pretending that this isn't a bug or a bug worth fixing.

Some people want to invest time in a hobby and to work to build a project, I don't go about telling people to embrace mediocrity and to go do something else. It's like kicking a sandcastle someone invested time helping to build, telling them it's just a sandcastle and to go play something else.

[Tarheel1999]

Except of course, it does nothing of the sort. Press F10. Problem solved. You are no longer prevented from flying SSTOs. Or if this upsets you so much stop playing until Squad releases a fix.

Considering the amount of button pressing this game requires, you are not going to convince anyone that pressing F10 once when the heat gauges show up is a hardship.

[Levelord]

It's

1) A workaround.

2) Not a fix.

3) Needs to be reset with every new launch of the game.

4) Willfully trying to ignore a problem that needs fixing in the first place.

This is exactly the type of problem I'm highlighting with you people. It's a button press that is irrelevant to the gameplay and should have been unnecessary from the get go. You're trying to argue that since it's 'not a hardship" (which isn't what I'm arguing) that it's a bug not worth fixing.

[Temeter]

You can press a button to deactivate anything, but it's

1) A workaround.

2) Not a fix.

3) Needs to be reset with every new launch of the game.

4) Willfully trying to ignore a problem that needs fixing in the first place.

I've been beta testing this game since 0.16 and never once asked for a release date, or asked that the game be rushed to a deadline. All I did was find bugs and reported them. But at every turn I find moronic sycophants who had some irrational emotional attachment to the game that they try to defend, cover up and hide the every bug/problem the game had. It's frustrating, annoying, hinders progress, wastes time and is outright dishonest. I'm sorry, but trying to downplay a bug isn't honest to me. A bug is a factual statement and not a matter of opinion. I'm sick of people telling me that every bug should be compensated by the player and implying that it's not worth fixing.

You know, when you feel obligated to arbitrarily suspect some damaging logic behind a behaviour, that could be easily explained by being nice and helpful, then it might be time to calm down and take step back. Nobody tries to defend the bug, which is obviously a very serious one on his own, but not using the ultra-simple workaround for the time being would be stupid.

Edited May 5, 2015 by Temeter

[Luis]

There is a tendancy to shoot the messenger in these forums whenever someone tries to report a bug. Arguing away the bug is not the best way to get them fixed.

[Temeter]

There is a tendancy to shoot the messenger in these forums whenever someone tries to report a bug. Arguing away the bug is not the best way to get them fixed.

Nobody does that. If you talk about the 'lol look how broken the game is (lulz hotdogz)', 'squad is ruining ksp' or 'hopefully far will redeem me from this bs' stuff, yeah, toxicity creates a counter reaction. I haven't seen a single reasonable bug report that got shot down.

So, if you claim tendency to do that, link some examples. Should be easy to find a common occurance on a public forum.

[Tarheel1999]

It's

1) A workaround.

2) Not a fix.

Obviously. None of this in dispute. I started this thread to bring this bug to the attention of both Squad and fellow players. But this bug does not "block an entire mode of gameplay." Rather it is a inconvenience and it prevents players from using a cool and helpful new feature (the gauges). The sky is not falling chicken little.

- - - Updated - - -

There is a tendancy to shoot the messenger in these forums whenever someone tries to report a bug. Arguing away the bug is not the best way to get them fixed.

Funny. I wasn't shot for reporting the bug (look at the OP) but for being insufficiently melodramatic when doing so.