Massive Frame Drop from 4.32 to 4.33
First of all thanks for 4.33, but I have not been able to enjoy it much. I had 4.32 running well (some of the eye candy stuff off but smooth), but 4.33 FPS is <50 going down to 20 in the first training mission with everything off (everything means all the shades, auto gen, anything that could be off or low). I understand 4.33 is more FPS hungry but that much? I also find strange that FPS drops considerable when I look down at the cockpit but not at the clouds or ground even with auto gen 7. Outside view gives FPS >150. Pulling G’s also gives a massive drop (any way to turn the condensation off?). 32 or 64 doent seem to change much. Clouds also dont seem to be the problem. 4.32 still running smooth.
My question is: should I expect this performance from my system or there is something else wrong? Any suggestions on how to try to fix this?
Thanks in advance,
OS Name Microsoft Windows 10 Home
System Type x64-based PC
Processor Intel Core i5-3350P CPU @ 3.10GHz, 3101 Mhz, 4 Core(s), 4 Logical Installed Physical Memory (RAM) 8.00 GB
Name NVIDIA GeForce GT 620
PS: I am not too computer savvy.
So I was reading another post about frame drop and found a solution to my problem.
As suggested by 91861, I added the line: g_bUseShaders 0 to bms.cfg and my FPS jumped from 30-40 to 60-70 and everything is smooth again. Before anyone asks, I had turned off all the shaders in the configuration window but this extra line made the difference to me, don’t know why. I was suspicious of the shaders because when I looked straight up to the sky and clouds I would get +20 FPS and when I looked straight down to the ejection seat I would get -20 FPS.
I hope this can help other people.
Again thanks for 4.33.
does it look huge different to u when shader off?
Confirm! I also added the line: g_bUseShaders 0 to bms.cfg and FINALY managed to run 4 33 smoothly in my laptop! No trees though… Also i observe some stuttering in runways while viewing them from high altitude but apart from that everything else works fine. The Shaders are fps “hungry” and obviously low end PC’s have a hard time to keep up with the demanding 4 33 graphics!
Based on this thread, I ran comparison testing with and without “set g_bUseShaders 0” in the falcon bms.cfg file. There were moderate gains in frame rate.
HOWEVER, it also disables rain effects completely. But much worse, it also introduced really bad graphical artifact jitters outside the plane while in the cockpit when operating in inclement weather conditions.
Your experience may vary.
I should also add that after adding the line the runway and buildings started flickering which they don’t do without the added line. I suppose some tweaking with the video card may help but after a few tries I could not get it to stop flickering.
If someone knows how to stop the runway and buildings to stop flickering I would appreciate the help.
that was a pretty bad line to add, it literally killed the beauty of this sim’s graphics.