Thanks for the update, that’s finally some good news.
I will give 22.10.3 a try once released.
Thanks for the update, that’s finally some good news.
Odd thing is that the recording made was perfectly normal, so I can't show it!
I'm just giving the new drivers a whirl now... RX 6800 XT here which was running on 22.3.1 until now (no hotfixes used).
Ody started up fine, no colour flickering, I successfully landed on a surface of a non-atmo planet.
Was the Orange Sidewinder happening when trying to land on any surface or only atmos?
There is one problem though - the texture detail pops in too late for me now. It's like I'm moving in a bubble where the details are fine but outside the borders they are not loaded yet. And the bubble is too small.
I tried to delete graphics settings but that did not help in any way.
But I honestly can't tell if this was the case with older drivers or not. Maybe I'm just concentrating too much and noticing things that were there before anyway.
View attachment 329773
I just tried 22.10.3 on my system. Radeon RX 6600. Graphic settings have been reset and then set back to Ultra.
The Orange Sidewinder crash has gone but now the game shows some problems with the graphics when playing ground missions. When I enter the building, the graphics seem to be ok in some places. The glitch also seems to be influenced wheather the flashlight is on or off which you can see in the video I just recorded.
Source: https://youtu.be/GGz4yyzpY_0
View attachment 329777
Is there fix for the weird green thing? Seem to have 22.10.2 running fine bar the insane green thing
Cheers, I thought that was for the Orange Sidewinder thingy. I've been using it and been working a charm so thanks for the hard work. I'm trying to track down an OBS issue with Odyssey so testing without it enabled.Reference workaround #2.
Cheers, I thought that was for the Orange Sidewinder thingy.
I'm trying to track down an OBS issue with Odyssey
It breaks frame sync so despite getting reasonable FPS it's jerky as anything. This isn't whilst streaming, as soon as OBS is open it happens. FPS drops by 10 percent and the odd jerkiness happens - it's 2 way also so if Odyssey is smooth, OBS capture is jerky. My OBS is very optimised with total CPU use when not streaming is under 3 percent.The only fix required for the Orange Sidewinder crash was the AppConfig.xml change. The 3DMigoto stuff was always for the teal overlay.
What issue?
Just uploading to youtube, so may take a while to process.Post it anyway, so we can see the location/scenario the issue was occurring in.
It breaks frame sync so despite getting reasonable FPS it's jerky as anything. This isn't whilst streaming, as soon as OBS is open it happens. FPS drops by 10 percent and the odd jerkiness happens - it's 2 way also so if Odyssey is smooth, OBS capture is jerky. My OBS is very optimised with total CPU use when not streaming is under 3 percent.
It's the most annoying thing ever and I've tried literally everything from matching monitor frequencies to separating CPU affinities for the processes...maddening. I tested with DXVA disabled and doubles turned back on quickly and all was smooth but that was just now and for 5 minutes only, I need to test it bit further.
As soon as the game started loading ( so selecting EDO) the screen was flashing, top two thirds with cycling colours. The ship interior colours were unnaturally bright beneath the flashing. None of this can be seen in the video!
This is without encoding started mate and it's on all capture sources - game, window and displayWhat capture source are you using and does this happen even if you don't have the output preview enabled?
What encoder/settings?
I haven't seen anything like this. Does it persist after clearing shaders and deleting the worktable?
It not being on the video suggest it's being added very late in the display chain. Any overlays or unusual scaling active? Any display issues? Using an unusual pixel format?
I don't use any overlays or other tools - this was recorded using AMD's Adreneline.It not being on the video suggest it's being added very late in the display chain. Any overlays or unusual scaling active? Any display issues? Using an unusual pixel format?