Fps counter that works with 4.35
-
Is there one in game? Tried MSI Afterburner, It works in the UI but not in flight, same with 4.34, tried the one in Win 10 but only works in 4.34. What are you guys using in 4.35? Trying to solve a performance issue in 4.35
Thanks, Marc… -
@marcq12 press Alt press C release Alt release C within a second press F for in-game FPS
-
@marcq12 as oakdesign says, Alt+C then F works well and has an advantage that it shows frame times across the CPU, GPU and the sim engine to see what your bottleneck is, MSI Afterburner has worked for me in 4.35. What mode are you running BMS in, full screen or windowed?
-
@snake122
Was using full screen mode
Marc… -
Thanks guys it worked, funny thing is that the win 10 fps counter now works in 4.35
Marc…
-
@Marcq12
Obvs start with the new [alt+C][F] (or setset g_bShowFrameRateDefault 1
in cfg file)Beyond that, I like Nvidia’s FrameView tool. (Works for AMD and Intel graphics, not just NVidia … I think it’s just a GUI wrapper around Intel’s open-source PresentMon tool.)
It can show p90 or p99 frame-rates, which is more meaningful than just “average” fps.
-
so i thought i would try to remember the keystroke for fps mid-flight (not a good idea of course!) and i think i hit alt or ctrl alt and c then r and i think it broke the jet…lol!!!
i started flipping different things at that point and it just seemed to get worse.the best part is, knowing falcon over the years (not expert at all), if i knew what i did wrong, i could have probably recovered.
i tried flcs, avionics, battery, toward the end i even tried shutdown on downwind leg in hopes to get out of secondary engins(checked switch there also)@40:32 into video below is when i hit the keystroke if your curious to see it.
-
@Justice lol I’m surprised this kind of thing doesn’t happen more often
I run with a very minimal keyfile partly for this reason … it’s exactly the kind of fat fingering I might do
-
@Justice alt c : r is the key combo for random system failure or as I like to call it EJECT!
-
@Justice I’ve remapped mine to something easier ages ago, but now it’s just there when I start playing, no need to turn it on/off as it’s always on.
-
You broke the engine, probably with “random error generator”.
Can’t say what exactly (you sucked a bird … poor birdie), but engine was in SEC, even switch was is in PRI (default).
Your engine temp was in excess 1000-1100C , OVERHEAT, it was miracle you didn’t catch fire.
Land ASAP, or bail. - or try flameout if feeling luckyCheers
-
@CriticalMass so it was probably a bad idea to press that again(whichis what i did) thinking that it would undo what i did. knew deep down after all my time in falcon, it was not a good idea to try to guess a key command lol.
-
-
@Snake122 said in Fps counter that works with 4.35:
@marcq12 as oakdesign says, Alt+C then F works well and has an advantage that it shows frame times across the CPU, GPU and the sim engine to see what your bottleneck is, MSI Afterburner has worked for me in 4.35. What mode are you running BMS in, full screen or windowed?
FWIW, the BMS counters do not show GPU frame time. There is no easy way to show actual pure GPU frame time without really measuring every draw call via a dedicated DirectX functionality (BMS doesn’t try to do that because with all the draw calls there are, it would be extremely hard to follow).
What BMS shows you in thos 3 columns regarding frame times and FPS are:
-
General - Overall time/FPS
-
Sim - Means CPU time spent on preparing draw calls (That does NOT include Logic time, i.e no avionics, AI etc)
-
Render - Means CPU Render thread time - The closest you can get for GPU frame time without actually measuring internal GPU times
Logic/AI/avionics/campaign and anything else not related to GFX can be estimated more or less as the diff between 1 and 2 (i.e General FPS and Sim FPS).
-