3D Rendering Sorting Issue with newer AMD GPUs

Some of the play-testers, for my game, with specific AMD GPUs appear to have a 3D rendering sorting issue like below:

The affected cards are as follows:

AMD RX 6650 XT

RX 7800XT

RX 6700XT

rx 6800s

RX 5700 XT

I have tested it on a Radeon 580 and the glitch did not occur, which leads me to believe it could be related to the new architecture of these newer cards. (RDNA 1 / 2)

I didn't do a bug report on this issue because I do not have access to the newer cards and so I can't replicate it for myself. And also because I can't be sure that this isn't just something to do with the Web GPU settings that my game has enabled.

Does anyone have any idea what this could be? This glitch has never appeared on any other graphics card.

You should make a bug report on github with what you have regardless, this is not a good place to make a report if you hope to eventually have action taken.

I still don't know if it's a bug or if its a project setting, I was wondering if anyone had any idea what could be happening or if perhaps they had one of the graphics cards listed.

The first thing to look out for with this kind of issues is making sure the devices have an updated browser and updated graphics drivers.

Old GPU drivers are the number one cause of weird graphical problems that seem to make no sense.

Thanks Diego, these play testers have said they have updated drivers.

UPDATE: The issue comes from "--in process-gpu", however removing this removes the steam overlay support.

I'm afraid graphics driver bugs are a nightmare. Often there is no good solution other than to try to get the vendor to pay attention and fix the bug, which can be arduous.

--in process-gpu is a custom Chromium engine flag that may not be supported by Google. You could try reporting it to them, but they may just say that's not a supported mode.

The reason Construct uses that flag is to work around another bug: that the Steam overlay doesn't work without it. Developing for the overlay is a nightmare as the Steam overlay seems hackily implemented and has various bugs that make it harder to integrate. We keep trying to ask Valve to improve or fix it but they generally just ignore us; we ask customers to ask Valve to improve it to increase the pressure, but generally if people can get by with workarounds then they don't bother. So we end up using --in process-gpu long-term as a workaround, but workarounds don't fix the underlying problem, and sooner or later you run in to some other problem and get cornered as there is no way to have everything working.

So I'm afraid we've done the best we can with Construct given the hacky/broken Steam Overlay and graphics driver bugs; for further help you'll have to contact other companies. Ideally Valve would make an overlay that can be more easily integrated!

Hello!😊 Can you please!! I kindly ask you to write in more detail, preferably with screenshots - where is this setting, or what is it - how to fix this error on these video cards (my project is not for Steam, and I really need to know how to fix it) I just didn’t understand a lot .. ..(is this --in process-gpu??). I would like to ask you to help me on how to run my project so that it runs correctly on video cards in the firt message. Beg!😰😥😭😭

Hi! You need to use version r388-2 and switch compositing mode to low-latency, and make sure "use worker" and "enable web gpu" are set to NO.

You have to use that specific version of construct because they don't support the compositing mode feature anymore.

construct.net/en/forum/construct-3/how-do-i-8/restore-compositing-mode-182909

This is still an on-going issue, and now it's affecting browsers too, when it wasn't before - so maybe it's a chromium issue?

Ashley

Just further on this. It seems to effect other browsers aswell, not just chrome. Using Webgpu removes the issue, and the issues seem to effect all AMD RX cards, but webgpu causes other issues at this time on several projects.

And to pinpoint the issue, what happens is any 3d object or sprite with a transparent or semi transparent pixel inverts its zdepth so it appears ontop of everything infront of it.

I don't have much more to add, other than: yep, that sounds like a graphics driver bug. I've seen such issues plaguing software and game development ever since I started coding around 20 years ago. They're a total nightmare.

Your best bet is still to try to get in touch with AMD - or perhaps report it to the browser vendors who may be able to figure out a workaround. For our part, even if we wanted to try to help, we'd have to start by ordering in affected hardware and building a system that reproduces the issue, which may then not reproduce the issue because it actually depends on something we haven't figured out yet; even if we reproduce it, it may be impossible to work around in our engine anyway, in which case we're back to square one. I've attempted such things in the past and generally it's hopeless, so it's best to follow up with browser vendors or the GPU vendor who are generally better prepared to deal with such issues.

If using WebGPU works around it but there are other issues, you can report those to us, or list them here if they are already reported, and I will try to prioritize them. The architecture of WebGPU allows for much simpler drivers, which should hopefully make cases like this much rarer. In the long term our goal is to move to WebGPU by default and ultimately (probably very far in future) retire support for WebGL.

Ashley

Yea I'll work through the bugs with webgpu to make them easier to spot on what causes them. I have contacted AMD but because I don't have an RX they are putting me through diagnostic procedures I can't do haha.

Yea webgpu fixes it but not on node webkit, I'm unsure if this is because node webkit may be defaulting to webgl regardless? (Is this a bug not allowing webgpu on nwjs, not sure)

The bugs I have on webgpu are probably easier to sort if I isolate them then pass them over to you in the usual bug reporting. 👍