FSO vs. Exclusive Fullscreen

[daviddave1]

I couldn't do it with this method. But this is not the only method.
It is possible that another person will have more luck.

Thank you dude! Fr33thy couldn't do it also ( on Server 2019) but he told me that on the latest Windows Builds FSO is the same now as Exclusive Fullscreen with inputlag. ( he said a mate of him tested it)

[R1sk]

@1000WATT
I restored my Children folder with gamebar and set "Flags" to 211 hex....it still doesn't work unfortunately. Have you managed to get FSE back?

Flags to 11 Hex not 211 Hex who said 211 and why?

[eliasballz]

Borderless Fullscreen with FSO on Apex Legends leads to minimum additional 1 frame latency.

On this note, just to be clear on my previous comments to everyone here, when I was talking about FSO vs. exclusive fullscreen, I was talking about FSO on + game set to exclusive fullscreen vs. FSO off + game set to exclusive fullscreen only.

- Game set to "borderless/window" + FSO on = borderless/window behavior (retains DWM composition + Fast Sync-like V-SYNC solution)
- Game set to (exclusive) "fullscreen" + FSO on = exclusive fullscreen behavior (with allowance of adaptive DWM for overlays/alt+tab transitions + tearing with in-game or CP V-SYNC off)

I've seen DSI/DSR scaling quirks sometimes occur with the borderless scenario (vs. borderless + FSO off), however (may have been addressed since though, or was game specific; primarily saw this in Sunset Overrdive which only supports borderless).

Anyway, due to DWM, borderless/window does indeed add 1 frame of latency over exclusive fullscreen:
h


For the most responsive experience, borderless/windowed (FSO on or off) must be avoided, and exclusive fullscreen (FSO on or off) must be used instead.

Obviously, exclusive fullscreen isn't always an option though, so borderless/windowed G-SYNC mode is the next best bet, as it appears to bypass DWM in that mode regardless (I will test this again in the latest Windows build for confirmation when/if I receive an LDAT from Nvidia):




Finally, during my original G-SYNC 101 tests, I also tested all combos of Game Mode, Game Bar, and FSO off-record, and found no measurable input lag differences. See:
viewtopic.php?f=5&t=3441&start=10#p26839

For the record, I know my "G-SYNC 101" article only evokes "G-SYNC" when people see that title, but in actuality, it fully covers G-SYNC, double buffer (and to a lesser degree triple buffer) V-SYNC, Fast Sync, V-SYNC OFF (no sync), exclusive fullscreen, borderless/window, and in-game/external FPS limiter scenarios (and across 6 refresh rates).

hey, i saw your post on the actual blur buster website and saw a guy "shadowlord" respond to you saying he a had a problem with marvel rivals. i wouldve responded there, but i cant send pictures of my benchmarks while running the game. i have a ryzen 7 9700x and a 3060 rtx 12gb and my system is obviously gpu bound and my gpu sucks. im playing on a 240 monitor that has gsync. so im stuttering, or tearing, or something. i used to have unstable fps with stock settings, but i got it to a point where i got stable fps and a stable frametime at 120 fps (even got it to be stable at 140 and 180 before. but i undervolted a bunch thinking it was my gpu usage being a problem) im so frustrated and need help. its been about a month of trying to get rid of these stutters and tears. from the bios turning on pbo and global c states (obvi did ram, expo), to nvidia profile inspector, to msi afterburner undervolting, and underclocking and rtss framelimiter. the images show i have gsync on and vsync off. (after reading your post, i will be trying both on also with vrr? if thats what you meant about vrr in your posts on the blur busters website) i notice fps and frametime spikes with some settings, but even getting rid of them with certain settings, i feel stutters and i even teleport in the game (even the practice area). here are my current settings in the pictures (game mode, hags and vrr off, fso not disabled) along with a benchmark of the game running

nvcp settings

image.png (107.91 KiB) Viewed 3016 times

nvcp settings

image (1).png (83.5 KiB) Viewed 3016 times

msi afterburner settings

image (2).png (51.33 KiB) Viewed 3016 times

[eliasballz]

sorry, i couldnt add more than 3 images. but here is my benchmark as well

benchmark

image (3).png (45.67 KiB) Viewed 3016 times

rtss settings

image (4).png (5.48 KiB) Viewed 3016 times

[jorimt]

the images show i have gsync on and vsync off.

G-SYNC on + V-SYNC off can still tear. 100% tear-free G-SYNC is G-SYNC on + V-SYNC on.

(after reading your post, i will be trying both on also with vrr? if thats what you meant about vrr in your posts on the blur busters website)

"VRR (Variable Refresh Rate)" is another term for G-SYNC, FreeSync, adaptive sync, etc. They're all the same thing, fundamentally.

i notice fps and frametime spikes with some settings, but even getting rid of them with certain settings

G-SYNC can't reduce or prevent system-side frametime spikes.

All it does is dynamically steer the tearline offscreen for framerates within the refresh rate when properly configured. It's not a "smoothing" mechanic or a system performance enhancer. It essentially aims to be V-SYNC on with latency closer to V-SYNC off, and that's about it.

i feel stutters and i even teleport in the game (even the practice area).

Teleporting would be more server/ISP than system-side; rubber-banding, ping, etc.

[Slender]

I can’t go back to g-sync off / v-sync off, even though when everything works as it should it doesn’t matter.

[1000WATT]

(good luck getting Microsoft to replicate it and fix it though )
That said, my commentary in this thread thus far has been entirely based on the presumption that FSO is working as intended in the posed scenarios.

year2020
Somewhere in the Microsoft office.

Olivia: These guys from the blurbusters forum are always unhappy about something. Something needs to be done.
Isabella: Yes, they don't like how wddm works.
Olivia: Aren't we doing everything we can to make FSO mode perform better and be more comfortable than FSE mode?
Isabella: This will require large financial investments and the involvement of highly qualified programmers.
Olivia: There must be another way!! Find another way out!!!

year2024
Isabella: We have done a truly outstanding job and are pleased to introduce WDDM 3.1 to you. https://youtu.be/mUB6YLuJRZk
Isabella: After we broke FSE, no one will argue that FSO is inferior in any way.
Olivia: This is an amazing decision, I'm proud of you.Finally those guys from the blurbusters forum will be happy.

[ManWhoSoldTheWorld]

@1000WATT - Your overlay says «Legacy Flip» in the YouTube clip

[Z3CrosS]

.

[Z3CrosS]

.