Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.0a11
2019.1.0b4
Issue ID
1134349
Regression
No
Spawning objects via Timeline Signals causes Unity to add the same scene into the Hierarchy
How to reproduce:
1. Open the attached project
2. Open the "SampleScene.unity" scene
3. Press Play
4. Once you see SampleScene appearing in the Hierarchy, pause the Play mode (to prevent Unity crashing)
Actual result: Unity randomly adds SampleScene to the Hierarchy.
Expected result: Unity shouldn't add any scenes into the Hierarchy.
Reproducible with: 2019.2.0a8, 2019.2.0a1, 2019.1.0b6, 2019.1.0a11.
Notes:
Sometimes Unity may crash before the SampleScenes are added to the Hierarchy. (The crash is reported)
Errors are thrown when selecting the scenes in the Hierarchy.
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
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
This is a duplicate of issue #1129866