<aside> 👉🏼 Contents Files with high object count Revit 3dsMax Rhino
</aside>
Nanite in Unreal Engine 5 currently has a limitation of 50k unique objects per scene. Palatial can help overcome this, but only if the file is broken up into individual exports that don’t exceed this limit. If you think your file may exceed this limit, see below for strategies on how to break up exports for each supported DCC software.
<aside> ⚠️ Exporting a master Revit file with other linked files using Datasmith will import each linked file as an actor with nested subcomponents. Palatial does not currently support optimization for this type of actor.
This is an issue we’re aware of and are currently working to resolve (June 7, 2024).
</aside>
Revit scenes are exported based on what is visible in the 3D view and what linked files are loaded. For extremely large projects, we recommend exporting each linked file separately:
Open each Revit file and use the manage links window to unload all linked files
Once files have been unloaded, click OK to apply changes, and wait for the viewport to update.
Next, export the scene as a Datasmith file and repeat this process for each linked Revit file.
Datasmith exports on 3dsMax can occasionally fail due to problematic geometry, excessive file sizes or file access issues. When this occurs, 3dsMax may freeze or crash. In cases like this, we recommend exporting each layer separately. doing so will reduce the likelihood of memory related crashes and also help isolate problematic geometry.
There are 2 ways to do this:
The 3dsmax Datasmith Toolbar
Use the isolate selection function or the layer explorer to show only what what you want to export and use “Export” from the Datasmith Toolbar
Select what you want to export and use the export selected button on the Datasmith Toolbar
Do this for for every layer or group in the file.
Note that older versions of the datasmith exporter (pre UE5.1) will not have this see 3dsMax file prep for more details.