SKP import - Mirrored groups will display with the default material in Keep Hierarchy imports

TM - Interoperability - Apr 10, 2025

Reported in SF [Link Removed] SketchUp models containing grouped elements that are mirrored will incorrectly display these elements with the default material when imported using the Keep Hierarchy ...

Animation - Imported fbx animation mesh appears distorted

TM - Tools - Apr 9, 2025

Reported by user in SF [Link Removed] An animated FBX file from Mixamo appears with a distorted mesh inside Twinmotion. Distortion appears regardless of settings used for import. ...

Video material previews incorrectly on Mac

TM - Rendering - Apr 3, 2025

Received multiple reports of users on Mac computers experiencing issues previewing video materials in Twinmotion 2025.1. When adding video materials to the scene, the scale seems to be incorrect an ...

DAE Import - Missing geometry in imported .dae model from Cabinet Vision

TM - Interoperability - Mar 27, 2025

Reported in SF [Link Removed] Client created a ,dae file in Cabinet Vision. When imported into TM, geometry will be missing, such as the walls and parts of the cabinets. Tested and occurs in TM 20 ...

Incorrect UVs on imported FBX when collapsed

TM - Interoperability - Mar 18, 2025

UVs appear to be broken when client file is imported using Collapse by Material or Collapse All.  ...

Some objects are imported with incorrect position in Keep Hierarchy

TM - Interoperability - Mar 17, 2025

I could only replicate with the user's sketchup file. Exporting this file as fbx, and importing the fbx in KH doesn't have the issue.[Image Removed] ...

Animated characters may appear in A pose after loading a file with Path Tracer enabled

TM - Rendering - Mar 12, 2025

When saving a file with Path Tracer enabled at the time of save, animated characters will appear in an A pose state. This will persist until Path Tracer is disabled. Occurs in Twinmotion 2024.1.2 a ...

Shading error after flipping normals on mesh

TM - Interoperability - Mar 11, 2025

As far as I can guess is that in the initial state of the object, the vertex normals are as they come from the DCC, but after the modeling operation they get recalculated somehow that doesn't match ...