Datasmith: SketchUp to Unreal issues

General Feedback & Requests
, ,
1

Testing a SketchUp to Unreal workflow using Datasmith (instead of using fbx). I run into these three issues. See attached SketchUp file. In it a (very very simple) demo scene. I export these 3 containers as separate Datasmith files;

  1. remain (some context that will be put on the persistent level together with the lights, ppv etc),
  2. demolish (some old stuff that will be demolished, put onto a separate sub-level
  3. new (the new design, also on a separate sub-level).

The nice thing about this setup is that - for Archviz - you can easily switch between the current situation and the new design(s).

The issues I run into are:

Issue 1: Re-importing the Datasmith file after making changes, at some point changes wont carry over anymore IF the datasmith file is on a sub-level(!!). If there are no sub-levels, it will change the hierarchy just as in SketchUp. To replicate:

  • In Sketchup, open the [modernHouse] component in the [New] component and break up the windowz group into 2: one for each story so Windows will turn into WindowsA and WindowsB
  • save the Datasmith file
  • re-import the datasmith file and the windows on one floor dissapear

Doing the same if the Datasmith file is on the persistent level everything works as intended.

Issue 2: In SketchUp you can mix materials with colors. For instance the windows & frames both share the same base texture (in this case empty.png). Using fbx export, this generates 2 new textures and the result in UE is just as in SketchUp. Using Datasmith, these materials are mixed up and end up totally different (the parent material)

Issue 3: lightmap density doesn’t change for some objects when running an EditorUtilityWidget + compute lightmap resolution-action;

  • Create an Editor Utility Widget with a button and an action [compute lightmap resolution] set it to any ratio and tick [apply changes].
  • After running the widget, the lightmap density will change for all objects but not for the 90_street. That one will have LightmapResolution of value [4] in the StaticMeshEditor. This problem is not unique using Datasmith. The same can happen with fbx imported objects

Maybe the second issue is as intended. I hope the first and last could be fixed at some point.
Cheers,
Max

test.skp (564.4 KB)