When converting files from previous versions of Twinmotion to Twinmotion 2025.1, re-importing any existing imported geometry will cause the geometry to be re-imported with two-sided geometry disabled. There is no way to adjust this, causing some geometry to appear broken on re-import.
The workaround is to delete the existing import and start a new import, or manually adjust materials to be two-sided. This can present workflow problems for backwards compatible projects.
Result: The imported model will be re-imported with two-sided geometry disabled. There is no way to change this behavior.
Why does the REMOVE method of map container remove elements have memory leaks?
Does media player's OpenFile method support dynamically opening a video file?
How does TextureRenderTarget2D get TArray<uint8> type data?
How to delete some elements correctly when deleting an array loop?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
What is the difference between Camera and CineCamera?
What does the number (2152,1-34) in glsl error mean?
How would I go about lerping the rotation instead of it snapping when turning (pls dont sue me epic)
There's no existing public thread on this issue, so head over to Questions & Answers just mention TM-18474 in the post.
0 |
Component | TM - Interoperability |
---|---|
Affects Versions | twinmotion 2025.1 pr2 |
Target Fix | twinmotion 2025.1 final |
Created | Jan 28, 2025 |
---|---|
Resolved | Feb 6, 2025 |
Updated | Feb 6, 2025 |