URDF importer: visuals has corrupted data in primvar st: buffer size 24 doesn't match expected size in faceVarying primvars

Hi all,

When I use URDF importer in Isaac Sim to convert my robot urdf to usd format, it occurs problem as:

/World/Robot/leg_link/visuals has corrupted data in primvar st: buffer size 24 doesn’t match expected size 24588 in faceVarying primvars

The converted usd file could be separately viewed in Isaac Sim, though having the output as:

Mesh /World/envs/env_94/Robot/leg_link/visuals has corrupted data in primvar st_2: buffer size 4776 doesn’t match expected size 24588 in faceVarying primvars

But loading it requires more time (much slower than other robot types when loading 1024 robots).

I think it is a specific problem with my dae file during conversion. I checked the related output only appears in ~/.local/share/ov/pkg/isaac_sim-2022.1.0/kit/plugins/rtx/librtx.hydra.so.

Could you give me more hints about the detailed reason to trigger this output?
Thank you very much in advance.

1 Like

Hi, do you have the URDF file so I can inspect what is happening? what settings did you use when importing it too? If you don’t want to share the urdf publicly in the forum, feel free to DM it to me.

I can share mine here. Pretty much everything in the part-net mobility dataset is problematic.
mobility.urdf (36.7 KB)

Hi, I have the same problem. What is the solution? Thanks.

Hi, I have the same issue. Did you solve the problem? Thanks.

I’d need the meshes as well, do you have a link where I can find those assets?



40417.zip (3.9 MB)
Here is the complete urdf
Let me know if you have any questions.

Is there any possibility for this to get resolved?

Hi - Apologies for the late response. Are you still having any issues with the latest Isaac Sim 2022.2.1 release?

I don’t think anyone really solved this issue. It seems even Nvidia’s in-house Orbit has this issue.

you can take a look at the first image. It shows this issue.

@rgasoto for vis

Is there a timeline for this issue to be fixed? @rgasoto @rthaker

Hello, It should be fixed in the upcoming release.

1 Like

Hi, I still have the same issue in 2023.1.0

It will be fixed in upcoming bug fix release (~Mid Dec).