I have a "Boot" scene as a Buildin resource and a "SampleScene" scene as an Addressable resource. When I build it as a meta Android app and run it, the "Boot" scene is loaded by default. Then, in Start, the "SampleScene" scene is loaded using Addressable (LoadSceneMode.Single). However, when I use the Profiler analysis tool to check the number of triangles being rendered, I find that occlusion culling is completely ineffective. But this is normal in the Unity Editor (including when loading with Use Existing Build) and android phone.
There is a problem on the Unity forum about Occlusion Culling not working. The solution provided is to reset the ActiveScene in the frame after loading the scene, but this does not work on Meta devices. Has anyone encountered a similar issue? Or are there any possible solutions to try?
