My Microstation model has been exporting fine until today. The first screenshot shows the model correctly located - I've placed trees and set up animation paths.
I've made a few changes to the buildings and terrain, but not added anything beyond the extents of the terrain. As you can see in the second screenshot, the model has shifted relative to my trees and animation paths. In OBJECT COORDINATES it shows -609.6m, 1.219km, 755.03m, which presumably means it's shifted by those x,y distances because the original location is 0m,0m,755.03m.
I'm able to manually move the model back to where my trees are by unlocking OBJECT COORDINATES, but can't seem to dial in the 0m, 0m needed to accurately and easily do so. Those numbers are greyed out.
Why did this happen? It was a common problem with earlier versions of LumenRT (remember when we were advised to place four blocks at the outer extremities?). What's the best way to diagnose this? I've tried exporting just some minimal geometry but everything is shifted by that 609, 1.219 distance.
This is purely speculation but you could give it a try and see if it helps.
A recent forum post was talking about the file properties of a DGN file. In Window Explorer, I took a look at the Properties of my dgn and this is what I found.
There are LumenRT offset coordinates in the Custom tab. It looks like the offset is stored this way when the file is first exported to LumenRT.
You might be able to adjust these values to get your exports back to the correct location.
A remarkable discovery, Ron!
The x,y offsets in both files are indeed dissimilar and I'm fairly sure that if I could modify them back to their original offsets my problem would be solved. Unfortunately, the Modify button is greyed out.
A workaround would be to use a copy of my original file (with the correct x,y offsets) - delete all contents, reference and copy all contents from my new file into it and try the export to LRT from there.
Question is; why did Microstation change these "LumenRTOffset" attributes? Or does LumenRT write this custom property to the DGN? What circumstances trigger this action? Any insights from Bentley would be appreciated.
You have to modify a value first to enable the Modify button.
Thanks Ron - of course, I had only placed the cursor in the box and not yet changed the numbers.
As it turns out, after changing those numbers to the "good" offsets, the exported geometry remains unmoved from the wrong location. I've resorted to my work-around of replacing everything in a "good" file placeholder with my updated geometry from the "bad" file. All okay now, but I'd really like to know why it happened.
Question to Bentley; what situations trigger a Microstation > LumenRT export to shift co-ordinates?
Wow thanks for finding this! I had the same problem but could fix this using a backup file of my visualisation container file. I would never have guess that the problem originated from my container file.