That was a dead link for me…
At any rate, I somehow got this to work.
The format for the DefaultEngine.ini IS correct. 4.17 didn’t change that thankfully.
If I had my device connected to my PC via the Android Device Monitor (monitor.exe), while running as Development I could see the logs telling me that I had a valid texture specified instead of the default empty string. I knew it was working in some form though because the initial load and every level transition sent out a debug of “Splash Texture load successful!”
But even with seeing this, for a good while, I still saw nothing. I tried changing all of the variable (distance, scale, etc), thinking it was jsut in the wrong spot, but no change.
Turns out I had to turn off Multi-View & Multi-View Direct. Then it worked.
Oddly though, I turned Multi-View back on, and it still worked. ??? I have no clue what exactly is going on here, but in some ways it makes sense that multi-view could interfere with rendering the Splash screen.
I wish the GoogleVR plugin had a setup like the Oculus one does, where you can simply specify this in the editor. Would make setup a bit easier.
However, now I’m having the issue where after updating to Android 8.0 (is that Oreo?), it crashes on launch 100% of the time. So, I see the Splash screen, and then it crashes.
Basically this issue:
I tried what was suggested there, but now I can’t even get my project to successfully build anymore.
I keep getting this at the very end, during the final package preparation:
D:\NVPACK\android-sdk-windows\tools\ant\build.xml:573: …/support-v4-25.0.0 resolve to a path with no project.properties file for project Y:\JavaLibs\permission_library
I’ve updated the SDK’s, and still busted. This whole week has been very frustrating…