You've already forked UnrealEngineUWP
mirror of
https://github.com/izzy2lost/UnrealEngineUWP.git
synced 2026-03-26 18:15:20 -07:00
c99ece33ff
- Actor name for a Revit element is now composed from the 'path' through whole hierarchy of Revit elements(including linked documents). This makes every element that occurs multiple times in the scene(e.g. in Linked docs) to have different actor name - This makes it unique(path to element occurrence is unique). - This 'path' is stable because of not using any 'unstable' elements(like temporary geometry symbols created by Revit during export - only elements UniqueIds) - additional: debug output for scene parsing(compile-time enabled using DatasmithRevitDebugOutput symbol) #rb benoit.deschenes #jira UE-169815 #preflight 6380f92b3377450900872239 #lockdown jeanmichel.dignard [CL 23300209 by kerim borchaev in ue5-main branch]
// Copyright Epic Games, Inc. All Rights Reserved. Since the Datasmith Revit Exporter is programmed in C#, the standard build process just runs a post-build step to build in batch the release configuration of Visual Studio C# project file DatasmithRevit<year>\DatasmithRevit<year>.csproj. To develop the C# code, it is preferable to directly open DatasmithRevit<year>\DatasmithRevit<year>.csproj in Visual Studio. The Visual Studio C# project automatically includes all the Datasmith Revit Exporter C# files from project directory Private and all the Datasmith Facade C# files from directory Enterprise\Binaries\Win64\DatasmithFacadeCSharp\Public. Outside of Epic Games, environment variable Revit_<year>_API must be set to the Revit API third party directory on the developer's workstation. Inside of Epic Games, when opening the Visual Studio C# project directly, environment variable Revit_<year>_API must be set to the developer's Perforce workspace directory Enterprise\Source\ThirdParty\NotForLicensees\Revit\Revit_<year>_API. At this time, <year> can be in the range [2018..2022].