-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default Upscaling is broken in 1.4.0 #96
Comments
My system specs: I uninstalled Quake 2 RTX and deleted the game folder from C:\Program Files (x86)\Steam\steamapps\common, then I redownloaded it. Same issue occurred with mostly default settings. I only changed Antialiasing and Resolution scale (same behavior in both Windowed mode and Fullscreen). https://steamcommunity.com/sharedfiles/filedetails/?id=2323195151 |
Sorry, can't reproduce. Upscaling works as intended in all modes, tested on 20 and 30 series RTX GPUs. And I see other users on the Steam forum can't reproduce this either. Maybe you have some non-default setting in the Nvidia Control Panel that might affect texture sampling? Or some other additional software?... |
I tried default settings in Nvidia control panel, except that GSync was active and vsync was forced on. Other running programs were Bitdefender and Stream Deck software. This issue also never occurred with the previous version. (I have about 100 hours in Quake 2 RTX this year). I just double-checked, and the issue only presents when TAAU is off and Dynamic Resolution Scale is ON and set lower than 100%. Scaling works normally if DRS is off. I hope that helps more. |
That was it - thanks! Fixed in 7330ad7 |
If you disable TAA and use a resolution scale lower than 100%, there is no longer any upscaling as of 1.4.0. Instead, the game is rendered in a smaller window with junk and the HUD filling the rest of the screen. This happens in both windowed mode and exclusive fullscreen. It also affects both Vulkan and Nvidia extensions.
https://steamcommunity.com/sharedfiles/filedetails/?id=2322338166
The text was updated successfully, but these errors were encountered: