Johannes Schmitz

I still need to implement the "trick" mentioned above but was working on double and colored road marks and splitting the lanes for highway exits and some other stuff. So...

The trick seems to be working, I am doing something like this: ``` # Teleport to initial position init.add_init_action(car_name, xosc.TeleportAction( xosc.WorldPosition( x=obj['position'][0], y=obj['position'][1], z=obj['position'][2], h=obj['hdg']))) # Get pitch and roll...

Here is some additional information and suggestions from the Microsoft Team regarding this issue: https://github.com/microsoft/debugpy/issues/938

@emackey Since there is no recent activity I am going to ask this: Is there any chance of this ever being merged so that we can easily look at .glb...

@emackey how about you just combine the two steps you suggest (1. Import, 2. Preview) in a single convenience command. Also when doing so you can just open the resulting....

Can't you write all or some of the files to tmp maybe?

Well, I am sorry for the inconvenience but with the current implementation you will have to configure a matching road cross section yourself manually. The smartness you want is theoretically...

@GithubMingEnter Just for your understanding: If you haven't so far, please study about the OpenDRIVE reference line and lane linkage in the official standard document available on the ASAM website...

Hm, sounds a bit strange, you could save it and upload the .blend file (in a .zip file) here if you want me to have a closer look.

It is possible to create a map and export as .xodr + .fbx, simply choose the .fbx option in the export dialog. What is currently not possible is to import...