I am exporting two site terrain surfaces with my model into LumenRT. A larger sized one for the greater site. and a Smaller one with more terrain detail as well as a more detailed image. The smaller one "sits" in the larger one.
When I export my buildings and terrain models, the larger one exports it's draped material attachment just fine. However the smaller one does not. It seems to change the material mapping to a tiled mapping instead of mapping across the entire surface. Both Materials were made in the same way in the material editor.
When I export the smaller terrain model alone into LumenRT, it exports just fine and has the expected mapping.
Am I exceeding some kind of buffer? I can't figure out why the mapping gets corrupted. Suggestions?
OpenBuildings Microstation Connect Edition Update 6 - Version 10.06.03.04
Bentley LumenRT CONNECT Edition - Update 13
NOTE: I am using a brain-dead machine that my employer has assigned to me. It doesn't have a good graphics card. It has the on-board Intel GPU which uses extended memory. I get the dreaded "The dedicated Video Memory (VRAM) on your video card is not sufficient to render LumenRT LiveCubes correctly (128MB detected)."
Would it be possible to share the files for testing?
https://bentley.sharefile.com/r-r397a9fbf9514f4fb
As a test try the following:
1. export the model with just the detailed terrain section
2. If successful save the lumen file
3. in the dgn file turn the larger terrain on and reexport the model. This should take advantage of the sync feature and just update the lumen file to include the larger terrain.
I've continued to try and find a solution. I've tried a number of things, but most did not solve my problem or offer any hint to the solution.
I said, "Most."
One thing I tried is to make the file which has the small, problem terrain mesh the file I render from. To do this, I referenced the LANL Master file with a nest level of 1. This made it easy to remap my many reference files and make the file containing the small mesh my active file. When I render this new file in Luxology, the draped material for my small terrain mesh now renders, but the draped mesh for my larger terrain mesh not has either lost its material or renders in such a way it is no longer recognizable.
So, in all the time I've used Microstation for renderings, most times I've used the Raster Manager referenced image method of draping a material over a terrain mesh. I don't recall creating a material definition using the Elevation Drape setting in the Material Manager. I thought you could have multiple materials definitions which were draped materials, but this new experiment makes me believe that perhaps not. At least it is perhaps a clue to my problem.
I thought folks were using multiple draped 1600 x 1600 pixel images over corresponding meshes to achieve large high-resolution seemless terrain models which exported into Luxology or LumenRT. Yes?