@EMvirtualprod
That is exactly same thing as disabling Oodle or other plugin, that people here said this fixed for them the problem.
The shader cache is refreshed after you change drivers or the game executable receives any update.
This problem don’t appears if shaders are rebuild since it checks the materials from current scene, problem will appear again later when the engine doesn’t check these shaders for a while, few days, a week etc.
What is happening:
The engine simply gets stuck for a few seconds when move the camera in the viewport then some of the materials from the scene turns into black. If more more camera, other materials follow same thing.
The first time this happened to me is when I was building a scans library 150gb or so of assets, some of the assets like rock or cliffs started to turn into white - black. The large textures starts first. Restarted the engine, all ok for a few seconds then same thing repeats.
If rebuild shaders problem don’t appears but after a few days starts again.
Same with resave all textures.
Same here. 5.5.0 - 5.5.3 (4060 Ti or 4070 does not matter). Opening all textures in editor once (even without saving) usually “fixes” this issue for a while for me but it’s no real solution.
I’m on 5.5.1, and I’m having this problem as well. I’m assuming by the posters here, that 5.5.2 and 5.5.3 have the same problem, so I may as well wait until the next version.
The weird thing is, it only just started happening a few days ago, and I’ve been on 5.5.1 for weeks now. I didn’t even do any art-related stuff this week, and sys/video memory is definitely not full. And I’m on the same video drivers as I was weeks ago. Nothing has changed basically. I mostly have done coding and started working with metasounds recently since the texture problem started.
The way I “fix” it temporarily, is just open the textures up, and then they load into memory (and then appear in the level.) The problem is, that random textures keep popping up like this.
Luckily for me, I’m not far enough into my project to worry about it… but May seems pretty far away for what feels like a game-breaking problem? I’d hate to be a studio that can’t fix this problem and they’re ready to ship.
Could we at least get some details on why/where it’s occurring and how we could maybe workaround the problem?
Like I mentioned before, this wasn’t happening to me for weeks, then all of a sudden, I switch maps and as you walk around it gets choppy and keep nulling out all those textures until half the objects turn black/shiny. Did it start happening because of total assets reached a certain size in the project? Would deleting unused assets from the project help reduce it?
“Q&A still has not blessed it yet but its in their que.”
I’m a little lost in the lingo here, does that mean this fix will be in 5.5.4? Also is 5.5.4 even a thing if 5.6EA is planned for May? I rather not make more major upgrades to my project version if possible.
It’s good to hear it’s going to be fixed in 5.6, for anyone struggling with the issue before that version. As someone said before, saving the texture file helped for me. If there are a lot of files containing this problem, go to the top of your Content Browser, search for ‘Texture’, and shift-click to select how many you want, right-click and press save. This will fix all of your files!