I've just spent a couple of hours with LumenRT Update 15 and have a few comments.
First, congratulations to the development team - there are some good improvements. I also tried everything to make it crash - without success.
Hello Max,
Thank you so much for the feedback and detailed report on update 15.
I really appreciate your time having mentioning all this.
Will try to cover all the question one by one and provide you the right feedback on the same.
Thanks.
Rg,
Ankur Ashesh
Thanks for this, Ankur - feedback on these issues would be really useful.
Max
Ok - easy way to make LRT crash...
A raster image (JPG) is mapped to a mesh in Microstation. Export to LumenRT, all fine.
Now do some photoshopping to the JPG and overwrite the original JPG. Re-export to LRT and it will corrupt the LRT file.
There are some occasions when it doesn't corrupt the LRT, but the original version of the map remains in the file (not the updated one).
Please provide a work-around or update to make this work.
Thanks,
Thank you for reporting.
Can you just confirm, which version of Microstation you are using?
We will reproduce the issue in the same version.
Thank you.
Regards,
Pinky Shee
Thank you - CE 10.15.00.74
It feels as if LumenRT latches on to some unique identifier (not just file name) for each image map. If I change something on the image, but keep the same file name, LumenRT will hold on to the original image and is not interested in the updated version.
Will be able to share a small sample file for testing ?
I will try to reproduce the issue at my end.
I've not been able to reproduce the crash with a smaller version of my files, but can demonstrate the problem in a different way.
Attached is a small version, with just one of the many meshes included. I've created a draped jpg called "draped aerial image", and for reference have written "OPTION A" on it.
I hope this helps. As I said previously, it feels as if LumenRT is determined to keep the original image map rather than accept any updates from Microstation. Possibly related; I did a screenshot of a Microstation message earlier which made reference to a missing pattern (same as my draped aerial images). (lost the screenshot, but it was something like "Unable to find pattern: draped aerial image.jpg [X10F273500DE78]
It adds a complex identifier behind the filename, which makes me think the JPG is not only identified by filename, but by unique identifier too. This is confusing to the Microstation>LRT export process.
SP_test_2.zip
Hello,
I posted a question in the visualization forum about LumenRT and roadway section. When you have time can you help me out.
Thanks
MicroStation V8i (SELECT series 3) - Version 08.11.09.578
Microstation Connect 10.14.00.109