The steps above are reduced to their simplest expression. I appears that several customers complained about lightmap baking resulting in glowing objects. This typically happens on interior door frames and crown moldings around walls.
After digging some more, the problem is that in some cases, depending on how entities are modeled in max, Datasmith imports data in a way that tangents are scaled weirdly.
After lightmap baking, those objects seems to capture illumination from the sky - which is lot brighter than interior scenes, resulting in a "glowing" effect.
In SM Editor, you can `fix` it by recomputing the tangents . Note that with FBX the problem doesn`t seem to occur
See this document.
more details: [Link Removed]
-----------------------------------------------
Simple steps:
Export the attached scene
Look at the tangents in SM editor
SEE: they are in a "flat" incompatible form
----------------------------------------------------
[Image Removed] file: [Link Removed]
How does TextureRenderTarget2D get TArray<uint8> type data?
How to delete some elements correctly when deleting an array loop?
Why does the REMOVE method of map container remove elements have memory leaks?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
How do I set a material as a post-processing material?
What is the difference between Camera and CineCamera?
UMG RichText not appear image when packaged
How to assign a value to a member of UMG's UMaterialInterface pointer type in C++?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-70461 in the post.
0 |
Component | UE - Editor - Content Pipeline - Datasmith - Exporters |
---|---|
Affects Versions | 4.22 |
Target Fix | 4.24 |
Created | Feb 22, 2019 |
---|---|
Resolved | Jul 29, 2019 |
Updated | Oct 28, 2019 |