Seemingly random framrate drops.

[novahike999]

I've only been getting this issue since I installed ksp 0.21 but my framerate will be normal for about 30 seconds to 2 minutes and then it seems to be capped at 10 fps for about a minute. During the lag when it seems to be capped to 10 fps the mission clock will flash yellow about once every 2 seconds. Does anybody else get this or know how to fix it? Please, Kerbals lives are in grave danger if I crash a lander because of this again. D:

Mods I have installed:

Mechjeb 2

Nova Punch

TT Modular Wheels

Procedural Dynamics (Wings and Fairings)

Radial Nuclear Engines

Editor Extensions

SM SkyCranes

Lots of love - Pffft, You really think I love you?

[Guest]

It could be a MJ2 information window. Try this : When you notice lag starting, quickly, as fast as you can, pause with esc., alt-enter to windowed mode, _ ksp to the background, then go check KSP.log to see if it has spammed anything at the end of the log. This can help identify the exact problem.

[novahike999]

It could be a MJ2 information window. Try this : When you notice lag starting, quickly, as fast as you can, pause with esc., alt-enter to windowed mode, _ ksp to the background, then go check KSP.log to see if it has spammed anything at the end of the log. This can help identify the exact problem.

Yea, I get about 500 lines of "[LOG 12:37:27.140] Skipped rendering frame because GfxDevice is in invalid state (device lost)".

[Guest]

That is probably not what is causing your lag. That is a common error that is caused by "alt-tab"ing (or hitting the windows key on some keyboards) out of KSP to perform other tasks. That's why I suggested alt-enter to windowed mode first.

If it's a MJ2 error I would expect something along the lines of [LOG 18:27:37.317] getObtAtUT result is NaN! UT: 19254.37889324.

I suspect the new terrain is giving MJ2 fits when it tries to calculate your ships altitude above the surface.

Another way to debug is to close all information windows, then start opening and closing them one at a time to see if you can isolate the one that is causing lag.

edit : for anyone reading this thread : what does getObtAtUT mean? Does that mean something is asking for Orbit, Altitude, and UT(time)?

Edited August 22, 2013 by Otis

[novahike999]

That is probably not what is causing your lag. That is a common error that is caused by "alt-tab"ing (or hitting the windows key on some keyboards) out of KSP to perform other tasks. That's why I suggested alt-enter to windowed mode first.

If it's a MJ2 error I would expect something along the lines of [LOG 18:27:37.317] getObtAtUT result is NaN! UT: 19254.37889324.

I suspect the new terrain is giving MJ2 fits when it tries to calculate your ships altitude above the surface.

Another way to debug is to close all information windows, then start opening and closing them one at a time to see if you can isolate the one that is causing lag.

edit : for anyone reading this thread : what does getObtAtUT mean? Does that mean something is asking for Orbit, Altitude, and UT(time)?

What do you mean by open each information window at a time. And making it windowed did not fix it?

[Zeblote]

edit : for anyone reading this thread : what does getObtAtUT mean? Does that mean something is asking for Orbit, Altitude, and UT(time)?

I could be get orbit at ut, whatever a ut is, but get it for that specific ut

[Guest]

I may have made some assumptions that are not true, I'm bad about that. I assumed when you listed Mechjeb 2 as one of your mods, that you were using one or more of the information windows while flying rockets or planes. Windows like orbit info, surface info, or maybe even custom windows that you made for yourself, that give the pilot longitude,latitude,velocity,altitude,heading.etc. Like this :

I have recently experienced lag similar to what you described, and found that it was a MJ2 window causing it.

Even if MJ2 is not responsible, I believe that if you can prevent KSP from spamming "Skipped rendering frame because GfxDevice is in invalid state" by either :

a. quitting the game completely when you notice the game begin to lag then checking KSP.log(probably best) or

b. alt-enter to windowed mode then check KSP.log

then you will probably find whatever is responsible for lag. Try uploading KSP.log to pastebin or something then posting the link here. See this. Even though squad does not support installations with mods, there are still lots of people around that might recognize something and be able to help you out.

I could be get orbit at ut, whatever a ut is, but get it for that specific ut

Thanks for response. I guess it could mean get orbit at ut(i think that's universal time in seconds), but why is it a capital At?

Edited August 22, 2013 by Otis

[novahike999]

I may have made some assumptions that are not true, I'm bad about that. I assumed when you listed Mechjeb 2 as one of your mods, that you were using one or more of the information windows while flying rockets or planes. Windows like orbit info, surface info, or maybe even custom windows that you made for yourself, that give the pilot longitude,latitude,velocity,altitude,heading.etc. Like this :

I have recently experienced lag similar to what you described, and found that it was a MJ2 window causing it.

Even if MJ2 is not responsible, I believe that if you can prevent KSP from spamming "Skipped rendering frame because GfxDevice is in invalid state" by either :

a. quitting the game completely when you notice the game begin to lag then checking KSP.log(probably best) or

b. alt-enter to windowed mode then check KSP.log

then you will probably find whatever is responsible for lag. Try uploading KSP.log to pastebin or something then posting the link here. See this. Even though squad does not support installations with mods, there are still lots of people around that might recognize something and be able to help you out.

Thanks for response. I guess it could mean get orbit at ut(i think that's universal time in seconds), but why is it a capital At?

Your assumptions are not wrong. I do use one or more windows, I just didn't know what MJ2 meant.