This question was created in reference to: [texture load issue related to material [Content removed]
We are still seeing this issue after merging in the suggested fix.
This is plaguing our VFX team. It shows itself as either invisible, or grey/default textures being used in effects until the texture uasset is opened. This only happens in editor, PIE and has been seen in micropatch builds. We have never witnessed it in a packaged build.
Unfortunately, this bug doesn’t seem to have a consistent repro. Some days you get textures, others you don’t.
Has this issue been reported since the 5.6 fix? Or are there any other CLs that were necessary to grab? Thank you
Hi Daniel,
As far as I know, there have not been many reports lately about VT loading issues. We still have another CL related to a common VT crash that occurred in 5.5 that we ask licensees to integrate, but this is about a crash you do not seem to encounter. Maybe you can check if you have it integrated already (the screenshot of the diff should be attached to this message). Otherwise, do you recognize any patterns with the textures that are not loaded correctly? Are they always the same ones? Are these merely SVTs or also RVTs? Could you also post the CVars you used to set up your VT system? Lastly, if you can figure out some way to consistently reproduce your issue, however likely, that would be the most surefire way to find the root cause of your problem. Please let me know your thoughts on this.
[Image Removed]
Thanks for sending the videos and the extra info. I have also reached out to the team in charge of materials, so I am hoping I can get some more information from them. As we will be on summer break for two weeks starting next week, it will likely take some time until I hear back from them. If, in the meantime, you find a fix for this, please don’t hesitate to drop a line here. Please let me know if this issue blocks you at the moment. If so, let me know, and we can look into getting you some extra help.
Hi Daniel,
Our dev team said that the issue has been solved in 5.6, so perhaps you can backport the fix: Unreal Engine Issues and Bug Tracker (UE\-239365\). The CL with the fix should be 39490945. Let me know if this is a feasible fix for you
I am sorry for that, I overlooked that bit of information when I wrote my reply. It seems this is a new issue, which we have not encountered. I have gone ahead and created a ticket with the dev team, which is going to investigate this further: Unreal Engine Issues and Bug Tracker (UE\-305449\). I know you mentioned this loading issue happens sporadically, but are there any further details you can share with us that can help us consistently reproduce the issue? This would help us a lot in finding a potential fix.
Otherwise, do you recognize any patterns with the textures that are not loaded correctly?
Only our VFX team has noticed this issue. So that points to either Niagara or their Uber material. After posting this question, I did make some changes to fix preview material compilation failures due to preview textures not being set. Time will tell if that was the cause all along.
Edit: Out VFX team informed me that they have reproed this outside of their Uber material. Additionally, it seems to get worse and affect more textures the longer they work or the more assets they touch. So that makes me think texture pool saturation?
Are they always the same ones? Are these merely SVTs or also RVTs? Could you also post the CVars you used to set up your VT system?
This is happening with regular streaming textures. Not VTs.
I’ll add some videos below showing how this looks for us.
Apologies for the cursed format, but you can see how we have default textures on the material until we open the source texture.
And in this case, the texture is just invisible, rather than default, until the source texture is opened.
No, not blocking yet. I’ll try and get you some more info by the end of the week.
As I noted in the original post, I have already merged that CL and the issue persists.