Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 2 [3] 4 5   Go Down

Author Topic: AMD driver woes  (Read 4621 times)

0 Members and 2 Guests are viewing this topic.

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23882
  • Taking a timeout
    • STFU
Re: AMD driver woes
« Reply #24 on: September 20, 2023, 01:19:09 AM »

Argh.
Another room in the AMD driver hell.

AMD's OpenGL "Optimization" in newer drivers ultimately broke quite a couple of games, and waiting for AMD to fix this will probably exceed the expected lifespan of most of us.
Any alternatives?
Maybe.
There are 3rd party drivers out there and some are working better with older OpenGL titles than the official AMD ones. YMMV.
The ones from Amernime are known to be of good quality, but in lack of a decent AMD GPU I can't test them myself:
https://www.amernimezone.com

The "Navi" branch of drivers is said to be compatible with RX 7900 XTX (see device compatibility list down on their page) so you could give it a try.

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23882
  • Taking a timeout
    • STFU
Re: AMD driver woes
« Reply #25 on: September 20, 2023, 06:37:34 AM »

*bump*

both JPG and TGA as if there corrupted wen made in DirectX mode

I've managed to identify an odd issue with DirectX screenshots in combination with TD's new DT.dll (which we are using in latest Ultrapack versions) in certain edge cases.
Ultrapack 3.4 Patch 2 Hotfix 20 will address this issue.
Please note that Hotfix 20 has not been released yet.

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.

WhiteSnake1976

  • member
  • Offline Offline
  • Posts: 207
Re: AMD driver woes
« Reply #26 on: September 20, 2023, 11:32:44 AM »

*bump*

both JPG and TGA as if there corrupted wen made in DirectX mode

