FPS impact of 4.35
-
-
[older Core i7-3770 system, newer NVidia GTX 1660 Ti]
I’m getting a pretty serious FPS reduction, in 4.35 … seeing mostly 50-70 fps, down from 80-100 fps in 4.34.4.
Anyone else? Or is it just my ~8-year old CPU…
And yet … even at the lower frame rate, somehow 4.35 “feels” better to me than previous version. Improvements to the flight model? Or did the move to DX11 reduce end-to-end latency in the rendering pipeline?
Hoping santa brings me a Ryzen 5000 cpu. Until then, I’ll get by with 50fps.
Have you gone through each and every config option to be sure you are comparing fairly ?
-
I just tried setting everything to the least demanding settings and had about 80-100 FPS in the TR_BMS_21_Osan_Taegu training mission. Enabling Shadow Mapping brings it down to around 20-30 FPS. There has always been an performance impact by shadows but it was not that extreme for me in 4.34.
-
Settings and pc specs and fps chase is kinda a never ending story…
The BMS manual has very nicely documented the settings.
So control gfx from Falcon and leave it on gfx driver to application controlled.The other way around is playing and finding your unique setup sweet spot. This can take zillion of tries and checks and logging and whatever.
And the results almost all the times will be different if you try different aspects or missions or time.So do the basic setup, see if your system is ok, generally from 4.34 should have same or better performance, with better the most common case.
Then once you have verified you are on the safe side play as much as you like to find the sweet spot.The general rule is don’t look the fps, disable them, if it’s fluid to your experience then you are ok, go enjoy it. The number is just a number.
Fine example in flight simulation… all chasing the highest fps, like I have 144Hz monitor and I only have 60 or 90 fps and suddenly MSFS 202 comes and everyone is super happy with 20-30FPS and going WOW, same for RTX, chasing fps and enabling raytracing goes to 30-40 but it’s WOW and suddenly everyone is silent on the oh my eyes hurt with such low fps… For me it’s the experience and not the number.
-
Thanks for your reply Arty!
Settings and pc specs and fps chase is kinda a never ending story…
The BMS manual has very nicely documented the settings.I’m aware of the documentation.
So do the basic setup, see if your system is ok, generally from 4.34 should have same or better performance, with better the most common case.
Then once you have verified you are on the safe side play as much as you like to find the sweet spot.That’s why I’m replying to this thread. I have a fluid experience in 4.34 and since most of the people are reporting even an increase in performance I’m wondering what’s happening on my system.
The general rule is don’t look the fps, disable them, if it’s fluid to your experience then you are ok, go enjoy it. The number is just a number.
Exactly, I wouldn’t be bothering with it, if the experience wasn’t unpleasant.
Looking at your specs, guessing you are having no issues, I’m wondering what the issue with my setup could be. But since 4.34 (on the same system) is not showing such low performance with the same config settings I’m trying to figure out what the issue could be.
-
Logs m8, logs.
Run app that logs cpu and gpu performance, run falcon, then observe the logs and what can bottleneck.Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
Have you gone through each and every config option to be sure you are comparing fairly ?
I used a diff tool to compare the cfg files … I know not every option is a cfg line entry (eg. cloud resolution). And it appears some options have been added/removed or consolidated. Eg. no more per-pixel/vertex lighting… and no more option for cockpit/focus shadow. But apart from that I’m 99% sure I’m comparing fairly.
I’ve gone back to square zero … trying hyperthreading on/off … fullscreen vs borderless window … etc.
-
I just tried setting everything to the least demanding settings and had about 80-100 FPS in the TR_BMS_21_Osan_Taegu training mission. Enabling Shadow Mapping brings it down to around 20-30 FPS. There has always been an performance impact by shadows but it was not that extreme for me in 4.34.
YES this seems to be it! Turning off shadows made a huge impact. The ‘sim’ frame timer dropped from around 15-20ms to around 7ms. Enough for me to max out my 100hz monitor.
In 4.34 we had more fine-grain options for shadow control… here are the settings I had before (which saw about 90-95 fps, just daytime landing in Kunsan, TR #3)
set g_bShadowMapping 1
set g_bCockpitShadows 1
set g_bFocusShadows 0
set g_bShadowOnSmoke 0
set g_bWaterNormalMapping 1
set g_bWaterEnvironmentMapping 0
set g_bEnvMapRenderClouds 0
set g_bEnvMapRenderFocusObject 0And here is what I have now in 4.35… now getting up to 100fps. (Turning off g_bShadowMapping was the huge framerate win, on my system.)
set g_bShadowMapping 0
set g_bShadowOnSmoke 0
set g_bWaterEnvironmentMapping 1
set g_bEnvMapRenderClouds 0
set g_bEnvMapRenderFocusObject 0It seems focus-shadows and cockpit-shadows have been consolidated under a single option for shadows? It’s a shame to lose cockpit shadows (99% of the only shadows I’ll ever see). Unless they are somehow responsible for the perf hit on DX11, in which case I’ll gladly take the higher frame rate / lower input lag.
-
I’ve got a pretty significant performance decrease from 4.34 as well, 25% almost. While arty is right, frame rate isn’t everything, I do chase at least 60 fps in every combat sim I play as a minimum. I find 60fps allows the smoothest trackir experience. 30 fps in FS2020 is fine because you’re just watching the world go by. Looks like I need a new ryzen cpu myself.
-
Ghastly, what cpu do you currently have? If I recall correctly, don’t you have a 2080 super gpu? I thought that you would be fine.
-
Agree, below 60 is where the choppiness of panning the view breaks the sense of immersion. Maybe 50fps would be ok if it were really solid and consistent… and with a VRR monitor… one could get used to it.
In my case, the fps was varying significantly from 40 to 70… based on what, I couldn’t figure it out?
I had a good clue … hitting [Shift+2] to toggle the cockpit rendering made a huge boost. Now I guess I know, my fps was probably dependent on the angle of the sun/moon and time of day. (cockpit shadows)
Ghastly – have you tried turning off shadow mapping?
-
I’m glad to be born in the late 70’s and to have known the CPC6128, AMIGA500, PC486DX33 … so I can be extremely happy and satisfied now with what I have, even with 30-40FPS.
-
That makes two of us on this one!!!
-
I have seen a 20-30 fps bump myself and that was stock with no changes. I have a nvidia 1070 with 8 meg ram.
-
This post is deleted! -
Ghastly, what cpu do you currently have? If I recall correctly, don’t you have a 2080 super gpu? I thought that you would be fine.
Hey Scott! Long time, hope you’re well! I have a ryzen 2600. It’s definitely my bottleneck, at least for the way BMS now uses CPU. At 4k in the benchmark, my GPU is 30% utilized.
Agree, below 60 is where the choppiness of panning the view breaks the sense of immersion. Maybe 50fps would be ok if it were really solid and consistent… and with a VRR monitor… one could get used to it.
In my case, the fps was varying significantly from 40 to 70… based on what, I couldn’t figure it out?
I had a good clue … hitting [Shift+2] to toggle the cockpit rendering made a huge boost. Now I guess I know, my fps was probably dependent on the angle of the sun/moon and time of day. (cockpit shadows)
Ghastly – have you tried turning off shadow mapping?
I have thanks to you. from 29 fps to 52 fps in the benchmark TE. I may have to leave it off.
I’m glad to be born in the late 70’s and to have known the CPC6128, AMIGA500, PC486DX33 … so I can be extremely happy and satisfied now with what I have, even with 30-40FPS.
I’m absolutely not ungrateful for the work you guys do to keep Falcon going, Dee-jay. Just trying to make the most of my relatively new hardware.
I have seen a 20-30 fps bump myself and that was stock with no changes. I have a nvidia 1070 with 8 meg ram.
I’m getting 23 fps on the ground in a campaign on a 2080 Super. I’d have had a negative framerate in 4.34 with your kind of bump
-
I’m glad to be born in the late 70’s and to have known the CPC6128, AMIGA500, PC486DX33 … so I can be extremely happy and satisfied now with what I have, even with 30-40FPS.
I too am a child of the 70s but somehow more easily spoiled.
Btw just want to clarify that none of the bugs and nitpicks and minor perf regressions I’m posting should be interpreted as complaining – I’m HUGELY happy with the major update (has it been 5 updates in past 12 months? a record?) and glad to see there’s been a driving force for simplification on all those overly-complexified graphics options – even if it means I have to turn off shadows … I’ll mostly never notice.
My only motivation to hash out quirks like this in the forums, is to help others with similarly older gen hardware that may be in the same situation.
-
Shadows have been always a fps discussion.
Rather to uncheck that I suggest to point at hdr off option.
Also, leave falcon do the work for graphic, for GPU it needs AA set to 4x and AF to 8x if you have a good monitor.
On GPU settings control panel pay attention on energy saver.Happy flights
-
As a long time Falconeer and a “FPS chaser” since ever, let me try to help. I would like to make sure that you aren’t chasing ghosts here with GPU settings…
My system:
i7 9700K CPU @stock speed
32GB RAM (although with 4.35 16GB or even 8GB won’t make a difference…)
GTX-1080
2560x1440 @75Hz
ALL graphics options enabled in BMS config including Highres textures and “shadow on smoke” under shadows checkbox
Multi Sampling within BMS set to level 8
V-Sync disabled (Check below for my recommendations)In Benchamrk TE on the taxiway I get:
Overall FPS - ~44
Sim FPS - ~45
Renderer FPS - ~145So, before you go on and chase your GPU, please make sure that you have a Renderer FPS problem. If not, then just leave your GPU alone, he is OK
My settings are simple:
1. Go get Nvidia latest drivers
2. Install and reset all settings to default
3. In Nvidia panel make sure power usage is aimed to “Maximum performance”
4. In Nvidia panel put Anisotropic filtering (aka AF) at x16
5. In Nvidia panel disable V-Sync (If you want you can keep it on but know that it’ll limit your FPS to the monitor’s refresh rate)
6. In BMS itself Setup Graphics screen set Multi Sampling and put it on the level that suits your GPU (I use x8 here which is OK for my GPU and resolution, you may reduce to x4 or x2 if 8 is too much)PLEASE do NOT force Anti-aliasing from within the Nvidia panel, from my experience that is worse for both performance and and quality than the internal Multi-Sampling setting (And if you think it’s not then just keep it, but then you may pay too much in FPS for the little to none extra quality…)
These settings worked fine for me with both this setup and my older card (GTX-1060 3GB on FHD resolution)
If you are looking at GPU problems, please first check your Renderer FPS, if it’s high and you are getting low Sim and total FPS, then your CPU is the bottleneck.
Just to make sure everyone is aligned regarding the new FPS counter:
1st line - Total FPS
2nd line - Simulation FPS - In large you may think of it as your CPU FPS
3rd line - Renderer FPS - GPU FPSBecause with the new engine (which isn’t only DX11 but a TOTAL new engine that was written from the ground up using state of the art methods), the Renderer is (almost, there is always some) totally independent from the simulation, and so it runs at its own pace.
For AMD users, sorry if this post is Nvidia oriented, that’s all I know in last years but basically you should act similarly with your AMD setup. I used to have A R9-280X and I used same settings (But Multi-sampling level 2 or 4 maybe, in 4.33) and picture quality was good.
-
Thanks I-Hawk – what is your take on the g_nAnisotropicValue in bms cfg? Do you leave that ‘0’ then override to 16x in NVidia control panel?
set g_nAnisotropicValue 0 // The max anisotropic filter value to use if anisotropic filtering is ON in the setup UI. Valid values: 0 = max available (default), 2, 4, 8, 16
This is first I’ve heard anyone draw a distinction between letting the app handle AA but the graphics driver handle AF… curious to learn more, why the difference in advice? (I’m a software engineer by trade… but no real experience in 3D game development or profiling.)
My gpu render times are 6-7ms … but my cpu times are up around 20ms (this is with g_bShadowMapping=1). My monitor is 100hz max (g-sync) so my goal is to keep the cpu and gpu frame times at or around 10-12ms range. Realistically I’m happy with anything 70+ if it’s stable, consistent and pleasant looking.
Anyway, for now, setting g_bShadowMapping=0 gets me back into the 80-100fps range, and I’m happy with that. Just looking to learn more… and learn where best to focus $$ next upgrade. ie. It’s clear I’m cpu-bound, but does BMS need raw computational speed or higher memory I/O bandwidth?
I gather a lot of the cockpit must be rendered in software (things like the HUD, MFDs, DED, etc) and those textures then passed over to the gpu with every frame? I’m wondering if something like that is my bottleneck, on my old DDR3-era system.
All I know is, hitting [shift+2] and [alt+C,H] to turn off those MFD/HUD elements instantly reduces my cpu frame processing time by about 3-4ms. (Same for external views too actually.)
OS: Windows 10, 20H2
CPU: Core i7-3770, ca. 2010? not overclocked, Hyperthreading OFF
RAM: 32GB DDR3, 1600MHz
GPU: Nvidia GTX 1660 Ti, ca. last week
Monitor: G-Sync, ultrawide 3440x1440p @ 100hz