# The Datasmith SolidWorks exporter does not transport texture mapping correctly 

**URL:** <https://forums.unrealengine.com/t/the-datasmith-solidworks-exporter-does-not-transport-texture-mapping-correctly/2746710>\
**Category:** Feedback & Requests\
**Tags:** Datasmith, twinmotion\
**Created:** [August 26, 2026, 5:42pm UTC](https://forums.unrealengine.com/t/the-datasmith-solidworks-exporter-does-not-transport-texture-mapping-correctly/2746710 "2026-08-26T17:42:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![quietcookieman](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@quietcookieman](https://forums.unrealengine.com/u/quietcookieman)\
**Post date:** [August 26, 2026, 5:42pm UTC](https://forums.unrealengine.com/t/the-datasmith-solidworks-exporter-does-not-transport-texture-mapping-correctly/2746710/1 "2026-08-26T17:42:01Z")

</div>

Texture mapping is baked into mesh UV0 by the exporter (`FGeometryChunk..ctor` → `FConstructionGeometry.ComputePlanarUV` / `ComputeCylindricalUV` / `ComputeSphericalUV`), not carried as material parameters. Each of the five SolidWorks mapping types is wrong in a different way, and one of them destroys triangles. Separately, and independent of mapping: **appearance colours are shipped to Datasmith as if they were already linear** (below, E1) — mid-grey arrives 2.33× too bright and saturation drops ~40%. Reference this github repo for in-depth analysis and a patch. [GitHub - bdm310/solidworks-datasmith-fixer · GitHub](https://github.com/bdm310/solidworks-datasmith-fixer)

I’ve submitted a bug report via the Twinmotion contact form, don’t know if that’ll actually go anywhere. Figured I’d also post here so it’s visible and searchable.
