Hi @Qoojo,
I get your point, but I have already reported it to them. Anyway, as I mentioned, it happens in two completely different projects. Additionally, the most basic one (in terms of Unreal's technology) is also very, very simple overall—just a small baked map with a VR pawn. What should I do? I'm not even using C++, and the usual nodes… well, they are just the standard nodes we can use. What else?
Moreover, Intel seems to work fine too (though I can't confirm this with absolute certainty).
In summary, there's nothing more I can do to find additional workarounds beyond what I've already tried. I'm simply asking AMD to run a quick test to confirm whether it's an AMD issue, that's all. Surely, they have Nvidia and Intel GPUs to compare with and can conduct a deeper analysis of the situation, as the issue is very basic. We could even say that Unreal Engine’s core functionality is what’s causing AMD to crash, and I believe Unreal is an important game engine worth addressing.
If AMD wants us to believe their drivers are just as good, maybe they should ensure they work just as well when using the basic, default settings in projects made with such a major engine as Unreal. I’m even offering my project for them to test—it’s a symmetric relationship, simply put. As I said, using the common configuration and default nodes, there is one (or rather, two) GPU brands that just work. Should it really be my responsibility to break my head trying to make the other brand work too? Sometimes even Epic and GPUs brands work together to make things work.
