I get a scene like this in most of the default projects, and my own projects as well. If I don’t disable mobile HDR, I always get screens like this:
The game is responsive and running (I can hear sound effects playing, for example), and the virtual joystick UI draws properly, but the visible scene is garbage.
Turning off mobile HDR before deployment seems to ‘fix’ the problem.
Platform is Nexus 7 2012.
Howdy ryani,
Thank you for reporting this issue. I am just going to need a bit more information before i begin digging into this issue. Would you be able to clarify which version of UE4 you are currently using when you are seeing this error? Also, above you say that the scene looks like this is most default projects. Would you be able to list which project(s) you are mostly seeing this error on?
Any additional information would be greatly appreciated.
and have a great day!
Hi Sean! I have seen this problem on Github builds of 4.4, 4.5, and 4.5.1. You should be able to create a default first person project (C++ or blueprint) and deploy onto the Nexus 7 device to reproduce the problem. I have not tested 4.6 yet.
Hey ryani,
Thank you for reporting this issue. I have been able to see the error that you seem to be running across. I have entered UE-6401 into our bug database so that the issue may be resolved in a future release.
and have a great day!
Hi, I have a problem for the same issue. My UE4 version is 4.12.5. I want to know what is changed for UE-6401. Please let me know the URL or web page where fixed code to integrate that code.
This is the updated link: Unreal Engine Issues and Bug Tracker (UE-6401)
While looking over the internal report I noticed we don’t have a fix Change List entered. This means that the issue was possibly fixed by some other change and we didn’t reproduce the issue in 4.12.
Unfortunately, there really isn’t a way to track what code could have fixed the issue without doing a major regression test that would involve syncing individual changes and checking to see when the fix occurred.
If you are up to date in 4.12 you shouldn’t be experiencing this issue. If that is the case please make a new AnswerHub post under the bug reports section as this will need an investigation.
,