I'm having the exact same issue since updating to the latest AMD drivers.
Anyone with an RX 6000 series card able to get Odyssey to run with the 22.5.2 drivers?
- Thread starter Morbad
- Start date
Went to AMD's site and downloaded the 22.5.1 drivers. 22.5.2 is listed as optional, not WHQL. I downloaded them through the AMD software before. I went back into the settings for the AMD software and set it to check for recommended drivers (WHQL) only.
Just throwing in my 2¢ that I've run into this as well. RX 6900XT, driver 22.5.2 works fine as long as I stay in space, but immediate Orange Sidewinder if I try to go down to a planet.
Real shame given the huge D3D11 performance increase from the driver. Though in fairness I guess never going down to a planet does technically increase the average framerates I'll see in Elite.
Real shame given the huge D3D11 performance increase from the driver. Though in fairness I guess never going down to a planet does technically increase the average framerates I'll see in Elite.
Another thread.... Frontier realy needs to get their stuff together.
So you blame Frontier for an AMD beta driver? OK
So you blame Frontier for an AMD beta driver? OK
Hard to say who is at fault here. It's possible that the drivers are compliant with relevant standards that the game is somehow violating. This is not the first or only issue with this specific combination of game and hardware.
If the issue persists when the same driver is released with WHQL certification, then perhaps the blame can be attibuted to Frontier 'cutting corners'?
Added: It will be inconvenient if the issues do remain, so hoping otherwise!
Last edited:
WHQL only means that the driver is certified as compatible with Windows. It could still be a beta or alpha quality driver and be blatantly problematic in applications and still get signed.
Plus, the last ten or so WHQL releases have texture color pallet corruption and orbit lines that are somehow immune to the game's post-process AA. If it's a driver bug causing any of this, it's probably not one that's going to cause it to fail WHQL testing.
I certainly hope the next release of the driver or game fixes this, but I fear that being able to play this game on RDNA2 parts is going to mandate locking one's self into increasingly old and unsupported drivers.
Ah, memories of one particular game I used to have which only ever worked with one specific outdated revision of the drivers for the graphics card I owned at the time.
I'd very much suspect AMD is at fault, if it worked fine with prior drivers up until now - and still works fine with the latest NVIDIA and Intel drivers...
Getting Orange Sidewinder errors in Horizons now trying to load the SRV tutorials.
Well, the game ran with prior drivers; wasn't problem free though.
AMD is certainly at fault for altering the way their drivers treat the game, but as I said, it may very well be a case of the current drivers adhering to standards better than before, and the game not doing what it's supposed to...prior drivers may simply have been more tolerant of aberrant behavior. This is why standards exist, so software will run without special accommodation from the hardware/driver and vice versa. Whoever isn't adhering to those standards is ultimately at fault, but I have no real way of knowing who that is.
Well, the game ran with prior drivers; wasn't problem free though.
AMD is certainly at fault for altering the way their drivers treat the game, but as I said, it may very well be a case of the current drivers adhering to standards better than before, and the game not doing what it's supposed to...prior drivers may simply have been more tolerant of aberrant behavior. This is why standards exist, so software will run without special accommodation from the hardware/driver and vice versa. Whoever isn't adhering to those standards is ultimately at fault, but I have no real way of knowing who that is.
Alright I got terrain working again in Horizons by reducing the GPU scheduler multiplier back to 0.5 and disabling PermitNativeDoubles. Not sure which setting did the trick, probably the latter, will double check.
Haven tested Odyssey again, yet.
Edit: The Horizons terrain issue can indeed be resolved by setting PermitNativeDoubles=false in AppConfig.xml.
Odyssey still not working and still taking ages to prepare planet generation system.
Haven tested Odyssey again, yet.
Edit: The Horizons terrain issue can indeed be resolved by setting PermitNativeDoubles=false in AppConfig.xml.
Odyssey still not working and still taking ages to prepare planet generation system.
Last edited:
Thanks for the research, it’s much appreciated.
I wasn’t planning on updating my drivers but should this issue persist even with WHQL release then it’s good to know someone is working on a workaround.
Same problem here with a Radeon 6800. Rolling back the drivers to 22.5.1 fixed the problem for me.
I also had blue graphical corruption when approaching atmospheric planets
Please, everyone submit a bug report to AMD. You can do it in a few clicks by clicking the insect icon at the top right of the AMD driver control panel.
I also had blue graphical corruption when approaching atmospheric planets
Please, everyone submit a bug report to AMD. You can do it in a few clicks by clicking the insect icon at the top right of the AMD driver control panel.
Data point - using the 22.5.2 drivers with a RADEON VII (16GB) - older card than the 6000 series but the floating point unit makes it worthwhile since my research machine doubles as my gaming machine.
Upon loading after updating the driver
Launched Odyssey
85 seconds for generating first part of shaders
80 seconds to generate the planetary shaders
Let station, flew to planet, approached and landed and took off a couple of times - no issues noted.
Graphic settings are set to ULTRA and SAM disabled (actually not supported with the Threadripper 2950) no other changes made from 22.5.1 settings. I don't have any of the Adrenalin gaming features enabled.
Typically I see about 58-72 FPS at Ultra in pretty much all parts of the game with sometimes a 10 FPS drop at ground stations with about 68% GPU utilization. My main monitor (Dell 3415) is locked at 60 Hz so no real need for much higher.
I am not sure how closely the Radeon VII (which is a 2nd gen Vega chipset) is to the RX 6000 series to tell if they would share any architectural bugs related to Odyssey. If there is any testing I can do to help pinpoint this let me know. I have an 6950 card I was planning for a different system I can swap in.
-----
System
TR 2950, Gigabyte Aorus Xtreme MB (F5), 128GB main RAM, Radeon VII, Windows 11 Education on its own NVME drive and ED on a separate NVME drive.
Upon loading after updating the driver
Launched Odyssey
85 seconds for generating first part of shaders
80 seconds to generate the planetary shaders
Let station, flew to planet, approached and landed and took off a couple of times - no issues noted.
Graphic settings are set to ULTRA and SAM disabled (actually not supported with the Threadripper 2950) no other changes made from 22.5.1 settings. I don't have any of the Adrenalin gaming features enabled.
Typically I see about 58-72 FPS at Ultra in pretty much all parts of the game with sometimes a 10 FPS drop at ground stations with about 68% GPU utilization. My main monitor (Dell 3415) is locked at 60 Hz so no real need for much higher.
I am not sure how closely the Radeon VII (which is a 2nd gen Vega chipset) is to the RX 6000 series to tell if they would share any architectural bugs related to Odyssey. If there is any testing I can do to help pinpoint this let me know. I have an 6950 card I was planning for a different system I can swap in.
-----
System
TR 2950, Gigabyte Aorus Xtreme MB (F5), 128GB main RAM, Radeon VII, Windows 11 Education on its own NVME drive and ED on a separate NVME drive.
I'm doubtful these are related issues.