You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is meant to track the progress of converting SDF to USD, which is currently a work in progress.
@ahcorde if there's anything I'm missing in the feature list below (or if anything seems incorrect/out of date), feel free to modify the feature list directly.
Supported
World's gravity information
Lights
//light/direction is currently ignored (USD lights will point down by default)
//light/diffuse and //light/specular are currently ignored, but a potential workaround for these elements is to apply a material to the USD light
Mesh geometry support is limited to points, lines, and triangles submesh primitive types
collisions
Limited support. Currently, a collision is created for every visual, with the collision geometry matching the link’s visual geometry. SDF supports setting collisions that can differ from link geometries (perhaps users want a simpler collision shape, for example)
This issue is meant to track the progress of converting SDF to USD, which is currently a work in progress.
@ahcorde if there's anything I'm missing in the feature list below (or if anything seems incorrect/out of date), feel free to modify the feature list directly.
Supported
//light/direction
is currently ignored (USD lights will point down by default)//light/diffuse
and//light/specular
are currently ignored, but a potential workaround for these elements is to apply a material to the USD lightIn Progress
//lidar/scan/horizontal/samples
and//lidar/scan/vertical/samples
currently aren’t being parsed to the USD lidar sensor$HOME/.ignition/fuel
)Not Supported
sdf2usd
parser executable only supports SDF files with exactly one world)Additional context
Here are past PRs related to this work that have been merged:
The text was updated successfully, but these errors were encountered: