Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
Issue ID
1056485
Regression
Yes
Wireframe in 'Baked Lightmap' debug mode is not at the correct location
When going in Baked Lightmap debug mode, the wireframe is display at a wrong location
Note: Certainly a camera-relative issue
To debug you need to look in Look in `EditorCameraDrawing.cpp`
case kEditorDrawBakedAlbedo:
{
RenderNodeQueuePerformRenderFunction renderStaticLightmap(RenderBakedAlbedo, sharedRendererScene->queue);
RenderLightMapResolution<false, false> renderStaticLightmapResolution(sharedRendererScene->queue);
PerformRenderFunction* rfuncs[] = { &renderStaticLightmap, &renderStaticLightmapResolution };
PreMultiCustomRender(cullResults, renderFlags);
MultiCustomRender(cullResults, rfuncs, ARRAY_SIZE(rfuncs));
PostMultiCustomRender(renderFlags);
DoRenderSelected(cullResults.sceneCullParameters, false);
break;
}
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1164241