Anyone with an RX 6000 series card able to get Odyssey to run with the 22.5.2 drivers?

I'm running into the same issue I had with the preview drivers; initial terrain generation takes forever (about five hours), the game loads to the main menu, then crashed back to the main menu with an Orange Sidewinder error upon entering any mode or playing any training mission.

Horizons works normally.

August 13 edit: Thus far, these issues exist on all drivers using the new D3D11 branch, so everything after 22.5.1. However, there are workarounds.

Additional edit: If you are using DXVK, these are my recommended dxvk.conf settings: https://forums.frontier.co.uk/threa...n-with-the-22-5-2-drivers.603678/post-9924170
 
Last edited:
Similar issue here. I'm using an RX 6700 and get the Orange Sidewinder error. It definitely seems related to planets/terrain somehow, as the game will load and function normally in space with the 22.5.2 or preview drivers, but any attempt to land on a planet will result in the Orange Sidewinder error as soon as you pass the 2500m/s threshold when attempting a planetary landing. Rolling back to the 22.5.1 driver resolves this, but I hope we get a full fix soon.
 
Last edited:
not that it matters as I dont have that series GPU but performance is Identical to 22.5.1 , no real point in updating , but it does work fine for me
 
not that it matters as I dont have that series GPU but performance is Identical to 22.5.1 , no real point in updating , but it does work fine for me

Performance changes aren't the same across different series chips. Drivers don't run all chips completely the same way. Newer chips have different ways of doing some things and sometimes have performance features older series chips lack entirely. Your statement could end being completely true though because AMD is less software-centric than nvidia. Which is how it should be anyway.
 
I have a 6000-series one and I'm almost tempted, since I'll be getting an account copy from XBox down the line, to grab Odyssey just for the purpose of benching it for my friends to let them know if/when it's worth them getting it. I fully plan on continuing to play in Horizons as long as Frontier will allow, but I managed to match and in some places exceed the XBox Series X settings for Cyberpunk 2077 on my laptop (Ryzen 7 5800H with an RX 6600M) and get an acceptable framerate (Mid 50s, which VRR smooths out), so Odyssey could be a neat project for me on that front.
 
Performance changes aren't the same across different series chips. Drivers don't run all chips completely the same way. Newer chips have different ways of doing some things and sometimes have performance features older series chips lack entirely. Your statement could end being completely true though because AMD is less software-centric than nvidia. Which is how it should be anyway.
good to know , I figured as much though. There may be like a 2 to 3 fps difference on the planet which may be why its crashing on your systems , it affects the planet generation in some way.
 
actually scratch that , just had a hard crash of the computer display vanished and pc froze completely , time to uninstall the driver I guess
 
And this is why unless it is guaranteed to fix a critical bug giving me bluescreens, etc. I stay a revision or two behind on my graphics drivers, where I know everything is stable.
Given the chance that the preview drivers at one point will feature a full release, be grateful there are people testing these ahead of time. Hopefully FDev will pick up on this.
 
AMD's relative lack of D3D11 threading and performance in CPU limited scenarios, has been a problem since Kepler. I'm not sure on the mechanism by with these 22.5.2 (as well as the earlier preview) drivers are improving D3D11 performance on the 6000 series, but it has improved in most of my D3D11 games.

The difference is enough that, overall, these drivers are better, for me, even if Odyssey is completely unusable.

Given the chance that the preview drivers at one point will feature a full release, be grateful there are people testing these ahead of time. Hopefully FDev will pick up on this.

This is the full release of the prior preview drivers. They are technically still a beta, but one-hundred-to-one, the WHQL/recommended driver will have the same problem.

Odyssey has issues on the RX 6000 series, that no other game I've encountered does, that have persisted for a year of game and driver updates. Every 6000 series driver and every version of Odyssey has major aliasing issues with orbit lines, and always has, from the first alpha build I tested on the second day of the EDO alpha, to today. There was also an annoying terrain texture pallet bug that may be just as old, but is more intermittent. Now the game just won't build or render Odyssey terrain correctly on the newest drivers. Chances are these issues are primarily on Frontier's end and obscure enough that AMD won't become fully aware of/prioritize a fix on their end, for a while.
 
Odyssey has issues on the RX 6000 series, that no other game I've encountered does, that have persisted for a year of game and driver updates. Every 6000 series driver and every version of Odyssey has major aliasing issues with orbit lines, and always has, from the first alpha build I tested on the second day of the EDO alpha, to today.
Perhaps it will ease the pain a little that on my 1060 the AA on orbit lines is nearly non-existent as well.
 
Perhaps it will ease the pain a little that on my 1060 the AA on orbit lines is nearly non-existent as well.

I have other GPUs (including Polaris and Ampere NVIDIA parts and RDNA 1 and GCN AMD parts). If you think orbit lines look bad on your 1060, they look worse on my 6800 XT and 6900 XT.
 
I've just downloaded and installed these drivers, and had a brief look. (My system R9 5900X / Radeon 6900XT)
The generation took no longer than 'normal' (which always seems an age) and EDO launched without issue. I did only have a few minutes to play though.

When I'm back from dog walking I'll fire up and have a proper play, I'll report back if there are any issues.
 
Horizons works normally.
Morning duties done: Into the game, briefly!

I have the opposite situation, EDO is launching normally and Horizons is delivering an Orange Sidewinder either on launch, or when dropping from Supercruise.
I'll play around a little more for an hour or so.

ETA: OK... Back to EDO, it rebuilds the shaders and planetary generation, drop from SC into an Orange Sidewinder. Try again...

OK, rolled back to previous version as neither EDH or EDO are functioning (darned sideys!) although other games tried are working as normal. Will check after U12, just in case!
 
Last edited:
Had the update this morning, crashed to desktop on approaching the first settlement, and couldn't restart the game without it crashing back to desktop.

Started up in Horizons (first time in a loooooong time) and moved ship away from planet in supercruise.

Restart Odyssey, all working again, but settlements were insane distances away.

Tried a planetary approach in a different system, Orange Sidewinder and CTD again.

Rolled back GFX drivers, uninstalled AMD Adrenalin 2.5.2 and reinstalled 2.5.1.

All is back to normal now.
 
Back
Top Bottom