Recent AMD driver to fix voxels

[MaximumDoom]

Hi there.

Some good news, AMD emailed asking for all the info on the voxel bug, they sent everything over. Should get a reply after the weekend.

[gulshan212]

Hello this is Gulshan Negi
Well, I am a newbie here. I will recommend you visit AMD support or check their website for any specific driver updates related to voxel performance. It's also a good idea to make sure your graphics card is compatible with the software you're using and that it meets the minimum system requirements.
Thanks

[MaximumDoom]

Hi there.

Email from the AMD forum admin AMD_Matt, they are investigating the issue and AMD are requesting the GZDoom developer Graf to follow up on the AMD OpenGL thread.

This is the email sent to me.

"Thank you for your email.

We have one of our AMD Developer Guru's looking into this issue, you referenced the thread link earlier.

Please ask the engine developer to follow up on this discussion and provide the requested information. [Glitch] AMD Driver 22.4.1 and 22.5.1 have trouble... - AMD Community

https://community.amd.com/t5/opengl-vul ... m-p/526470

Alternatively, if the issue relates to a different game, a new discussion can be posted in the AMD Dev Guru OpenGL forum where an AMD Dev Guru engineer will investigate OpenGL & Vulkan - AMD Community

New AMD Dev Guru members are first required to post in the Newcomers Section in order to be granted access. Newcomers Start Here - AMD Community

https://community.amd.com/t5/newcomers- ... omer-forum

Please pass this information along to the developers so they can post in the relevant discussion.

Best Regards,
Matt"

Mr Graf can you take 5 mins to contact AMD Dev Guru thread and they will provide the info needed to update GZDoom.

Cheers.

[Rachael]

Again and again and again I have to keep repeating that OpenGL is deprecated for GZDoom on AMD cards and IT WILL NOT BE SUPPORTED. Do you really have that much trouble reading? Please quit passing responsibility for AMD's screw-ups to us. If they want to fix it, GZDoom and the required mods are easily attainable, and they can run it with FreeDoom to avoid paying for any game licenses they won't need. AFAIK though, it's fixed in the most recent driver anyhow, so all of this is probably just a huge ass nothing burger.

If you want the AMD devs to look at it, create a package with GZDoom, FreeDoom and some models and/or voxels and let them look at it - but this is not our problem. It runs fine on Intel, it runs fine on NVidia. It runs fine on AMD drivers older than a certain date. It runs fine on AMD when running Vulkan with pretty much any recent driver. The shader is open-source for them to look at. Is this really that hard to understand?

If you are running a recent enough AMD card to be affected by this bug, it runs Vulkan, and that's all we will support, at least for AMD cards. In other words - stop using OpenGL! Switch to Vulkan. It's very easy to do in GZDoom. If this one simple step escapes you, one that actually will fix your problems, then you are simply beyond help.

There are multiple ways to get Vulkan (any of these 4 methods will work, pick the one you're most comfortable with):

• Start GZDoom with the startup parameter "+vid_preferbackend 1"
• While GZDoom is running, open the console with Tilde (~) or for European keyboards you might have to use quote (') or backtick (`) - and type "vid_preferbackend 1" - then quit the game and restart.
• In the menu, go to Options->Display Options->Preferred Rendering API, and press the Right Arrow Key until "Vulkan" is selected, then hit Escape until you are in the main menu and Quit the game and restart.
• If you are using the advanced menu, go to Options->Set video mode->Preferred Rendering API, and press the Right Arrow Key until "Vulkan" is selected, then hit escape until you are in the main menu and quit the game and restart.

I'm locking this thread because you continually ignore me and this is going nowhere.

Stop making this our responsibility. We are not entertaining this issue any longer.

[MaximumDoom]

Hi there.

You have a serious problem on this forum, the admin, what a piece of dog shit.

Now I know why none of my friends would join this forum, absolute dog shit!

Graf your engine is crap, is does not work, if AMD was so bad then why is it on the Steam Deck?

Also you got all salty over Lilith..WAD HA, well guess what, your engine is broken as shit pal, piss poor workmanship.

[yum13241]

I know I shouldn't engage, but the following is misleading at best and misinformation at worst:

If AMD was so bad then why is it on the Steam Deck?

The Steam Deck runs Linux, AMD + OpenGL + Windows is what's broken.

This is what I call "being a parrot".

Also you got all salty over Lilith..WAD HA, well guess what, your engine is broken as shit pal, piss poor workmanship.

Sounds like you just got into Dwars. (no hate to him)

[Rachael]

Adding his PM because it was too absurd and ridiculous not to post it.

So you lock my thread when I wasnt even speaking with you, you claim AMD has stopped development for OpenGL? WRONG! Did You even read my last post you idiot, AMD are investigating the issue and are going to fix it but you, whatever your fucking name is, it isnt racheal, your a fat bloke in a dress pretending to be a woman! HA you fucking beta male soyboy! Disgusting socialist leftist scumbag that who you are!

I was trying to help and you just lock the thread because you cannot be bothered to fix this mess!

Now I know why no-one wants to join this piss smelling forum.

Obviously this user has already been banned by another moderator - so nothing more needs to be said - except this: if you're going to be a shit bag, fucking OWN that shit! Don't be trying to hide it by putting it in my PM box. That's cowardly. Put your shittiness where everybody can see it so we can all laugh at you.