Hello.
It used to be in the e-on only version of LumenRT that you could create multiple .lob versions of a plant in Plant Factory and add "VAR#1,VAR#2" etc at the end of the filename. Then LumenRT would recognize all variations as different versions of a single "species" and would automatically cycle through different versions when placing multiple plants (which of course is a great feature!).
This does not work in the current Bentley LumenRT though. Has the naming convention changed or something? It's definitely not a Plant Factory issue because I created a new set of variations with Plant Factory 2016 and tested in both the current and the prior e-on LumenRT version, and they still worked in the e-on version but not in the current Bentley LumenRT Update 2.
Any ideas why not working or is the naming process different now?
Thanks.
I was hoping these issues would be resolved in Update 3 - still no random rotation of custom plants.
The whole point of purchasing Plant Factory was to fill in the deficiencies of LumenRT's delivered content. In my case, none of the delivered trees are indigenous in my country so I need to create my own. I would expect LumenRT to provide the tools to place them in my scene in the same way it does for its own trees.
Max
Hi Max,When loading a custom plant in LumenRT, the random rotation is applied only if the .lob file is located in this folder:"%userprofile%\Documents\Bentley\Bentley LumenRT CONNECT Edition\Plants".This is a bit misleading indeed...We will see if we can change this behavior, but as a workaround you can put your custom plants in this folder.Alex
Thanks Alexandre - this solves the problem.
Much appreciated,
Hi Alex,
It seems this "workaround" is no longer working in CONNECT u11.
LOB file placed in "%userprofile%\Documents\Bentley\Bentley LumenRT CONNECT Edition\Plants" does not get picked up.
If placed in "ProgramData/Bentley/BentleyLumenRTCONNECXTEdition-Update10/LumenRTContent/LumenRT/Plants", it does get picked up, but without any random rotation/ scale applied.
Is there a new "workaround" available?