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

Can you please confirm that the “internal testing” team can and will test with triple screens?

There is a small but dedicated segment of MSFS users who do rely on triple screen functionality. Since the launch of MSFS 2024, the basic functionality that had existed for triple screens in 2020 has step by step been removed or eroded to the point where - speaking for myself - I’m quite nervous that the intent is to remove it entirely, which would make my rather significant investment in a capable PC and triple screens… regretful.

1 Like

I do not personally know the exact specifications of every single testers setup, however I can confirm that I have passed the information about this issue pertaining to multiple monitors to the team.

Thank you. I wasn’t asking for exact specifications. I was asking for some reassurance that someone - at least 1 person - in the entire MSFS / Asobo testing ecosystem, is using triple screens, and therefore our bug reports can be verified and fixed.

I would like to formally request that you ask, on our behalf, if possible?

For those of us who built our systems around triple screens, the incremental regressions are forming a pattern - starting with removing the ability to view a scene while aligning, and now the latest removal of Frame Generation.

It seems reasonable to assume that nobody in the MS / Asobo ecosystem is using triple screens. If they were, these issues would be equally apparent and problematic for them, and I assume would be acknowledged and hopefully put on a list to fix.

2 Likes

GimbalAxis and others, thanks so much for fighting for us triple monitor folks who count on Frame Generation to make an amazingly smooth, immersive, and impressive flight simulation experience. I focused on VR for seven years but got tired of the isolation and inability to quickly show friends what our MSFS24 can look like. My grandkids love the ease that they can really see what flying is like. The low cost ($250 per 60Hz monitor works fine) is entirely easy to set up. Microsoft/Asobo must realize that when they want to demo their wonderful product, you really can’t beat triple monitor - not VR or ultrawide.

Thanks again for your constant testing and reporting to our moderator. Things are working so nicely on SU4.

1 Like

This thread has now been updated from feedback-logged to bug-logged after successful reproductions by the testing team.

Thanks for providing your reports to help identify this issue!

3 Likes

Thank you. I assume that means at least 1 person in the MS / Asobo ecosystem uses triple screens (or at least recognizes that it is a legitimate user expectation that should be supported)?

As mentioned above, this has been bug-logged now after successful reproductions of the specific report provided to the testing team.

2 Likes

Good to know. Thank you Chewwy94.

At least the CDT when ending the flight with pop-out windowed on AMD FSR3 is solved.

Not better on the new SU5 beta…

Arh - Thats disappointing. I feel like this is one that’s going to slip into the release version and be one of those classic Asobo regressions that gets parked and forgotten about.

Of course as seems to happen with all SU Betas, the CM’s will “archive” the beta forum threads so nobody can see them anymore and there won’t even be a public record of this thread ever existing….

This is incorrect. Once a Beta ends, CMs are reviewing open reports and many of them are moved the Bug Reporting Hub (including votes and users contributions). If you identify a report that has not been moved please send a DM to @moderators so that we can review and take appropriate action.

1 Like

This issue is “game breaking” for some of us with triple monitors. If it’s not fixed during the beta, it means we will be out of luck for at least several months.

1 Like

Thank you for the correct - Perhaps this is a more recent change as I’m sure I read following previous SU a number of bug threads were closed and lost. Good to hear thats not the case.

No mention of this issue being addressed in today’s v1.7.16.0 update.

FSR3 Frame Generation worked on multiple monitors prior to SU5, so this bug is a regression. It has been broken in SU5 for some time now.

1 Like

Yep. Still the same issue… So frustrating. Please Asobo read us !!

1 Like

Can someone please explain to me how yous manage to line up your monitors. It is practically impossible in MSFS2024

Agreed! This regression is significant and was introduced in SU5 Beta. It really must be fixed prior to a proper release as it renders the sim largely unusable on a triple 4k setup.

1 Like

This is a very serious problem.

It’s disappointing that FSR3 FG can’t be used in multi-screen mode, especially since we can now enjoy detailed scenery.

Previously, when DLSS video glitches occurred in the beta version, they were fixed quickly.

While the Steam version of MSFS2024 allows switching between SU4/SU5 beta by creating a folder copy, we need to consider how to save SU4.

Even though this bug / regression earned “Bug Logged” it is obvious to me that nobody at Microsoft or Asobo is using triple monitors.

Their entire focus / priority over the past 2 years has been to get MSFS on console, cloud, and hand held devices (Xbox, PS5, and Asus hand held thingy).

The experience of MSFS flight simulation - like other driving/simulation titles - benefits greatly from extending screens to peripheral vision. But starting with the inexplicable UI for setting up additional windows/screen in the Settings > Advanced section, to breaking of FSR3 Frame Generation, it’s quite obvious nobody at the developer level is paying attention to this - if they were using triple screens, they would immediately be faced with the issues, and (presumably) proceed to fix the issues.

I think it’s safe to say that those of us who save and invest in more screen real estate - which is a significant expense when you include upgraded PC hardware - are feeling a bit nervous that MSFS will abandon extended screen support. We need some reassurance, please.

3 Likes

Agreed. Obviously once SU5 is released (presumably with this regression included) I’ll be looking to back to 2020 or see if Optiscsler cam fix it