Navigation
API > API/Plugins > API/Plugins/InterchangeImport > API/Plugins/InterchangeImport/Usd > API/Plugins/InterchangeImport/Usd/UInterchangeUsdTranslatorSetting-
Syntax
UPROPERTY (EditAnywhere, Category="USD Translator",
Meta=(Bitmask, BitmaskEnum="/Script/UnrealUSDWrapper.EUsdPurpose"))
int32 GeometryPurpose
Remarks
TODO: Most (if not all) of these settings should probably be specific to the pipeline, and not the translator, and will be moved there whenever we do make a USD pipeline.
For example: Instead of filtering prims based on purpose on translation, we should emit all of the translated nodes and filter only later on the pipeline, as translating the scene should be fast either way. That way users can even customize/disable that behavior if they want to, in order to use their own pipelines.
It's not clear what to do about StageOptions or RenderContext though: Maybe these should be here, as they actively affect how we translate the scene? (e.g. the generated Interchange Material node for a Material prim will be very different whether we use "universal", "unreal" or "mtlx" render contexts...) Only import geometry prims with these specific purposes from the USD file