Yellow MET, always, forever.

[mielgato]

Greetings everyone,

I'm not really sure where I should post this as i'm running a (very lightly) modded installation, but it's something that is also happening on stock installation. So i'm going Jebediah and post this over modded section

It has been adressed already, but I'd like a fresh point of view with data that may have been distilled over multiples threads.

To put it bluntly, the MET timer is ALWAYS yellow and will turn red when going over the mach1 bar with a 150parts aircraft. Which mean there is time dilation for calculation, that I understand. What I don't, is why i'm having the MET flickering fast green/yellow with a 19parts aircraft sitting on the runway ?

This is also happening in kerbin's orbit, regardless the craft size (well, with smaller craft >20parts the MET flicker from green to yellow, any bigger will make it stop flickering for a steady yellow, anything over 100parts, is almost unplayable)

I tried to set KSP's afinity on only one core, then two core, to see if there is a difference, but definitly no. (probably my CPU is too weak to allow the game to run without time dilation ?)

I tried fiddling with the max physic delta-time per frame option, but while I can get me the green MET again by doing so, I get a performance hit (getting under the 25fps bar, which is what I get with default settings of 0.04, half res). If I was playing on a laptop, I could have understood, but that's totally not the case for me as i'm using a custom desktop rig with a decent CPU (looks, it's an amd fx8350 black ed, I said decent, not awesome, yeah ok, its single core performances barely compare to an I5 4690K, but still, is that the cause ?)

dxdiag : https://www.dropbox.com/s/mn5mb5m04zspxxl/DxDiag.txt?dl=0

Mod list : Toolbar, DistantObject, Haystack, KAS, KIS, KER, KJR, PlanetShine, CriticalTempGauge, ScienceAlert, StageRecovery, TACFuelBalancer, KerbalAlarmClock, WindowTransferPlanner

 

Basically the question is :

Is there a community made fix ? Or should I wait for 1.1 (soon™) and pray that Unity5 will fix KSP's performances issues ?

 

edit: Ok, I played a bit with CPU overclocking, went from 4ghz up to 4.2ghz + went from 1.325vcore up to 1.4vcore, to see if there is a difference, and there is one slight, i'm getting a few more fps on the runway (3 exactly... I'm running on stock cooling, so I'm not overclocking more anyway), but time dilation code yellow is still there.

edit2 : I gave another try with a fresh stock installation, yup, 100parts craft sitting on the runway, steady yellow. 19parts craft sitting on the runway, flickering yellow. No change, it's definitly not coming from the mods I had

Edited February 2, 2016 by mielgato

[John FX]

have you tried changing your physics tick (is that the right name?) in the options?

Increasing the minimum time slicing will make the game run closer to realtime although at the cost of physics accuracy.

 

Mine also always runs yellow and I have SSD, 4Ghz cores, 24GB RAM and a GTX 690

 

EDIT : Ah, I see you already have. It seems we have to choose the trade off we want, high FPS or more physics ticks as one comes at the cost of the other.

Edited February 5, 2016 by John FX

[sackfalte]

don't overclock your hardware for this, it's not worth it, especially when using stock-cooling.

 

Are you playing on Windows? If so, why not try Linux, to see whether there's a difference?

[Red Iron Crown]

Try turning off the aero effects, the white "Mach effect" and reentry flames seem to be really expensive computationally.

[micr0wave]

did you check your computer if something is eating away the resources ?

Maybe avira going mad in the background or something, i have just a i3 and can have a steady green time with medium sized crafts

[Red Iron Crown]

Another thing to check: Some power management software does not correctly interpret KSP's high single thread load, it sees that as <100% load and starts to throttle. A quick way to check is to set your PC to "Performance" mode and see if the behavior persists.

[Ixenzo]

Planet Shine has been known for reducing performance, as well as anti aliasing. Aerodynamic FX don't really affect performance.

You best bet would be increasing physics dt. It's just the way KSP does things.