Revit datasmith exporter wishlist

[anonymous_user_a17ab3bf]

Hi，I am using the datasimth plug-in of UE4 to export the model with revit, but I found several problems:

1. When I package .exe, the result information shows success, but when I open the.exe file, it shows a black screen and an error (as shown in the attachment picture）.However, the same scenario imported into ue4 4.20 does not have this problem.
2. Can we realize the nesting relationship of revit nesting family in ue4 ？
3. Can subclasses of revit be included in ue4 ？
   I hope to get your reply as soon as possible, thank you!

[Etienneboy0 (Etienne 0_o)]

there is a new DataSmith update. is there a release note of whats fixed?

[Etienneboy0 (Etienne 0_o)]

@Etienneboy0

there is a new DataSmith update. is there a release note of whats fixed?

found it: https://forums.unrealengine.com/unreal-engine/unreal-studio/1548249-unreal-studio-beta-4-21-release/page3

linked models are fixed

are you people having trouble with large projects with many curtain walls?

i’ve got a project of 17000m2 with lots of curtain walls and it’s pretty intensive for a maxed out gaming pc to handel the scene.

[Anaximedes]

@LegendreVR

Regarding 6, some kind of voxelization, or mesh splitting internally would be very useful indeed, some meshes we have like very long beams, walls and the likes, come out with a stretched UV and wasted UVmap space… Surely this kind of sample isn’t really good for lightmass

https://i.imgur.com/AABBbaf.png

Absolutely agree, LegendreVR. I work mainly on laboratory interiors, great open rooms. Ceilings or floors have great surfaces (on both sides). It seems lightmapping 4K sizes is not efficient, and wasted lightmap space may be too high.

But no only this. I was thinking a little bit further as could be considering rooms and their identity data as floor, walls and ceilings finishings for automesh generating option for avoiding big default walls, floors and ceilings. This way is probably a good option to voxelize this kind of families in certain cases. As you know, in Revit, when creating rooms you can not only tag them but include finish info manually or may be dynamo scripting for automating tasks. Scripting later (Blutility) then in Unreal Editor with datatables for mapping room finishes to predefined materials.

What do you think?

[anonymous_user_21e38222]

Absolutely agree, LegendreVR. I work mainly on laboratory interiors, great open rooms. Ceilings or floors have great surfaces (on both sides). It seems lightmapping 4K sizes is not efficient, and wasted lightmap space may be too high.

But no only this. I was thinking a little bit further as could be considering rooms and their identity data as floor, walls and ceilings finishings for automesh generating option for avoiding big default walls, floors and ceilings. This way is probably a good option to voxelize this kind of families in certain cases. As you know, in Revit, when creating rooms you can not only tag them but include finish info manually or may be dynamo scripting for automating tasks. Scripting later (Blutility) then in Unreal Editor with datatables for mapping room finishes to predefined materials.

What do you think?

Can you do that with Dynamo ? Splitting/voxelizing meshes and have each part with the same metadata ? Would be pretty useful for lightmass indeed while waiting for a move from the Revit plugin devteam (or lightmass 2.0).

[Anaximedes]

@LegendreVR

Can you do that with Dynamo ? Splitting/voxelizing meshes and have each part with the same metadata ? Would be pretty useful for lightmass indeed while waiting for a move from the Revit plugin devteam (or lightmass 2.0).

As far as I know, with standarg nodes, no. May be Python scripting inside Dynamo, creating new nodes for getting rooms, I mean, remeshing for interior meshes for floor, walls and ceiling of every room, keeping out of this “HQ” and well lightmapped meshes the outside sides.

I think an aditional actor of every room would be wished for having room data inside US.

Will keep in contact.