Ithronwise Posted April 14, 2021 Posted April 14, 2021 Hi Aviators, AMD VSR doesn't work anymore in DCS World 2.7. I have an 1920x1080 Screen and have set a resolution of 2560x1440 in DCS graphics settings with activated AMD VSR in the radeon settings. Right after the update DCS ignores any resolution settings and runs only with the native resolution of 1920x1080 no matter what resolution is set. I already deleted the fxo and metashaders2 folders, ran cleanup and repair but nothing helped. I also have the impression that all graphics settings like MSAA or SSAA are ignored now. At least I couldn't see any difference between MSAA 2x and MSAA 4x or between SSAA Off and SSAA 1.5. Best regards, Rene ASUS ROG Strix B450-F Gaming, AMD Ryzen 5800X, 64 GB Corsair Vengeance LPX DDR4-3000, ASUS TUF Gaming Radeon RX 6800 XT, Samsung 970 EVO M.2 NVMe 250 GB (OS), Corsair MP600 PRO LPX M.2 NVMe 2 TB (DCS World), Gigabyte G27QC Gaming Monitor, DelanClip Gamer, WINWING F-16EX Metal Flightstick with Orion2 Joystick Base, WINWING F-15EX II Metal Throttle with Orion2 Throttle Base, WINWING PTO 2 Take Off Panel, VIRPIL Controls Ace Flight Pedals, Buddy-Fox A-10C UFC, Thrustmaster MFD Cougar Pack, Windows 10 Pro
Ithronwise Posted April 15, 2021 Author Posted April 15, 2021 Hi Aviators, hi ED Team, I tested a little around (deleted the options.lua and started with a fresh one) but there were no changes. DCS 2.7 ran with 1920x1080 no matter what resolution I set. Then I changed the resolution of my Windows to 2560x1440 and now DCS runs with 2560x1440. But this is no solution for me, because the Windows fonts and symbols are looking blurry with this resolution and I use my Rig for other tasks than gaming, too. I tested the following settings: 1. Windows resolution: 1920x1080 DCS resolution: 2560x1440 Result: DCS runs with 1920x1080 2. Windows resolution: 2560x1440 DCS resolution: 2560x1440 Result: DCS runs with 2560x1440 3. Windows resolution: 2560x1440 DCS resolution: 1920x1080 Result: DCS runs with 1920x1080 It seems the max. resolution limit of DCS 2.7 depends of the resolution of Windows now. Lower than Windows resolution is working, higher than Windows resolution doesn't work anymore. I think this issue is caused by this change in the patchnotes: "Graphic system. First game start will be in main display resolution, not 1280x768." Something is buggy there. Best regards, Rene ASUS ROG Strix B450-F Gaming, AMD Ryzen 5800X, 64 GB Corsair Vengeance LPX DDR4-3000, ASUS TUF Gaming Radeon RX 6800 XT, Samsung 970 EVO M.2 NVMe 250 GB (OS), Corsair MP600 PRO LPX M.2 NVMe 2 TB (DCS World), Gigabyte G27QC Gaming Monitor, DelanClip Gamer, WINWING F-16EX Metal Flightstick with Orion2 Joystick Base, WINWING F-15EX II Metal Throttle with Orion2 Throttle Base, WINWING PTO 2 Take Off Panel, VIRPIL Controls Ace Flight Pedals, Buddy-Fox A-10C UFC, Thrustmaster MFD Cougar Pack, Windows 10 Pro
Proteuswave Posted April 15, 2021 Posted April 15, 2021 Same here when trying to use virtual resolution. Intel i7 6700 3.4Ghz , 32gig ripjaw ram , Asus Strix RX480 OC 8gb , Samsung 850 Pro SSD, Asus ROG VIII Ranger Z170 Motherboard.
Hellbat Posted December 3, 2021 Posted December 3, 2021 This still seems to be an issue. Any chance of a fix in the near future?
ED Team BIGNEWY Posted December 3, 2021 ED Team Posted December 3, 2021 Hi I don't use AMD but I will ask the team about it, if I get a reply I will let you know. thanks bignewy 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
ED Team BIGNEWY Posted December 15, 2021 ED Team Posted December 15, 2021 Hi all, regarding AMD Virtual Super Resolution, we do not support any super resolution solutions at driver level, I can not promise we can support it, but the team will take a look. With the resolutions we use a protection of screen resolution which exceeds value returned by WinAPI virtualScreen size. For example if you use a notebook to connect to 4k display and play DCS that resolution is saved, but if you then launch it without the attached display the UI becomes unreachable due saved resolution exceeds boundaries of any native display found in the system. The team are aware and looking for a solution. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Ithronwise Posted December 15, 2021 Author Posted December 15, 2021 2 hours ago, BIGNEWY said: Hi all, regarding AMD Virtual Super Resolution, we do not support any super resolution solutions at driver level, I can not promise we can support it, but the team will take a look. With the resolutions we use a protection of screen resolution which exceeds value returned by WinAPI virtualScreen size. For example if you use a notebook to connect to 4k display and play DCS that resolution is saved, but if you then launch it without the attached display the UI becomes unreachable due saved resolution exceeds boundaries of any native display found in the system. The team are aware and looking for a solution. thanks This issue doesn't matter to me anymore since I bought a larger monitor with native WQHD resolution and higher pixel density. But apart from that, in version 2.5.6 the super resolution worked very well. Why is it problematic now in version 2.7? Your explanation is not really convincing, because other game manufacturers don't see it as a problem. ASUS ROG Strix B450-F Gaming, AMD Ryzen 5800X, 64 GB Corsair Vengeance LPX DDR4-3000, ASUS TUF Gaming Radeon RX 6800 XT, Samsung 970 EVO M.2 NVMe 250 GB (OS), Corsair MP600 PRO LPX M.2 NVMe 2 TB (DCS World), Gigabyte G27QC Gaming Monitor, DelanClip Gamer, WINWING F-16EX Metal Flightstick with Orion2 Joystick Base, WINWING F-15EX II Metal Throttle with Orion2 Throttle Base, WINWING PTO 2 Take Off Panel, VIRPIL Controls Ace Flight Pedals, Buddy-Fox A-10C UFC, Thrustmaster MFD Cougar Pack, Windows 10 Pro
ED Team BIGNEWY Posted December 15, 2021 ED Team Posted December 15, 2021 2 minutes ago, Ithronwise said: But apart from that, in version 2.5.6 the super resolution worked very well. Why is it problematic now in version 2.7? Your explanation is not really convincing, because other game manufacturers don't see it as a problem. As mentioned we dont officially support it at driver level, if it was working and is not now we have not changed anything with this intention. The team will look into it. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
WinterH Posted December 15, 2021 Posted December 15, 2021 Just want to say that I've been having this since 2.7 came with Nvidia DSR too. I'm stuck with a craptacular old 1440x900 monitor, but was using the sim in 1920x1200 with DSR prior to 2.7 just fine. Since then, regardless of full screen or not, DSR won't work anymore. Wishlist: F-4E Block 53 +, MiG-27K, Su-17M3 or M4, AH-1F or W circa 80s or early 90s, J35 Draken, Kfir C7, Mirage III/V DCS-Dismounts Script
Ithronwise Posted December 15, 2021 Author Posted December 15, 2021 1 minute ago, BIGNEWY said: As mentioned we dont officially support it at driver level, if it was working and is not now we have not changed anything with this intention. The team will look into it. Sorry, but I highly doubt that. The problem occurred after upgrading to 2.7 and was gone after I downgraded back to 2.5.6 because of it. So the only thing that had changed was DCS. ASUS ROG Strix B450-F Gaming, AMD Ryzen 5800X, 64 GB Corsair Vengeance LPX DDR4-3000, ASUS TUF Gaming Radeon RX 6800 XT, Samsung 970 EVO M.2 NVMe 250 GB (OS), Corsair MP600 PRO LPX M.2 NVMe 2 TB (DCS World), Gigabyte G27QC Gaming Monitor, DelanClip Gamer, WINWING F-16EX Metal Flightstick with Orion2 Joystick Base, WINWING F-15EX II Metal Throttle with Orion2 Throttle Base, WINWING PTO 2 Take Off Panel, VIRPIL Controls Ace Flight Pedals, Buddy-Fox A-10C UFC, Thrustmaster MFD Cougar Pack, Windows 10 Pro
ED Team BIGNEWY Posted December 15, 2021 ED Team Posted December 15, 2021 1 minute ago, Ithronwise said: Sorry, but I highly doubt that. The problem occurred after upgrading to 2.7 and was gone after I downgraded back to 2.5.6 because of it. So the only thing that had changed was DCS. That is the information I have directly from the dev team, but ok. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Ithronwise Posted December 15, 2021 Author Posted December 15, 2021 2 hours ago, BIGNEWY said: That is the information I have directly from the dev team, but ok. That may be, but I think you'll agree that if this problem occurs in 2.7 and not 2.5.6, something has changed between those two versions and is causing this issue. When I experienced this problem, nothing had changed on my system, and when I went back to 2.5.6 a day later, my system was still unchanged. Perhaps it is a side effect of another change in the 2.7 source code. ASUS ROG Strix B450-F Gaming, AMD Ryzen 5800X, 64 GB Corsair Vengeance LPX DDR4-3000, ASUS TUF Gaming Radeon RX 6800 XT, Samsung 970 EVO M.2 NVMe 250 GB (OS), Corsair MP600 PRO LPX M.2 NVMe 2 TB (DCS World), Gigabyte G27QC Gaming Monitor, DelanClip Gamer, WINWING F-16EX Metal Flightstick with Orion2 Joystick Base, WINWING F-15EX II Metal Throttle with Orion2 Throttle Base, WINWING PTO 2 Take Off Panel, VIRPIL Controls Ace Flight Pedals, Buddy-Fox A-10C UFC, Thrustmaster MFD Cougar Pack, Windows 10 Pro
draconus Posted December 15, 2021 Posted December 15, 2021 35 minutes ago, Ithronwise said: That may be, but I think you'll agree that if this problem occurs in 2.7 and not 2.5.6, something has changed between those two versions and is causing this issue. Of course something has changed but it was not their intention to break it. Quote ...we have not changed anything with this intention. The team will look into it. 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Recommended Posts