Search Issue Tracker
Won't Fix
Votes
3
Found in
2022.3.60f1
6000.0.44f1
6000.1.0b12
6000.2.0a7
6000.3.0a1
6000.4.0a1
Issue ID
UUM-101289
Regression
No
“Attempted to insert duplicate object ID hash <hash> into atlassing lookup map.” error is thrown when trying to bake lighting of Terrain GameObjects within additively loaded scenes
Reproduction steps:
1. Open the attached “Unity-TerainTest” project
2. Open “Assets/_App/Scenes/Default-Scene” Scene
3. In the Lighting window (Window > Rendering > Lighting), press “Generate Lighting”
4. Observe the Console
Expected result: No errors are logged
Actual result: “Attempted to insert duplicate object ID hash <hash> into atlassing lookup map.” errors are logged, followed by “[Progressive] Mismatched instance material bindings.“ error being spammed
Reproducible with: 2022.1.0a1, 2022.3.60f1, 2023.1.0a19
Not reproducible with: 6000.0.44f1, 6000.1.0b12, 6000.2.0a7
Fixed in: 2023.1.0a20
Reproducible on: macOS Sequoia 15.3.2 (M1 Max), Windows 11
Not reproducible on: No other environments tested
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
This is a valid issue, but due to it only affecting 2022.3, and the risk of regressions being relatively high, we will not fix it.
This issue will primarily happen in the case where you have a scene that contains a terrain, then duplicate that scene, additively load it, and bake both the original and the duplicate together. In that case, the baker will mistakenly view both the original and duplicated terrain as the same. Modifying the terrain will not fix this.
There is however a simple workaround. For each problematic scene, take the following steps:
- Create a brand new scene
- Copy all of the gameobjects from the hierarchy of the original scene to the new scene
- Save the new scene, and use that instead of the original problematic scene
Doing this will effectively re-generate all the identifiers that the baker uses to represent the terrains.