Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
DX12 has been nothing but issues for gaming.. I always had better performance in real fullscreen, sucks being forced to use windowed fullscreen.
AFAIK Vulkan and DX12 don't support FSE either, again because deprecated tech. The reason FSE existed in the first place was due to limitations in windows that no longer exist.
* It's not actually borderless windowed, it's a FS non-exclusive mode that's different than the old borderless windowed method games used which was to just set a flag that hid the title bar. This mode is, from a performance standpoint, the same on windows 10+ excepting cases in older versions of DX where the developer added specific optimizations for the specific OS version and display adapter which isn't necessary in proper DX12 implementations.
Good to know. I was upset about no Fullscreen too because generally I had better performance in Fullscreen over Borderless Window.
this fix seems to work consistently to fix any remoteplay formatting issues, it seems to run faster too... although im not sure if its REAL exclusive fullscreen, but it atleast gets the formatting correct, no black bars, stretches to fit (im using non-native res on win 10 for my phone, so games recognize that res, but it only works if the games support exclusive, because win 10 desktop formatting is wonky, scales to fit, doesnt stretch, so the black bars are rendered as part of the image unless you have an exclusive fullscreen game) and seems to be exclusive, so im betting it is. just takes launch commands and modifying the config file. but it should effectively work every time after that. although dx12 could always be using those commands to emulate exclusive by filling the black bars by smushing and stretching the image, which is FINE for my phone, as it stretches to fill the same screenspace with app settings making it effectively 1 to 1. the black bars are an issue with borderless when youre using a non-native res. im doing this so i can use my 2300x1080 phone with a pc that only has a 16:9 1080p display, it works fine if fullscreen as the games smush to fit and stretch on my phone making it effectively perfect. but win 10 as i said, doesnt format the same way. so i get black bars on top and bottom and an extra stretched display, or in cutscenes a black box. basically i require exclusive fullscreen to play games as intended. exclusive allows any wonky setup to work fine as long as the device your casting to is of that resolution. but windows 10 and borderless doesnt see it that way.
It doesn't.
You can bypass/extend dx12 to get FSE in an otherwise dx12 app by using a combination of legacy windows API settings (known as the "blt-model") along with third party vendor video card APIs, but DX12 by itself does not support the blt-model (bad things happen if you try to set those legacy settings without making use of the above mentioned third party apis).
Of course doing that actually performs worse than using the current flip model (which does not support FSE at all). So while you can do a bunch of extra work to get the old FSE in a modern app, it'll be for worse performance. There's a few use cases where this is necessary, but gaming isn't one of them.
That's why HWL doesn't support it and why most later DX11/12 games don't (though some will mock it by locking the mouse to the window and disallowing "outside" clicks from swapping windows only allowing it for alt+tab, in which case the user typically can't tell the difference). A bunch of extra work for less performance is generally a no-go proposition.
technically it does, if your issue is formatting.... what i explained actually fills out any black bars and makes the game run fullscreen effectively.... performance is debatable as the game runs great on a 10 series without rtx enabled at max. black bars is what im speaking of, and it is running exclusive as it takes over the windows screen settings and gets rid of them. less performance through benchmarks i could not discern, it was within 5 fps give or take, so a nonissue. my issue is nuanced as im using a nonnative res on a display to remote to a wider device, my issue was formatting not performance. but i think it is running exclusive through forced commands and cfg modifications. as it stretches to fit the screen vs black bars that render INSIDE my remoteplay app (which gotta be honest is pretty bad). btw because of the slightly higher render res, im using intel scaling.
im noticing 0 downsides in performance, usually upsides, but im also using an older card and not using rtx. infact increases in performance if anything. but exclusive fullscreen is a nessascary thing for remoteplay, it allows for screen resolutions to be set, which can be important in fixing nuanced issues with certain applications, especially games. idk anything about the performance model, or how it performs, i just know it works better for specified application.
That's not FSE.
its a modified resolution, but its effectively fse if you want the formatting to render properly on OTHER devices, and not for performance or other benefits. which is effectively what it makes it work on weird setups. my only issue was the black bars, that got rid of it. idk what setting fullscreen to 0 and setting launch commands to exclusive did, but it made the game format as i intended, and work better on my devices..... so if your issue is widescreen and weird setups not formatting properly, thats the way to fix it. my intention is getting rid of black bars, and that is the fix for that. if or if not it supports real fse is true or not doesnt matter, it supports something LIKE it if you modify abit, making it work with weird screen setups if you will. if its ONLY rendering like that because i forced it to render over the black bars, thats fine, it now fits my setup without bars surrounding it.