playing a single note (C4) for 5s taking readings every 100ms until 1s after release and taking maximum value It creates a CSV with the engine id, test name, minimum CPU usage for this test, index of preset that gave minimum CPU usage, maximum CPU usage for this test, index of preset that gave maximum CPU usage, average CPU usage of this test for all presets tested. Theoretical frame rate should be 1000/R or 1000/G, whichever is worse, but in practice is lower than that.I have knocked together a python script that instantiates a synth, connects MIDI and audio, selects presets, plays notes and monitors jack cpu usage. Whichever of R or G is highest is your bottleneck. If this is your bottleneck, reduce these or get a faster GPU. G is affected by resolution, AA, AF, AATransparency, filtering, sharpening, FXAA, heat haze, and any other pixelly things I’ve forgotten. If this is your bottleneck, reduce these or get a CPU with a faster single core speed. R is affected by scene complexity, objects, mirrors, shadows, dynamic shadows, dynamic track, grandstands, car detail, event, objects, crowd, car complexity, etc. Slower CPU’s might need to reduce the number of visible cars or get a CPU with a faster single core speed. You can monitor this in-game by adding CRG meters to the FPS blackbox.Įdit \documents\app.ini ĬPUMeter=1 Include the sim-thread's CPU usage in the L/Q/S meter group?ĬPUMeterAsText=1 Show CPU meter as ms in text?Ĭ is the CPU doing the physics thread at 60Hz, so needs to be under 16.7ms, and under 14ms in practice. Here Clive Norton explain how to do it and read them. Also, you can check it online going here: iRacing has a simple visual tool to help with these findings. Sometimes with the VR (Oculus, Vive, etc.) and the new CPU’s we are in doubt about what device is stopping us from reach the optimal performance.
0 kommentar(er)
