Hi all, I’ve been recently playing some somewhat old games and have had trouble with either crashing, or weird graphical glitches.
The list of games I’ve tried:
Warcraft III (a custom map, normal game seems to work fine) Quake 2 Spring engine 103 (rts engine)
Warcraft 3 has a glitched white bar following the cursor, and the map crashes with “access violation” as the only error, as did the rts engine. I managed to fix the crash by running a 64 bit version of spring engine, but it then had this weird graphical glitch: https://imgur.com/a/ij6FaWa I looked in the settings and kept changing anything I could think of, one was to set UseVBO=0 which fixed that graphical problem, but sometimes the game will still crash with “access violation” Quake 2 replaces all projectile sprites/trails with a circle: https://imgur.com/a/qtLR2To
I’m thinking this is a weird problem with my AMD card, because I have a computer with the same 64 bit OS and all of these games work fine on it, and I played quake 2 before on this computer with the only difference being I swapped the graphics card and motherboard (exact same model mobo) I’ve tried running warcraft 3 with djvoodoo and that didn’t seem to help, I’ve read online amd cards can have issues with older games running openGL and directx. Those posts are pretty old, but they make me think I might be SOL with an amd card
specs: OS: windows 10 home 64 bit mobo: gigabyte z690 UD ddr4 processor: intel i7 12700kf gfx: amd radeon RX 6800 XT
Appreciate any ideas!
Edit: wc3 crash log: https://www.dropbox.com/scl/fi/xrfw98rs7yhy356gt725g/2023-07-30-12.35.02-Crash.txt?rlkey=dp9oiqcibo4kigeq8lpzk8s0o&dl=0 running spring with a 32-bit launcher gives me Error: Failed to allocate memory 100% of the time I run it with UseVBO=1, 64 bit launcher gives me the graphical problem with UseVBO=1, and both work fine with UseVBO=0 quake 2 issue seems resolved if I change the openGL version, though it did work fine with previous settings before changing the graphics card, apparently this is a known issue pending future release.
The quake 2 particle effect bug is a known issue - a fix is ready for this internally, pending a new release.
Not familiar with those warcraft 3 bugs, however. Are both of the issues seen in wc3 intrinsic to AMD GPUs, or is the access violation generic?
For some context, the AMD OpenGL usermode driver was completely overhauled about year ago with 22.7.1. There were a decent number of bugs to begin with, but they got hammered out over time.
I’m not certain the access violation is intrinsic to the GPU or not, as I didn’t test these games on this computer with the old GPU, but it seems so, since if I set UseVBO=0 with a 32-bit launcher to run spring engine, it runs fine with no graphical bugs, but with UseVBO=1 it crashes with Error: Failed to allocate memory(and no other information). When I use a 64 bit launcher, UseVBO=1 gives me that graphical bug and UseVBO=0 runs fine. Here is a link to the wc3 crash log, if that helps. https://www.dropbox.com/scl/fi/xrfw98rs7yhy356gt725g/2023-07-30-12.35.02-Crash.txt?rlkey=dp9oiqcibo4kigeq8lpzk8s0o&dl=0 For reference I can run all of these programs on an older computer running windows 10 64 bit with 2 geforce 970s. I’ll try swapping out the old graphics card (if I can get it to work) and see if it’s a gpu problem. edit: wc3 map loads on both running it with -opengl. spring loads with the nvidia card just fine with UseVBO=1 on 32 and 64 bit launcher, with no graphical issues, so that seems like an opengl amd bug (probably similar to the quake 2 bug?). Also note: warcraft 3 had no bugged cursor with the old nvidia card, but had some bugged white bar next to it with this card (cursor is fine running it with -opengl)
Sorry, to clarify, were you always running WC3 under OGL whilst encountering these visual defects?
No, with the old graphics card that minor graphics bug did not happen, with or without the -opengl setting. It seems like the graphical glitch happens on the new car with opengl enabled or not, it just took a bit to come back.
Oh right. It’s strange that this occurs regardless of which graphics API is in use. We can take a look into it