Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.0.0f5
Issue ID
498608
Regression
No
Weird error in standalone build after upgrading project to Unity 4.0
Using unity 4 beta everything works fine in the editor but when i build to PC Standalone i get an error saying " mainData is corrupted [Position out of bounds 682596 > 682592] " but the project builds fine in unity 3.5. The error seems to be caused by the LaserTrap.cs script as the error is fixed by removing it from the project. as simple standalone build with this script in the project should reproduce the error.
Build the attached project for Standalone with Unity 4.0 and notice error in the Development Console. User suggests this is a regression from 3.5, but without a 3.5 version of the project, it's impossible to say.
Regression compared to Unity 3.5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment