Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
rroye1347's avatar
rroye1347
Explorer
10 months ago
Solved

the "SceneManager.LoadScene" function does not work. Help me

Hello. I was in charge of modifying the Oculus project from 5 years ago. It is a project that uses NGUI and OVRig (an asset that is scheduled to be released).
Since there is not enough time to upgrade to XR, I want to build it as it was before.
 
Unity is version 2019.4.24f1.
 
Currently, I can connect to Link or move scenes well in the Editor,
but when I install the apk file on Oculus and proceed, the "SceneManager.LoadScene" function does not work. All projects are the same.
 
There are no duplicate names in the SceneManager class, it does not work even when loaded with the Scene index, I did not omit the Scene in the Build, and the Scene Name is not wrong. I have been stuck in the current state for a week. Finally, I am posting on the forum to ask for help.
 
Please help me.. It's a life crisis.. Save me.

6 Replies

Replies have been turned off for this discussion
  • hmm.. if you aren't getting any errors during the build process it should be fine.  You could try something simple like  unhiding a cube on LoadScene.  That way you can rule out the SceneManager being the problem.  If that works then it may well be the next step which is the issue.

    It 'may' be because of the Unity version you are using is quite old now.  I would upgrade to Unity 6 if you can but that will more than likely open up a rather large can of worms for an old project, but that may well be what you have to do (I'm currently doing that myself!)

    • rroye1347's avatar
      rroye1347
      Explorer

      I'm trying to upgrade to version 2021.3, but it's a very risky attempt..
      I'm already using a lot of old assets, is there any other way or tip?

      • gavin_prior's avatar
        gavin_prior
        Expert Protege

        Not that I can think of at the moment.  Maybe upload the clip of code that isn't working.  That might give us some ideas.

  • Solved by unchecking Split Application Binary item