Hi Tom and fellow Revit LT users,
This will be my last post (I hope you understand that I am pretty well fed-up with Autodesk help by now), so I hope that you will find this useful.
So far, I have found that the best way to export Revit LT to use in Lumion and D5 Render is to export as an ifc file and convert it into an fbx file.
ifc files seem to be the best so far as it allows smooth curves (set ‘Level of Detail’ to ‘High’. Direct export to fbx does not allow a choice for ‘Level of Detail’) and the material names are also transferred. This is much better than a .dwg export (‘Polymesh’ or ‘ACIS Solids’) as you will have a never-ending issue with the hierarchy of material / family names shuffling around within Lumion or D5 Render.
Note: The above solution still has an issue that materials on either side of a composite wall are not recognised. I am therefore going to model internal and external skins separately for now until something improves. I do realise the hassle of placing doors and windows but have a workaround.
So….what is the best way to convert an .ifc into an .fbx? Well, that’s more tricky than I expected.
I was converting .ifc files into .fbx files using Simlab Composer 9, but discovered that numbers were added to the beginning of material names. This caused the ‘House Swap Test’ to fail and therefore there would be continuous workflow problems within both Lumion and D5 Render.
I assumed all converters gave you the same result. I was so surprised to discover that each converter will give you a different result.
- I came to the conclusion that using a ‘middle-man’ software program like Blender, UE4 or even 3DRhino would be disruptive to an efficient workflow. A simple converter would be more efficient.
So I tested the following…..
It isn’t the best because it is FREE. I like it the best because it is quick, simple and best of all, material names come out clean (no numbers or any other info added to the material names meaning they would be consistent from project to project). Just a warning…composite walls are still a problem.
I also tested the following but found issues with them.
- Cadexchanger – Too fancy and Revit material names were not recognised.
- 3D-Convert.com – Could not recognise Revit .ifc files so I couldn’t even test it.
- Automapki – Too fancy. Numbers and additional info were added to material names.
- Datakit – Cross Manager. ???? Still hopeful. I have asked ‘Central Innovation’ for a trial version.
- Aspose – IFC to OBJ. Most of the model was missing. The house looked like a construction site.
- NCH Software – IFC to OBJ. Model was mirrored and there were no materials.
Other conversions could still be tested, eg:
For LUMION, .ifc to .skp or .dae might work better???
For D5 RENDER, .ifc to Rhino .3dm might work better???.
The combo seems endless and overwhelming, which is why I will ask ‘Building Smart’ (developer of .ifc) which option they would recommend. If you are interested in the answer, check out the ‘Building Smart’ forum https://forums.buildingsmart.org/ in about a week or so.
Some D5 Render users have already asked D5 Render to consider introducing a model ‘hierarchy’ system similar to Twinmotion (we already know Twinmotion can read .fbx well because of this. Remember… a direct .fbx export from Revit will not ask for the ‘Level of Detail’ so close ups of round objects will look terrible). I am sure D5 developers will listen to their customers.
I would have liked to have helped Revit LT users further, but the kind of feedback I am getting is tiring.
I wish all Revit LT users the best in the quest to use Revit LT with 3rd party rendering software programs. I hope you find a successful solution.
With best wishes and kindest regards,
Leah