Computer Upgrade - Weird lag even with high fps and language mix-up

[luizsilveira]

So I've recently upgraded from a celeron with Intel HD graphics to a Ryzen 3 2200g with Vega 8. Huge improvement, as you can imagine. But mainly two things are really bothering me. Sytem has 8Gb RAM, out of which I allocated 1Gb to VRAM.

1) A few words, both in the game and in some mods, are in my native (windows 10) language. Which is weird. Everything else is in English just fine, it's just a few random words here and there. Slightly annoying but not unplayable.

2) With current 1080p and medium settings I get 60+ fps on the main menu and with small vessels in space. With large (100+ parts) vessels and stations, I still get 40+, which is pretty good on my book. But. If I look at a planet with atmosphere (tested on Eve and Kerbin), my fps drops to 17. Same thing happens on KSC, I have 17fps. If, in the very same scene, I move around to have the space on the background, fps goes straight back up to 40+. What is going on? Is there some specific setting I'm messing up? I've tried several, none made a difference. Eva around a station orbiting Kerbin was a chore; I think due to the physics slowdown to compensate, everything was in super slo-mo. Playing on my celeron the looks were very ugly but I didn't have such problems with everything slowing down as much.

3) My clock on the top left is yellow some 95% of the time. I've heard this happens when physics has slowed down because of poor performance. Well, why would it slow down when I have 40+ fps? I went to check CPU and it's 50 to 60% in use, 70% at max with huge vessels. And yet physics is slowing down pretty much all the time?

Disclaimer: I have quite a few mods, but none of them are visual or do anything to graphics. I think the only parts mods are Hullcam, Surface Lights, and KIS/KAS.

[hendrack]

Gonna need logs:

KSP.log in the game directory and player.log

Quote

Windows:
- 1.8 or newer:
 %USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\Player.log
- 1.7.3 or older:
KSP_win\KSP_Data\output_log.txt (32bit) or
KSP_win64\KSP_x64_Data\output_log.txt (64bit) or
%USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\output_log.txt

 

[luizsilveira]

21 minutes ago, hendrack said:

Gonna need logs:

KSP.log in the game directory and player.log

 

Duh. Sorry.

KSP.log
Player.log

I've noticed that my settings got messed up. I moved only the gamedata folder from old to new computer. So Max physics delta-time per frame was at 0.02, all the way to the left, which is probably not ideal and could help explain part of the problems.

 

[hendrack]

Can't find anything special in the log, only some warning about DMagic and some science mods, perhaps check the dependancies.

[luizsilveira]

37 minutes ago, hendrack said:

Can't find anything special in the log, only some warning about DMagic and some science mods, perhaps check the dependancies.

Interesting find, thanks.

I do not have dmagic's science mods and never had. I did have contracts window at some point.

The mentions on the log seem to be related to orbital science, which I never had installed. My science mods are [x] Science! and AutomatedScienceSampler. I see the latter is referencing dmagic stuff so it's probably something to integrate those mods, in case I did run both?

[luizsilveira]

Just in case, I've deleted \DMagicutilities folder from gamedata. It was seemingly just a leftover from Contracts Window I had tried out at some point.

I've increased Max physics delta-time per frame to no result whatsoever. I suppose my fps is now a bit lower on map view (mid 30s), but the clock is still yellow most of the time with any vessel, and all the time with any vessel larger than a couple dozen parts. On small vessels and looking at space I get 60+ fps, on larger vessels I get more like 30ish. But in either case the clock is yellow.

I'm finding it rather bizarre that I'm having a problem now with a Ryzen 3 2200g that I didn't have a Celeron N4100 (both cases with onboard graphics). Sure, I had (much) lower fps and worse-looking graphics, but I didn't have this slow-mo feeling all the time. 

To complete my bafflement, both CPU and GPU are just chilling at 50~60% and 40% respectively. 

[Harry Rhodan]

5 hours ago, luizsilveira said:

To complete my bafflement, both CPU and GPU are just chilling at 50~60% and 40% respectively. 

Is that only for one thread or is the whole CPU running at 50%? KSP uses only one thread for physics calculation per craft. That usually means usually any combined usage of more than 25% on a quad core with only four threads will indicate that the one core that is calculating your rocket is running at full speed.

[luizsilveira]

17 minutes ago, Harry Rhodan said:

Is that only for one thread or is the whole CPU running at 50%? KSP uses only one thread for physics calculation per craft. That usually means usually any combined usage of more than 25% on a quad core with only four threads will indicate that the one core that is calculating your rocket is running at full speed.

That difference did cross my mind. I don't know how precise Afterburner is but it's what I was using to check. 50-60% seems to be the most used CPU core; the others are 30~40% each.

Edit: I'll try to get a screen shot.

Edited June 21, 2020 by luizsilveira

[Harry Rhodan]

8 minutes ago, luizsilveira said:

That difference did cross my mind. I don't know how precise Afterburner is but it's what I was using to check. 50-40% seems to be the most used CPU core; the others are 30~40%.

Then that might be related to your current RAM setup and the CPU is actually waiting too long for the data.

[luizsilveira]

On 6/21/2020 at 2:31 PM, Harry Rhodan said:

Then that might be related to your current RAM setup and the CPU is actually waiting too long for the data.

Well, the RAM has arrived and the difference is noticeable in this specific problem (physics lag). I got more fps too, but the clock is still yellow and the physics lag behind quite significantly in some situations (though not all like before).

So like I said above, my fps would drop to 17 on large vessels when looking at a planet. Now it only drops to 30ish, and that is considering I increased the terrain settings. That´s looking into a 140 parts station too, so not bad at all.

However. When I look at Kerbin through this station, I get 30fps yet 10 real-life seconds equal 6 in-game seconds. Almost a 1/2 time warp! The most used CPU core is at 60% at this point, while the other three are oscillating at 30~40%.

If I look away from Kerbin and into space through the same station, fps goes up to 45+ and 10 real-life seconds equal 9 in-game seconds (clock still yellow). That's rather tolerable.

One weird thing I noticed though: my max physics delta setting is not saving.

I've tested it with min (0.02) and max (0.12 I think) setting and the difference was precisely nil. Same behaviour and performance. Yet every time when I come back to the main and then settings menu, it is set back at 0.02. 

Looking it up I noticed some people had trouble with settings not saving on 1.8. I'm running latest 1.9, and all the other settings do save. Only this one seems to reset back to 0.02 and has no effect in-game.

Thanks for any insights.

Edit: tried editing settings.cfg itself to try and use the max physics delta setting. No joy. No matter what I set it to, game is the same and the information on the file actually gets reverted back to 0.02.

Edited June 24, 2020 by luizsilveira