Search Issue Tracker
Not Reproducible
Votes
0
Found in
Issue ID
1096935
Regression
No
[Desktops][Standalone] Error in the Console during the building process.
"Invalid Cached Offset" error repeats about 2-200 times during the standalone building process.
However, it does not interfere the building process, nor the standalone Player is affected in any way.
It has a steady repro rate on OSX and Linux, but only seldom happens on Windows.
it does NOT happen when using an empty project. And if the user does NOT delete the previous built Player and choose to replace it from Editor, it does not occur.
Repro:
1. Use Desktop Test Project: https://oc.unity3d.com/index.php/s/02e5rMzd00a9WzX
2. Launch & build project with Trunk build.
3. Observe the Console window
Expected: No error generated in Console window during building process.
Happens on: Trunk (295800b35288)
Comments (2)
Add comment
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
mcroswell
Nov 20, 2018 22:40
I had this error in PlayMode (not a runtime and not with any build). This occurred with 2018.3.0b7 and OSX 10.12.6 and was solved by making one of my models into a prefab. I did this because I looked at the detailed stack-trace (from the console) and saw some remarks about prefab building. Anyway, after days of this thing bugging me every time I went into playmode, it has now disappeared. Hopefully, my comment help someone.