When using the next instruction to create a cone, the orientation looks wrong, not sure if it is a bug from the USDGeom library or this is expected, I know I could just change the orientation by code, but just curious.
@bmayoralarauz nothing is amiss here. but here are a few notes: the axis of the object and the USD stage/layer.
when you created the cone programmatically, the default object axis is set to Z-up. however, the USD layer is actually set up as Y-up. you can actually observe the gizmo in the lower left hand corner of the viewport showing you the USD layer’s orientation. as such, the triangle is on its side aligning the object’s axis to the world:
you can verify this also via the Layer panel. by selecting the root layer (the current USD stage), you will see the World Axis is set to Y-up. by changing this will reflect in the viewport gizmo:
If you are following so far, we can move on to the cone created via Create menu. but instead of creating a mesh, let’s create a shape to better illustrate the point (Create > Shape > Cone). with what we know now, the USD layer/stage orientation hasn’t changed (Y-up). but two things are true with this new cone: it’s bigger and it’s pointed up.
i could be wrong, but the reason why any of the mesh and shape prims created via GUI have been predetermined to always pointed up-right in relation to the world axis. what i mean by that is, if you now navigate to the new cone, you will notice that it’s actually set to Y under Axis:
but if we were to take a few steps back by deleting the cone shape created via GUI, then changing the root layer’s property to Z-up. when we recreate a third cone shape prim via GUI again, it remained up-right. but this time, you will see that the shape has re-oriented itself to align with the layer/stage’s Axis (Z-up):
so what about the size discrepancy? similar to the orientation, these premade prims in OV have certain default values. and they are generally about 1 meter in size. noticed that under the gizmo, you also have the measurement displayed (cm)? this can also be changed within the layer property whenever you need. that said, by default, Isaac Sim uses 1 MPU; and the USDA you generated uses cm instead, which reflects the MPU defined in the root layer:
so that’s just a long winded way of saying the behaviors you observed and the discrepancies between the prims created programmatically vs GUI are actually expected.
in terms of solution, is it possible to set the up-axis via code? yes! it is in fact something you can do in your code or append a single line in your USDA file. here’s how to do so:
wow, many thanks for so detailed explanation! Really useful!