I've managed to identify an odd issue with DirectX screenshots in combination with TD's new DT.dll (which we are using in latest Ultrapack versions) in certain edge cases.
Ultrapack 3.4 Patch 2 Hotfix 20 will address this issue.
Please note that Hotfix 20 has not been released yet.

]cheers[
Mike

Great to hear that Mike, P.S. in 4K res both OpenGL and DirectX screenshots act the same way, maybe you can take a look at that while your at it.
Thx in advance.
Logged

arnitos

  • member
  • Offline Offline
  • Posts: 12
Re: AMD driver woes
« Reply #27 on: November 20, 2023, 11:22:05 AM »

Hello,

I created the post below in guru3D forum in the hope of good advices but nothing efficient has been proposed

https://forums.guru3d.com/threads/il-1946-flight-sim-opengl-issue-with-amd-drivers-after-22-5-1.450169

I am afraid to use amernime (R.ID) drivers because it seems complicated to install. However, one day I will try because it is definitely a driver problem due to the removal of old openGL instructions existing in 22.5.1 and previous.
Very sad to not be able to play my beloved IL 1946 sim in full perfect mode ::( ::( ::( ::( ::(
Logged

Crazily6857

  • member
  • Offline Offline
  • Posts: 9
Re: AMD driver woes
« Reply #28 on: November 21, 2023, 10:04:03 AM »

Hey,
It is bad game's behavior at the backend that causes the issue.
Game does not use GL_ATI_fragment_shader extension, but queries for it. If it is not exposed by driver then "Perfect Mode" is not available.
In the end it uses ARB shaders, but not this extension...
So both - cloud artifacts and ability to activate Hardware shaders=1 is going to be fixed in AMD's driver in the first quarter of 2024.
You are welcome :)
Logged

WhiteSnake1976

  • member
  • Offline Offline
  • Posts: 207
Re: AMD driver woes
« Reply #29 on: November 21, 2023, 11:10:46 AM »

Hey,
It is bad game's behavior at the backend that causes the issue.
Game does not use GL_ATI_fragment_shader extension, but queries for it. If it is not exposed by driver then "Perfect Mode" is not available.
In the end it uses ARB shaders, but not this extension...
So ability to activate Hardware shaders=1 is going to be fixed in AMD's driver in the first quarter of 2024.
You are welcome :)

Thx,
I hope they fix it with a driver update, but so far running it in DirectX with a Settings Profile for the game in the Adrenalin settings with everything for quality set to max and overiding the game settings looks really good also. (more in my posts here: https://www.sas1946.com/main/index.php/topic,71698.0.html )
Logged

Fire112

  • member
  • Offline Offline
  • Posts: 14
Re: AMD driver woes
« Reply #30 on: January 24, 2024, 09:32:00 AM »

Hi there,

I think I kinda solved the OpenGL-Issues with AMD cards to a certain point. Stumbled across a solution for another game on reddit and gave it a try.

You have to edit a line in the registry to get it work, so you should know what you do. Don't blame me if your PC isn't running any more after this. But don't be afraid, it's pretty straight forward ;)
And I think you'll have do redo the registry-entries after you installed a new driver (to be verified)

What to do?

1. Get the atioglxx.dll from the 22.5.2 AMD driver package. I dont know if I'm allowed to upload this file, so you have to get it yourself by downloading the 22.5.2 driver package from AMDs website ( https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-5-2 )

2. Extract the driver package either by using 7-zip for example or by running it. When you are running it ABORT the installation after the file extraction when the installation window pops up.

3. Navigate inside the extracted driver folder to Packages\Drivers\Display\WT6A_INF\B379425

4. search for atioglxx.dll and copy it to another folder where you can find it again (I created a new folder on my HD under C:\driver\OpenGL and put it there)

5. Push the Windows-key and type regedit and push enter

6. Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000

7.  Edit the OpenGLVendorNameWoW string. Remove the text already in it* and replace it with 2 lines of your file path without quotes. For me this is

C:\driver\OpenGL\atioglxx.dll
C:\driver\OpenGL\atioglxx.dll

see image



*copy the path which is in there to a text file, so you can fast switch back to your current OpenGL-Settings if necessary


8. Click Ok, if you get an error about empty strings it's safe to ignore

9. That's all the magic, no reboot needed. Setup your Il2 config.ini with OpenGL and Hardwareshaders=1 and all the other fancy stuff, I'll add my settings for example (even enabled the NVidia settings apart from the water, that doesn't work for me with a value of 3 or 4). Hardwareshaders no longer switch back to 0 for me.

Code: [Select]
[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=1
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.UseVertexArrays=1
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=1
TexFlags.ClipHintExt=1
TexFlags.UsePaletteExt=1
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=0
TexFlags.TexEnvCombine4NV=1
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=1
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=1
HardwareShaders=1
Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3
Sky=2
Forest=3
LandShading=3
LandDetails=2
LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1
VideoSetupId=17
Water=2
Effects=2
ForceShaders1x=0
PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0


Further notice:

I use a Radeon 5700XT in my computer. I think this will only work with graphic cards which are mentioned in the driver package which are according to the AMD-Website

Radeon™ RX 6900/6800/6700/6600/6500/6400 Series Graphics
Radeon™ RX 5700/5600/5500/5300 Series Graphics
Radeon™ VII
Radeon™ RX Vega Series Graphics
AMD Radeon™ Pro Duo
Radeon™ RX 500 / Radeon 500X Series Graphics
Radeon™ RX 400 Series Graphics



And at last quick taken screenshot with this settings. Thanks to the B.A.T.-Team for this great mod.

Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23882
  • Taking a timeout
    • STFU
Re: AMD driver woes
« Reply #31 on: January 24, 2024, 09:55:30 AM »

Thanks for the update, which is good news for many AMD users as they can update their drivers now using this "trick" while retaining compatibility using the "old" atioglxx.dll file.
Unfortunately, it still doesn't provide any way out for RX7000 series users.

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.

Fire112

  • member
  • Offline Offline
  • Posts: 14
Re: AMD driver woes
« Reply #32 on: January 24, 2024, 10:58:57 AM »

Maybe someone can try with a RX7000 card, but I don't think it will work unfortunately.
Logged

WhiteSnake1976

  • member
  • Offline Offline
  • Posts: 207
Re: AMD driver woes
« Reply #33 on: January 26, 2024, 10:32:41 AM »

If i got more time i give it a try on my RX 7900 XTX, but i think on those cards it not just a OpenGL problem, since under DirectX it also has isues with the Hardwareshaders.
Logged

Crazily6857

  • member
  • Offline Offline
  • Posts: 9
Re: AMD driver woes
« Reply #34 on: February 26, 2024, 12:34:58 AM »

IL-2 issue on AMD GPU's is fixed with the next driver release. It adds "Perfect" mode back to options and fixes clouds corruption.
Just make sure the exe name is il2fb.exe

I have posted the info here
https://community.amd.com/t5/drivers-software/il2-1946-broken-open-gl/m-p/668523/highlight/true#M189041
and there
https://community.amd.com/t5/drivers-software/amd-drivers-22-11-2-issue-opengl-perfect-landscape-not-activable/m-p/668521/highlight/true#M189040
;)
Logged

Dragunoff

  • member
  • Offline Offline
  • Posts: 146
Re: AMD driver woes
« Reply #35 on: February 26, 2024, 01:23:15 AM »

Thank you for the info. I haven't been on AMD's site since I wrote them angry posts. :) I hope that everything will be fine in the foreseeable future.
Logged
Pages: 1 2 [3] 4 5   Go Up
 

Page created in 0.03 seconds with 27 queries.