What I find strange is that performance on my rig with DLSS is A LOT better using DX11 than with DX12.
Priller
Windows 11 23H2 Enterprise Edition
Intel i9 13900KF @ 5.8 GHz
be quiet! Dark Rock 4 Pro cooler
G-Skill 32Gb DDR5 RAM 7600-36
MSI Z790 Motherboard
Nvidia RTX4090 Graphics Card
Samsung 1TB 980 EVO PCIe M.2 C: drive
Samsung 2TB 980 EVO PCIe M.2 Data drive
be quiet! Straight Power CM1000W PSU
Like for many. I dont know why we have DX12 here, no any benefits and worse performance. Overall it's weird because MS itself promoted DX12 as a great engine and good optimization, and here you can see that it's not doing well and DX11 offers much better smooth of image.
Webmaster of yoyosims.pl.
Win 10 64, i9 13900 KF, RTX 4090 24Gb, RAM64Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
My update is finally done. My d/l speeds were good, but there were two loops that required restarts. Total time was 59 minutes from first folder installed to last, which includes the Content manager.
I've had worse...
I'll fly later - got some things in the real world that require attention.
Thermaltake H570 TG Tower
X670 Aorus Elite AX motherboard
AMD Ryzen 9 7900X 12-Core Processor
NVIDIA GeForce RTX 3070
NZXT Kraken X cooler
32GB DDR5 RAM
750 Watt PS
Windows 11 Home
Windows 11 23H2 Enterprise Edition
Intel i9 13900KF @ 5.8 GHz
be quiet! Dark Rock 4 Pro cooler
G-Skill 32Gb DDR5 RAM 7600-36
MSI Z790 Motherboard
Nvidia RTX4090 Graphics Card
Samsung 1TB 980 EVO PCIe M.2 C: drive
Samsung 2TB 980 EVO PCIe M.2 Data drive
be quiet! Straight Power CM1000W PSU
I get the same result with DX12, and DLSS just causes blurred gauges and glass cockpit screens - increasing the new AMD FidelityFX Sharpening just reduces FPS even further. I have an RTX2060 6Gb and Intel i5-7600k. Back to 516.94 Game Ready and DX11 for me, thanks anyway...
Maybe we should wait for the new game ready driver to come out. DX12 is giving brilliant results in other sims, so you never know.
Priller
Windows 11 23H2 Enterprise Edition
Intel i9 13900KF @ 5.8 GHz
be quiet! Dark Rock 4 Pro cooler
G-Skill 32Gb DDR5 RAM 7600-36
MSI Z790 Motherboard
Nvidia RTX4090 Graphics Card
Samsung 1TB 980 EVO PCIe M.2 C: drive
Samsung 2TB 980 EVO PCIe M.2 Data drive
be quiet! Straight Power CM1000W PSU
Game ready drivers (NVidia) will be in incoming week.
Webmaster of yoyosims.pl.
Win 10 64, i9 13900 KF, RTX 4090 24Gb, RAM64Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Windows 11 23H2 Enterprise Edition
Intel i9 13900KF @ 5.8 GHz
be quiet! Dark Rock 4 Pro cooler
G-Skill 32Gb DDR5 RAM 7600-36
MSI Z790 Motherboard
Nvidia RTX4090 Graphics Card
Samsung 1TB 980 EVO PCIe M.2 C: drive
Samsung 2TB 980 EVO PCIe M.2 Data drive
be quiet! Straight Power CM1000W PSU
I submitted the problem to the forum. The following solution solved the problem:
Create a new profile for your joystick. Do not copy or just rename the old one.
For now, just change the brakes to your trigger and test it.
This should work now. If so, go ahead and remap as desired, then delete your old profile.
Thanks, Tom, for your suggestion.
Jim
Bookmarks