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. Voting for the Unity Awards are OPEN! We’re looking to celebrate creators across games, industry, film, and many more categories. Cast your vote now for all categories
    Dismiss Notice
  3. Dismiss Notice

*** is corrupted, Remove it and launch unity again??[Position out of bounds]

Discussion in 'Scripting' started by JohnSonLi, Mar 28, 2018.

  1. JohnSonLi

    JohnSonLi

    Joined:
    Apr 15, 2012
    Posts:
    586
    anyone knows how to fix this??
    some particles built into a bundle, when I load this from the bundle, Unity crashed and gave me this error.
     
  2. Rotary-Heart

    Rotary-Heart

    Joined:
    Dec 18, 2012
    Posts:
    804
    I got that error on my serializable dictionary asset. I was using #if UNITY_EDITOR inside a script and my error said if I was using that since it could make a bad serialization. Did you read through all your crash report? I missed that line the first 3 times. Probably it says somewhere why it's crashing.
     
  3. JohnSonLi

    JohnSonLi

    Joined:
    Apr 15, 2012
    Posts:
    586
    I found the problem.... It is an animation problem....
     
  4. Qbit86

    Qbit86

    Joined:
    Sep 2, 2013
    Posts:
    487
    What was the problem with animation? How to fix it?
     
  5. JohnSonLi

    JohnSonLi

    Joined:
    Apr 15, 2012
    Posts:
    586
    I dont find a way to fix it.... Just Delete it and build one from scratch.
     
  6. better_walk_away

    better_walk_away

    Joined:
    Jul 12, 2016
    Posts:
    291
    I just encountered the same issue, had no idea how to fix it.
     
  7. manuelgoellnitz

    manuelgoellnitz

    Joined:
    Feb 15, 2017
    Posts:
    362
    I got the same issue after Updateing Unity to 2020.2.1.
    Builds with 2020.1.16 worked fine, after I Updated newly created builds throw that error with the "resources.assets" file.
     
  8. manuelgoellnitz

    manuelgoellnitz

    Joined:
    Feb 15, 2017
    Posts:
    362
  9. FanManPro

    FanManPro

    Joined:
    Jan 21, 2023
    Posts:
    6
    This issue started happening for me when I upgrade to Cinemachine 2.9.7, it must be corrupting the scene somehow.

    Solution was to simply downgrade to 2.9.5.

    Hope this helps.
    upload_2023-6-1_10-8-38.png