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
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
This is a duplicate of issue #1164241