Hi everyone! I need help diagnosing critical issues in Twinmotion that make work impossible; support hasn’t responded yet. I’ve collected maximum data, logs, and clear reproduction steps, plus compared behavior across two versions. If anyone has encountered similar problems or knows how to read these logs, I’d be very grateful for any tips.
What’s happening (briefly)
In Twinmotion 2025.2, SketchUp models from the built‑in library don’t load (the button is inactive), and the app consistently crashes when working with lighting (specifically during the scene refresh stage).
In Twinmotion 2026.2 Preview, the library works, but FBX import is broken: a warning appears about Nanite/Standard shadows, and all imported models get assigned a single texture that cannot be changed.
I cannot work productively in either version.
Issue 1: SketchUp models not loading from the library (Twinmotion 2025.2)
Models appear in the library, but the load button is inactive (grayed out). They cannot be downloaded.
Important observation: in Twinmotion 2026.2 Preview, the same library models load correctly. This strongly suggests a bug in the 2025.2 build rather than a network or permissions issue.
The problem reproduces in all projects and on different internet connections.
Issue 2: Crashes when working with lighting (Twinmotion 2025.2)
When adding any light source (Sun, Spot, Point), everything seems to be added, but the crash occurs specifically during the scene refresh (Refresh Scene) or when trying to save the project.
The error is stable: it repeats across different scenes and with different light types.
All changes are lost — this is critical for the workflow.
Issue 3: FBX import and Nanite/Standard shadows conflict (Twinmotion 2026.2 Preview)
When importing FBX, a warning appears:
WARNING: For optimization reasons, Standard shadows is disabled when Nanite is enabled on 1 or more objects. To use Standard shadows, disable Nanite on all objects.
All imported models are automatically assigned the same texture, and it cannot be changed.
This also makes working in 2026.2 Preview impossible.
How to reproduce (step by step)
- Open Twinmotion 2025.2.
- Go to the library, select any SketchUp model — the load attempt fails (button is inactive).
- Create a new scene, add a light source (e.g., Sun).
- Try to refresh the scene or save the project — the app crashes.
System specifications
- OS: Windows 11 Pro, version 25H2.
- Processor: 13th Gen Intel Core i7‑13700 (2.10 GHz).
- Graphics card: NVIDIA GeForce RTX 4060 Ti (8 GB VRAM).
- RAM: 64 GB (5600 MT/s).
- Graphics driver version: 32.0.16.1088.
What has already been checked
- Verified Twinmotion file integrity via Epic Games Launcher — no errors found.
- The TwinmotionContentLibrary folder exists at the default path.
- The issue appears in both new and existing projects.
- Tested with different internet connections — behavior is the same.
Data attached for analysis
For diagnostics, I’ve collected logs from 11.10.2026, when the main crashes were recorded:
- Twinmotion_3.log — session immediately before the first crash.
- Twinmotion_4.log — repeated session with similar errors.
- Two NVIDIA driver logs (D3D12…).
Logs are in an archive at this link: https://drive.google.com/file/d/1Myhfo627-RIqxotsx_b6_NsWENj3RbJO/view?usp=sharing (I cannot attach files on the forum due to user restrictions).
All files are packed in the archive D3D12.0.2025.12.15-23.08.55.zip.
What I’d like from the community:
I’m not familiar with programming or the intricacies of log analysis, so I’d appreciate explanations in simple terms.
Please help me understand:
- What could be the possible causes of this behavior in Twinmotion — both in version 2025.2 (lighting crashes and broken library) and in 2026.2 Preview (FBX, Nanite, and texture issues)?
- Are there any real, working solutions or workarounds that can be applied right now to restore stable operation?