I am landscape architect and urgently need proper looking 3D trees and other vegetation in my landscape models. Now that Bentely doesn't support RPC cells in the new VUE rendering engine I wonder what is the new procedure to get natural looking people, trees etc. in Microstation models and how to render them efficently? There are lots of third party 3D-tree cells available but they are so large and memory consuming that using them wastes tons of time, especially if one need them more than one. And how about people? Most of 3D-models of humans look like a a 3D-model of a human.
View online
If you encounter issues clicking "View online", check here.
You received this notification because you are subscribed to the forum. To stop receiving updates from only this thread, go here. To unsubscribe from a forum, please see this note.
Flag this post as spam/abuse.
Personally I would perefer to stay with one platform (Microstation) because it saves lots of time to edit & render the model using the same porgram. For me it has always been the major factor why I use Microtation at all.
I have used RPC cells a lot because they work quite well in real time peresentations with accelerated view modes (illustration & smooth). Problem with Lument RT plants is that the they don't look like natural species we have here in Scandinavia.
The other reason I don't like Lumen RT is that last ime I tried to use it Benley kindly sent me a 1000 € bill because our Select subscription seemingly dosen't cover Lumen RT and I am not excactly sure if the program is worth of paying extra thousands of euros on top of Microsatation. So, it there is some decent looking vegetetion & people which would work both in real time presentations and VUE renderings and don't take ages to render, I would love to try them.
I think the reason that Mstn users use LumenRT is that LumenRT is optimised for real time rendering and animation using the GPU etc. The other reason is that Navigator was extremely slow compared to Navisworks etc.
Moving / translating to a 'game-engine' viewer even with the loss of precision is a well trodden way of dealing with scalability barriers in the CAD app. R*vit users are used to using Navis to overlay the other disciplines models externally, side-by-side in Navis, next to R*vit. Something that Mstn doesn't suffer from as much but is still impacted. Even with the latest Vue improvements, I doubt you will be able to match the same performance. Regarding the new itwins attachment functionality in CE U16, the ref attached imodels are apparently a streamed HLOD format... which should help, but itwins are generally read only.
Ideally, the Mstn <> LumenRT should function like R*vit <> Enscape or ArchiCAD <> Twinmotion.... as side-by-side apps that are incrementally and bi-directionally synchronised, not requiring re-exports. Any changes or additions in LumenRT like trees, entourage, animations etc should be synched back to Mstn... if not there will be a lot of time wasted after the 'rendered' design has been approved and needs to be implemented.
A lot of road layouts etc designs start with a very incomplete, with basic aka 'high level' design by the traffic engineer and end up with the visualiser adding and amending the design in the rendering app, last minute... causing a lot of 'under-engineered artifacts' aka placeholder problems in the model and manual / unrealiable rework down the line.
A bit disappointing that Bentley still can't provide a seamless path between the two apps... 5+ years on. Maybe the Omniverse synchronisation API will finally provide the realtime synchronisation needed?
I share your feelings. Export / import cycles between Microstation and LumenRT are time consuming and clumsy, making LumenRT very unattractive option for me.