Some DCC may close a 3d scene without closing the application, in that case they must be able to close the DirectLink source as well.
With the simplified DirectLink API (FDatasmithDirectLink) this was only achievable by creating a new scene that would override the existing one, which is not desirable in this case.
Our C# exporters can only use the simplified API at the moment and this seems like a common enough use-case to be added to FDatasmithDirectLink.
#jira UE-140665
#rb Johan.Duparc
#preflight 6290fa2db83292836e093ea2
#preflight 62953a005370042eb043f84a
[CL 20433116 by benoit deschenes in ue5-main branch]
rules of thumb:
- Actor transforms are in doubles
- mesh internal data are in floats, except UVs that are in doubles
- compiled 3dsmax, archicad, navisworks, revit, rhino, sketchup, solidworks
#jira UETOOL-5070
#preflight 623f2ee47d49f37dfd3d599b
#rb Benoit.Deschenes
[CL 19533189 by Johan Duparc in ue5-main branch]
This represents UE4/Main @18073326, Release-5.0 @18081140 and Dev-PerfTest @18045971
[CL 18081471 by aurel cordonnier in ue5-release-engine-test branch]
Revit: Fix export time field in exported datasmith scene
#jira UE-88083
#rb none
#ROBOMERGE-SOURCE: CL 11604300 in //UE4/Release-4.25/... via CL 11604316
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11604350 by johan duparc in Main branch]