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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.