Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Beta WebPlayer "Failed to initialize player's 3D settings"

Discussion in 'Unity 5 Pre-order Beta' started by OP_toss, Jan 16, 2015.

?

Are your Unity 5.x Beta WebPlayer builds working?

  1. No, they've been broken ever since 1/15/2015

  2. Yes, they still work fine

  3. No, they've been broken even before 1/15/2015

  4. Sometimes they work, sometimes not

Results are only viewable after voting.
  1. OP_toss

    OP_toss

    Joined:
    Oct 19, 2012
    Posts:
    19
    Hey guys,

    I seem to have royally messed up my Web Player somehow. I don't think I changed a thing, but today all of a sudden my old and new Web Player builds made with Unity 5 beta don't work!

    I'm using Unity 5.0.0b18 with it's matching b18 Web Player.

    • I've rebooted.
    • I've uninstalled all things unity (beta, nonbeta, webplayers).
    • I've deleting all temp folders and appdata folders.
    • I've reinstalled b18 and only b18's webplayer.
    • Same error.

    • I've tried using Chrome, Firefox, and even QtWebKit.
    • Same error.

    • I've built a simple empty scene with a sphere using 5 beta.
    • Same error.

    • I've tried using old builds that worked yesterday.
    • Same error.

    • I've even tried using old builds and my sphere test on a DIFFERENT MACHINE that was also working yesterday.
    • Same error.

    This last test tells me it's not just my machine! So either Unity5b18 has been expired remotely, or the referenced JQuery/UnityObject2.js/w3 in the html file were changed, thereby breaking all previous beta webplayer builds.

    Can someone from Unity explain what happened? The only thing left to try is b19, which supposedly has "minimal testing", but I'm out of ideas.

    Any help or ideas would be greatly appreciated!
     
  2. fasyoki

    fasyoki

    Joined:
    Dec 22, 2014
    Posts:
    2
    Same problem here. I also had the same problem with b19.
     
  3. OP_toss

    OP_toss

    Joined:
    Oct 19, 2012
    Posts:
    19
    Yep I just installed b19 and the problem persists. I'm NOT CRAZY! :D
     
  4. TeamZero

    TeamZero

    Joined:
    Sep 3, 2013
    Posts:
    30
    Same problem with me. Beta 19. Web builds worked yesterday, but not today. Didn't change anything.
     
  5. joker999

    joker999

    Joined:
    Dec 4, 2013
    Posts:
    1
    Everything was working great until today (1/15) and now they're all broken.
     
  6. AustinRichards

    AustinRichards

    Joined:
    Apr 4, 2013
    Posts:
    321
    Make sure you're not using streamed web player. I've noticed streamed doesn't work, but non-streamed does.

    Edit: This just started to happen to me with beta 19... Not even with streamed webplayer (which is broken as well in a different way). I can't even test my game out over web player now D:

    Log File:
    Code (CSharp):
    1. 150115 23:52:05 ------------------------------------------------------------
    2. 150115 23:52:05 Instance starting, version 5.0.0b19_59056f3f1abe, UNITY_WEB_ENABLE_AUTODOWNLOAD: 1, GetDisableAutoUpdates(): 0
    3. 150115 23:52:06 Datafile file:///B:/Garrett/Files/Dropbox/Public/Build%2017.unity3d
    4. web: player version 5.0.0b20
    5. web: load mono
    6. Mono path[0] = 'C:/Users/Garrett Richards/AppData/LocalLow/Unity/WebPlayer/player/Beta5.x.x-Development/Data/lib'
    7. Mono path[1] = 'C:/Users/Garrett Richards/AppData/LocalLow/Unity/WebPlayer/mono/Beta5.x.x/Data/lib'
    8. Mono config path = 'C:/Users/Garrett Richards/AppData/LocalLow/Unity/WebPlayer/mono/Beta5.x.x/Data/etc'
    9. PlayerConnection initialized from  (debug = 0)
    10. PlayerConnection initialized network socket : 0.0.0.0 55107
    11. Multi-casting "[IP] 192.168.1.122 [Port] 55107 [Flags] 2 [Guid] 4241877207 [EditorId] 4294967295 [Version] 1048832 [Id] WindowsWebPlayer(AustinRichards) [Debug] 0" to [225.0.0.222:54997]...
    12. web: start, src=Build 17.unity3d abs=file:///B:/Garrett/Files/Dropbox/Public/Build%2017.unity3d flags=0x1
    13. PlayerConnection already initialized - listening to [192.168.1.122:55107]
    14. web: sucessfully initialized
    15. 150115 23:52:06 loader: start ok
    16. 150115 23:52:08 Times: download 0.5 load 2.5
    17. PlayerInitEngineReload settings: Could..... not preload global game manager #17   i=5
    18. 150115 23:52:09 Setting error display: 'Failed to initialize player's 3D settings.', details: '', link: 0
    19. web: shutdown player
    20. web: shutdown finished
    21. 150115 23:52:09 loader: final cleanup
    22. 150115 23:52:09 loader: unload unity dll
    23.  
     
    Last edited: Jan 16, 2015
  7. TeamZero

    TeamZero

    Joined:
    Sep 3, 2013
    Posts:
    30
    Downloaded Beta 20 this morning (along with the B20 web player). New web builds with Beta 20 are working for me.
     
  8. OP_toss

    OP_toss

    Joined:
    Oct 19, 2012
    Posts:
    19
    Good to hear. But this means any Beta builds built before version b20 are now and forever broken? Seems like only a partial solution, but I suppose it's in Beta so we can't complain too much ;)

    That being said, I'd love to hear something more official from Unity as to what happened. I read through b20's changelog and I couldn't see anything relevant to this significant issue.