Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Scene loads differently on Android than Editor & native OSX

Discussion in 'Editor & General Support' started by dangerdex, Feb 9, 2017.

  1. dangerdex

    dangerdex

    Joined:
    Mar 15, 2015
    Posts:
    8
    Hello there,

    I'm running into quite a strange bug on my project.

    The long and short of it is that I have two game scenes. GS1 and GS2.

    GS1 and GS2 both contain many of the same game objects. For example, Characters that have the same names and components will appear in GS1 as well as GS2.

    At one point, the player takes an action in GS1 that causes GS2 to be loaded. This is performed as a Single model scene load, not an Additive scene load. I am causing this load specifically with the code

    SceneManager.LoadScene("gs2");
    After this load occurs, I would expect that the first scene is replaced entirely by the second scene. This is what happens on the editor & native OSX builds, and it it what used to happen on Android. Something different happens now on Android, however.

    On all Android devices which I've run the game on, of which there are three, when the screen fades out for scene load and then comes back, the player's position hasn't changed. Neither have the positions of other NPC character objects in the game whose names appear in GS1 and GS2. The stranger thing is that both copies of the objects do not exist. For example, there is a character named P who has a different location in GS1 and GS2. Under normal circumstances, when I load GS2 P exists in the location seen in the editor while editing GS2. However, on Android, loading GS2 results in a world in which only one version of P exists, and it has the location in the game world from GS1.

    To make matters even stranger, when I revert back to a previous version of my codebase in which I absolutely am certain that this was working on Android (I made an APK and distributed it myself), I am now observing this behavior. I deleted the entire code base, redownloaded it from version control, and uninstalled and reinstalled Unity, and still I am getting this bug.

    This is quite a doozy so any help is appreciated. Thanks a lot in advance Unity community.
     
  2. dangerdex

    dangerdex

    Joined:
    Mar 15, 2015
    Posts:
    8
    An update to this:

    I tried deleting every single game object before loading the next scene, and the strange behavior described above still exists on Android and only on Android.