With SU5 being written for XBox which has AMDs version of resizable bar, direct access for the GPU to RAM in large blocks (or something), I wondered if the closed-case of resizable bar not helping, might be reopened.
I updated card bios and mobo bios. Precision X1 shows resize bar enabled, so the system is good to go.
MSFS doesn’t support RB, or rather, it’s not on the NVidia whitelist of games. However there’s a published way to modify the driver profile to enable it using NVidia profile inspector. That’s what I did.
I booted up with the default settings, no RB, with multiplayer off, clear weather, xcub at Meigs field, looking north, in cockpit, engine and avionics off…just spawned in. Identical situation with RB off and on, after relaunching the game.
The numbers bounce around, but those were the values I captured with my cell phone cam.
Not a huge improvement, but definitely not a reduction as was reported previously. I flew around with it on and could find no downside. I plan to leave it that way and see if I notice anything bad.
If anyone else experiments with this, post your results and impressions.
IMHO it’s never a good idea to force a setting through the drivers, if it was of any benefit the developers and nVidia would have enabled it by default.
Hopefully it means NVidia will enable this by default. I’m just experimenting since the major graphics engine surgery in Xbox/SU5 and the original recommendation of “no rebar” might be different now.
Hoping other adventurous souls try this too and reproduce my results or not.
I’m not really sure what you are trying to accomplish with this.
From my experiece a difference in performance that tiny is hard to test and recreate reliably. So this all might be a placebo effect. Also a difference of 1.3 fps is pretty irrelevant in every day life. And it is especially irrelevant when you are already running close to 60fps since you won’t be able to notice a difference above 40 fps anyway.
