Inspiring

Baking Lightmaps Breaks Build

11 replies
3393 views

Unity: 2018.3.6f1
Oculus Integration: 1.4

Hi all,

I am currently building an app for both PC and Oculus Quest.

I do not have any significant issues with my PC build.

However, whenever I bake lightmaps for my Quest build, I can no longer load the baked scenes without the app crashing.

When the app crashes, I do not get an error beforehand in ADB Logcat.

Has anyone else experienced this problem?

Corysia

Up and Coming

I'm not seeing that in 2019.1 or 2019.2.

As 2019.3 is an ALPHA release of Unity, you might also ask in the Unity forums. I'm not trying to sound snarky, but my first guess is that this isn't an Oculus thing.

VR Development: https://discord.gg/8R9SHQP Quest Example: https://github.com/Corysia/Unity-Oculus-Example

B

bmoodyP3Author

Inspiring

@Corysia , I am on 2018.3, not 2019.3.

Corysia

Up and Coming

OK! I will go back and sit in my corner now. :p

VR Development: https://discord.gg/8R9SHQP Quest Example: https://github.com/Corysia/Unity-Oculus-Example

M

MikeF

Inspiring

What does your available memory look like before the crash and what compression settings do you have on your lightmaps?

B

bmoodyP3Author

Inspiring

@MikeF , let me check. Thank you for your help.

B

bmoodyP3Author

Inspiring

@MikeF , these are the settings:

B

bmoodyP3Author

Inspiring

I am seeing a big GC allocation spike right before the crash.

M

MikeF

Inspiring

What i mean is the actual texture import settings. Make sure you have proper android compression settings applied and that the lightmap size(mb) doesnt push over your ram limit. Use the ovr metrics tool while running on the device to get a proper readout of how much memory you have left.

B

bmoodyP3Author

Inspiring

Thanks, @MikeF . I was able to keep the app from from crashing by compressing my lightmaps and lowering their resolution significantly.

B

bmoodyP3Author

Inspiring

How do I mark something as answered?