Hi everyone I had installed the flybywire mod since release because of the more functional Airbus, today I deleted the mod and also all the 5 liveres I had and the performance was incredible.
I didn’t touch anything in graphics I have set everything in ultra with render scaling at 170%
Certainly don’t have any massive performane issues with the A320NX. Infact there is very little difference between the default aircraft and FBW’s, and i don’t have anywhere near a top range rig with as follows. I would maybe look elsewhere for your issues.
My specs AMD Ryzen 7 3800x
32gb DDR4 Ram
MSI 570m Pro
Power Colour RX5700XT which returns 30-35fps in the cockpit, no jitters 60 -70fps at alt external view, 30-40fps on approach in A320
whats your screen res and having render scaling at 170% could be the problem
i have a 5600x 3080 32gb of 3600 ram and i get around 40fps at 1440p running ultra with 100 render scaling using the fbw a320
Which fly by wire mod are you using, you know there are now three of them? You need to read up on the cfbw to understand what is happening to really make the A32NX an outstanding performer!
Without stating what resolution your running at doesn’t really help either, if your 1080 or 1440 running at render scale of 170 is going to worsen performance, as your rendering above your native resolution
You are correct the FlyByWire mod eats up considerably more frames even sitting cold on the apron. The reason being is as soon as you hit Fly Now the plane is loaded into the sim and physics engine comes to life. You can see just sitting there in the mod that it consumes much more frames just running the physics alone. When you power on the individual (non shared) displays it will consume even more frames and start running even more scripts.
There is room for optimization here and it should get better once the sdk is enhanced to allow 3rd party full access to some of it’s functions like the shared panels as one example they mentioned. I really do love the mod though. It’s hard to go back to the stock plane but the framerate like you said is much better on stock and this is by design too.
Most people who don’t notice the FPS hit on the mod are running very high end rigs with i9 and high end GPU. To the mid and high range the FPS is very apparent. I don’t need the tools to even notice the drop in FPS on the mod. It’s very apparent as soon as it loads how many frames it eats. You can always test this for yourself too. Stock 320 plane will be much better for VR users so its very important she flies well this next update.
Of course there is, have you never heard of anti-aliasing (or supersampling)?
200% render scaling looks massively better than 100% in some cases, especially for 1080p and other low resolutions.
By following their Github for some time now I can see that they are mainly focussing on features and issues at the moment with a couple code optimizations here and there.
I personally expect a general code review before they release v1.0 after all features are implemented. Which should reduce the system load. But I’m surely not an expert in software development but from my observation this is a normal thing to do before you release a software (e. g. beta stage).
I wouldn’t bet on it since the GPU usage is only at 68% in the screenshot. If anything he should be able to raise it above 170 and not lose a frame in this exact spot.
I have nothing against fbw their are a great team who provided us a better and more realistic a320 I just stated the performance issue which I’m sure they get it fixed
I’ve noticed a performance hit using the mod, but specifically the Dev version. My guess is because that version has in-development code and perhaps debugging code or verbose logging.