FSR3 Frame Generation only applied to main window in multi-window set up

Good catch there! they have done this in another SUbeta but fixed it quite fast. I’ve used to run FSR3 on my RTX3090 with impressive results on my 2x 4K TVs. then upgraded to RTX5080 and there was no need for FSR3 cause now using DLSS Quality 4.5. This produced significantly better image than FSR3 with a performance boost as sell using frame gen x2! You might want to make sure you have also updated the FSR3 files within the DLSS swapper tool!

This is not a work around - The issue is simple and the thread should be kept on topic to avoid it drifing into a discussion as opposed to a bug report

1 Like

Hi folks,

There seems to be a lot of comments and various discussions here after the initial bug report. Can those of you who were experiencing the original issue around Frame Generation on multi-window set ups has now been resolved, or is this still an issue that may need further investigation?

Thanks
The MSFS Team

Not resolved - FSR3 Frame Generation is not applied to additional windows without toggling FG settings each time MSFS is launched.

Also, please notice the significant pattern of issues in SU5 Beta are about Settings not being saved, or applied, correctly - the Settings system, under the hood, is not working as intended and breaking lots of things.

3 Likes

Understood, thanks for the further information. I’ll get this logged now!

1 Like

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.

5 Likes

Confirming that with today’s release of SU5 v1.7.7.0, this issue still exists.

In Graphics Settings, Frame Generation set to FSR3, the frame generation is NOT applied to additional windows - meaning, the setting is not being read or obeyed.

Every time you launch MSFS, you have to:

  1. Change Frame Generation to None
  2. Save the setting
  3. Return to Settings
  4. Change Frame Generation to FSR3 again
  5. Save the setting
  6. Open a flight.
1 Like

Can confirm this also - Every launch I need to go through this process. It appears something is not sticking in the settings or is being reset on exit/startup.

Would be nice to see this marked as BUG LOGGED as its easy to reproduce and clearly not a new feature :slight_smile:

1 Like

ISSUE DESCRIPTION

When using three monitors in Flight Simulate 5, both the left and right side displays experience severe stuttering whenever a flight is started on the ground. To fix it, I switch both side monitors from full screen to windowed mode and then back to full screen. Once that’s done, the stuttering is completely gone and everything runs smoothly. AMD FSR 3.6 frame generation.

FREQUENCY OF ISSUE

On every flights

REPRODUCTION STEPS

  1. I start a flight on the ground

  2. Observing big stuttering on lateral screens.

  3. To fix it I switch both side monitors from full screen to windowed mode and then back to full screen.

YOUR SETTINGS

No mods and add-ons, community folder empty.

With or without using Developer Mode

Nvidia RTX 5080

AMD 9800 X3D

MEDIA

Link to a video of the problem

Did you try to toggle windowed mode - full screen again on the lateral screens ? That solves the problem for me.
9800 X3D / RTX 5080

I wouldn’t say it “solves” it. It’s a temporary work-around, which one must do every time. We still don’t know why settings are not being saved or applied correctly, and users should not be expected to do this kind of constant toggling of settings every flight. There is a chronic issue of Settings not being saved correctly - so the more often settings are being changed and saved, the greater the risk of corrupting them in its currently fragile state.

So it’s still a serious bug in my opinion, and settings should be saved and applied correctly in the final release of SU5.

Of course it’s en temporary solution. “Solves” was not the correcte word indeed.
But given the problem is not in all the previous versions it should be corrected easily. At least if our voices can be heard…

In the meantime I set on Right CTRL + space the windowed/full screen mode so it’s fast to “fix” it, and it works also on the menu before the flight.

In default on the keyboard this is since day one mapped for left alt + enter keys even in 2020 to switch between these fullscreen and windowed mode.
But also you must also in Windows set the screen option to remember on which monitor or tv is placed and this is not by default but a very important Note to the side with mentioning. As it is important to allign the screens here no matter where you place them on your desktop.

Still not marked as bug logged……….

This is why I believe nobody on the “Microsoft Q&A Test Team” or at Asobo uses triple / surround screens. This problem is simple to reproduce, and is a clear regression, but hasn’t been “bug-logged” so far.

I know we are a minority sliver of the user base, but we invest a lot of time, effort, and money in trying to have peripheral views and improved immersion - as many other simulation / driving titles provide. I hope eventually someone at Microsoft or at Asobo values the triple monitor experience. The Wishlist item for better multiple monitor support has hundreds of votes…

2 Likes

Is anybody able to confirm if this has been fixed on the most recent build (1.7.9.0)?

Again, I note this thread is not BUG LOGGED which is just bizarre as its so easy to reproduce.

This bug is NOT addressed in v1.7.9.0

I am actually quite upset that this very easy to replicate bug has not be bug logged by the unseen secret Microsoft team who bless or dismiss our bug reports.

This bug is a regression, 100% reproducible, and affects simulation.

I am starting to wonder why. I have noticed that they never engage on anything to do with multiple monitors, so, are they under-equiped or not knowledgeable enough to test it? Will they at least notify Asobo? Is ANYONE at Microsoft or Asobo using triple screens?

1 Like

Edited:

OK, now I’m very frustrated with Sim Update 5, and with the bug reporting process.

As of v1.7.6.0 (the first SU5 Beta version), FSR3 Frame Generation stopped working on additional monitors - but there was a work around: you could toggle FG off, save, then on again… and FSR3 Frame Generation would be applied to additional screens for your flight, and you would have to repeat each time you launched MSFS.

But as of v1.7.10.0 the above work around also NO LONGER WORKS. So now it is a compound regression, which breaks the functionality of Frame Generation on multiple screens and leaves no work around. We are out of luck, and not yet “Bug Logged”.

Agreed - This is now more than regression, this is a bug. Its concerning that its not listed as a bug. The cynic in me things this is the start of three or four SU’s that are going to stop Frame Generation working on multi monitors, which is going to be massively problematic for all of us who use multi monitors.

Can the CM’s please provide an update on this bug? Has it been acknowledged? There aren’t that many bugs being reported in this SU so you’d think tracking them would be easier than in previous SUs.

Hi @Airbumps2502,

In regards to this issue being acknowledged, when a forum thread becomes feedback-logged, this means it has been internally logged for investigation by our testing team. If internal testing or investigation discovers a bug in relation to this report, the forum thread will be updated to bug-logged.

I’ve ensured to update the report on our internal system to let the testing team know that this issue is still present in v1.7.10.0 for them to further investigate. If there is a status change, we will ensure to update this forum thread accordingly.

Thanks
The MSFS Team