Since I finally got 4.15.1 up and running with FMOD and my project seems to work as expected after upgrading to 4.15.1, I decided to give monoscopic renderer a spin.
Sure enough right after level was loaded (streamed), the app crashed. Here is logcat:
Galaxy S6 Android 6.0.1 Exynos / Mali
I reported this to Oculus and they said it’s due to CaptureSceneToScratchCubemap being called. I have Reflection Capture sphere in my scene as I need it to achieve better lighting for Sky Light. All lights are static / baked. And it shouldn’t really matter because what if I want to use reflection capture for reflections and whatnot?!
As per usual when reporting a crash bug, I need a way to reproduce this issue on my end in a new blank project in order to report this as a bug.
Using reflection captures is useful in VR so do not worry about that as much. I need a minimal test case, without FMOD plugin etc. so I can report this issue internally.
Alright, I made basic project (I have basic Gear VR template I used for all “blank project” tests) and it worked (didn’t crash).
Apparently it’s not reflection capture that causes the crash.
I have stereo layers, streaming levels, animation, particles, etc. in my project. So the only thing I can do at this point is upload my project and share download link with you or anyone else from Epic, privately.
It falls on the user to narrow down a repro case in a blank or minimal project to showcase the issue. It is not our responsibility to take user’s projects and figure out where and/or how the issue being described is occurring. We can offer suggestions or tips based on the evidence presented, but we simply do not have the resources or bandwidth to be able to test every users project and determine where the bug is occurring.
This does not mean we will not help, just that when writing a bug report, we need to provide a very minimal test case for our engineers to quickly identify the issue without having to sift through a number of content or irrelevant variables which could misdirect them to looking at something unrelated. Let me know if you have further questions.
I think I got it, but not really seeing anything useful (not sure what I need to look for, besides “crash”). PM’ed you on the UE4 forums with the link to the log file. Thanks.
Well, I ran monior.bat after I ran blank project (the one that doesn’t crash) and I had exact same errors (and more) as with the project that crashes. So none of those contribute to the crash.
Run a diff checker between the two logs to catch any outstanding differences that might exist. Then use that as a basis to find and determine where the project could be failing.