Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.3
2019.3.4f1
2020.2
Issue ID
1226326
Regression
No
Domain isn't reloaded when using Protobuf-net
How to reproduce:
1. Open the attached project
2. Open the "TestScene"
3. Open the "script" Script from the "Scripts" folder which is in the Assets folder
4. Change the Debug.Log string at line 11 from "Test1" to "Test2"
5. Save the Script and get back to Unity Editor
6. Enter Play Mode with the Console window open
Expected result: Console window outputs "Test2"
Actual result: The domain isn't reloaded and Console window outputs "Test1"
Reproducible with: 2019.3.8f1, 2020.1.0b3, 2020.2.0a5
Could not test with: 2017.4.39f1, 2018.4.20f1, 2019.3.0a11 (errors when downgrading the project), 2019.3.0a12 (License error)
Notes:
-The Console window will only output "Test2" after restarting Unity Editor or reimporting all of the Assets
-When all of the Assets are reimported an error message appears: "Error: Could not load signature of ProtoModel:Write due to: Could not load file or assembly 'runtime, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:runtime, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none>"
-The mentioned error doesn't seem to occur when launching a fresh project but only after clicking "Reimport All" in the Project window
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note:
This doesn't seem like a problem with Unity, inspecting the ProtoModel assembly in dotPeek shows that there is a missing "runtime" reference (as you can see in the error message as well). The missing reference will cause the assembly not to be compiled.