Hi! We’ve noticed visual artefacts with some Niagara effects in our game, particularly with the ones that use multiple meshes for particles and select meshes based on MeshIndex parameter. This happens on multiple Adreno GPUs, the one I’ve checked in particular - Adreno 750, Samsung S24 Ultra. Please check the video attached.
I’ve managed to reproduce the issue within a clean project on 5.5 with both our effect (that I’ve migrated and also included in the archieve) and on the default emitter preset within Niagara called MeshArrays. The particles on the default emitter just blink but on our NS they also seem to have vertices messed up and cause significant artefacts.
Could you please help on investigating the issue?
Best regards,
Daniil
Steps to Reproduce
Package provided project for Android (I’ve included archived android build as well just in case) and run it on any device with Adreno GPU, there’re particles that has visual artefacts and glitches on the level.
The sample project also includes our DefaultScalability.ini and DefaultDeviceProfiles.ini files. Also we’ve modified /Script/Engine.RendererSettings in DefaultEngine.ini.
Niagara assets with the artefacts are located by these paths:
Content/VFX/Niagara/Systems/DestructablesVFX/NGS_WoodenBoxesDestruction.uasset (the one from our project)
Content/EffectAndStuff/TestVFX.uasset (the one with default MeshArrays emitter, to which I’ve added rotation and set another meshes instead of default ones)
Hi! I’ve got a minor update on this, it might be not only Adreno GPUs but others as well, if I’m not wrong someone had the same issues on Mali-G76.
Regards,
Daniil
Hi Daniil,
We are aware of an issue ressembling this affecting Adreno GPUs after V@0676.11 and before V@0800.17.11 where the issue was resolved by Qualcomm. Is this the case for the issue here?
Best regards.
Hi [Content removed]
Yes, it’s the case for me because what I have on the device is V[Content removed] although it’s the most recent OS version for the device (s24 ultra).
So the user (at least on Samsung) won’t be able to update the driver as well and the only thing we can do is to disable the feature usage based on driver version I guess.
Regards,
Daniil.
Hi Daniil,
The following CL may serve as a workaround: https://github.com/EpicGames/UnrealEngine/commit/9fcf684b02dc2c6bc8cec88c26bdac4b66fdcf1c
Other users have also seen the following change resolve the issue, however, from our tests, this isn’t 100%.
[Image Removed]
Best regards.