Search Issue Tracker
Won't Fix
Won't Fix in 1.6.X
Votes
0
Found in [Package]
1.6.0
Issue ID
MTTB-1457
Regression
No
Installing Netcode for Entities and for GameObject packages or vice versa throws unclearable "Assembly with name 'Unity.NetCode.Editor' already exists" errors
Steps to reproduce:
1. Create new Unity project
2. Open Package manager window
3. Find "Netcode for Entities" package and install it
4. Find "Netcode for GameObjects" package and install it
5. Observe the Console window
Actual results: Errors "Assembly with name 'Unity.NetCode.Editor' already exists (Packages/com.unity.netcode.gameobjects/Editor/Unity.Netcode.Editor.asmdef)" are thrown in Console window
Expected results: No errors thrown in the Console after installing packages
Reproducible with versions: 1.6.2 (6000.0.54f1, 6000.1.14f1, 6000.2.0b11, 6000.3.0a3)
Tested on (OS): Windows 11
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
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
Resolution Note:
Hey, this is a known thing and from user perspective there should be no use case for having both packages in the same project, if there is some, we will happily see what it is and reopen the ticket if it makes sense. From our perspective there is no use-cases to use both packages
Otherwise it would require us to release a new major package version (for NGO or N4E) since this is a breaking change
Because of this we decided to close it with "Won't fix" resolution
Resolution Note (1.6.X):
Hey, this is a known thing and from user perspective there should be no use case for having both packages in the same project, if there is some, we will happily see what it is and reopen the ticket if it makes sense. From our perspective there is no use-cases to use both packages
Otherwise it would require us to release a new major package version (for NGO or N4E) since this is a breaking change
Because of this we decided to close it with "Won't fix" resolution