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. 👍
Where can I contact AMD? I do own a computer with the issue.
By the way, the issue isn't very hard to replicate at all. Just have an AMD card. I've tested over 5 different cards, and every one had the issue. You can imagine my despair when I have a game that uses 3D set to release in October. Due to this issue I'll have to delay it for sure.
In my opinion, it doesn't matter if it's AMD, WebGPU, or whatever issue - as one of the creators of the engine that has the issue Ashley , it should be your job to go after the issue and try to understand it better. As an end-user, I don't know how you've programmed the 3D in the engine, so even if I reach out to AMD, how am I to explain what's the engine doing?
I hope that turning the WebGPU option off helps somewhat, but now I have to go through my entire game and check out if anything has changed. I'll still try to contact AMD though.
Once again, just a heads up for anyone who comes to the thread wondering why their 3D game is broken in C3 - right now, no AMD cards can run the 3D Construct games properly.