Is there anyway that Meta-Coding can be used when exporting from MicroStation to LumenRT.
I am trying to put together a visualization that includes traffic signals. I have 3D models of the traffic lanterns but I would like the ability to embed lights within these lanterns to represent red\green\yellow etc which I can then control the state of with the movie editor.I can get this to work by manually placing the lights within the lanterns when I'm in LumenRT, but this is lost if I have to re-export from MicroStation.
I have tried naming cells using the convention below, but I can't use the ampersand (&) symbol in MicroStation cell names for starters.
Alternatively, is there anyway to simulate traffic signals using the traffic data exported from VISSIM?
From the LumenRT documentation:
It is possible to name objects within your generic 3D scene files so that LumenRT allows to either make the object part of a high quality zone, or to completely replace the corresponding object with a content pack item. The latter case can also be enriched with optional custom coloring (if supported by the item), and/or custom transformation matrix information.
For example, naming an object like this:
LumenRTProxy&f=Plants/Pine Scots 3.lob&m=1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 1
will result in your object being replaced with the Pine Scots item's third variation, with a custom transform matrix and a slightly purple color. With this syntax, the exact lob file name and sub-folder must be specified, relative to your ProgramData/e-onsoftware/LumenRT Content/LumenRT folder. A more user-friendly way of naming the object would be:
LumenRT_Pine Scots&m=1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 1&c=0.5,0.3,0.6
Which will indeed use the Pine Scots item, but will randomly choose one variation among the available ones for the selected plant species. Using the "LumenRT_ " shortcut prefix allows to specify the item name directly without its sub-folder and the " .lob " extension. But for plants, a random variation selection is always performed. To select a specific variation, the former syntax has to be used.
Here is another object naming example:
This will replace your object with the Vehicles/Fiat 500.lob item and give it a slightly purple color.
A final example shows how to make an object part of a high quality zone:
This will tag your object accordingly. As soon as one object has the high quality zone tag in your 3D scene file, any non tagged object will be exported in draft quality.
Here is an exhaustive list of the object meta-coding LumenRT codes:
& : Parameter delimiter
LumenRTHQ : High quality zone tag.
LumenRTProxy&f= : LumenRT proxy object which loads a pre-made LumenRT content object.
example: LumenRTProxy&f=Vehicles/Fiat 500.lob
LumenRT_: LumenRT proxy object which loads a pre-made LumenRT content object.
example: LumenRT_Fiat 500
m(optional) : Proxy object's 4x4 transformation matrix. The first 4x3 values define the X,Y and Z local axis, and should end with zero. The last 4 values define the 3D position and should end with one.
example: LumenRT_Fiat 500&m=1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 1
c(optional) : Proxy object's overall color, if the corresponding item does support it. Currently, only vehicles do support this setting.
example: LumenRT_Fiat 500&c=1.0,0.5,0.2
For anyone following this. I have since discovered that MicroStation light sources are supported when exporting to LumenRT. So no need for any fancy Meta-coding to make that happen.
I am using a 3D cell of a traffic lantern with 3 embeded light sources red\amber\green and it seems to be coming across to LumenRT no problem.
Next I might have a crack at altering the VISSIM to LumenRT python script to see if I can control the traffic signal lights with the information from VISSIM. I'll update this thread once I have given that a go.
Is anyone able to shed some light into the format of the Animation XML file that is produced using the VISSIM2LumenRT.py python script?
I would like to modify that python script to help with the automation of traffic signals. I currently have traffic lanterns in LumenRT that contain light sources for red\green\amber.
I am also importing traffic data from VISSIM to animate the vehicles in the live cube.
I would like to extract the signal timing's from the VISSIM animation file and write some output in the animation xml file that will cause the various light sources attached to each traffic lantern to switch on\off.
I can handle the python side of things. But I just need to know what LumenRT expects to see in the Animation XML file to make this happen.
Any help would be greatly appreciated.
I am also keenly interested in this... commenting to follow
Any progress on this? would also like to soundclips to vehicle objects.
I am interested in this as well.....