Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
625951
Regression
No
Unity replaces original scene when importing it after it was exported as a package
Unity replaces original scene when importing it after it was exported as a package and renamed in another project and exported back.
1. Create a scene in Project 1
2. Export it as a package (scene 1)
3. Import exported package in a new Project 2
4. Rename scene (-> scene 2) in new project and update it (so it'll differ from original)
5. Export new scene as another package (scene 2)
6. Open original (Project 1) project and import new package (scene 2) into it
Expected: Scene 2 is a new scene next to Scene 1
Actual: Scene 1 gets updated with new content (replaced by scene 2 content).
At least this is the flow I've assumed would work and found this (IMHO) not quite logical behaviour.
Not a regression against 4.3.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment