Inconsistency : Extent vs Extents

General Issues and Bug Reporting
, , , ,
1

Summary

Pixar made the same mistake a couple times, and it’s quite frustrating. I see you are now using extents (incorrect term; not interchangeable) in (SceneGraph:)collision_box please consider the importance of consistency.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

collision_box{Extents:=…}

Expected Result

collision_box{Extent:=…}

Observed Result

lets chalk it up to a typo that wasn’t caught in code-review…

Platform(s)

Windows

Additional Notes

extent
const TfToken extent
“extent”
UsdGeomBoundable, UsdGeomCube, UsdGeomSphere, UsdGeomCylinder, UsdGeomCapsule, UsdGeomCone, UsdGeomCylinder_1, UsdGeomCapsule_1, UsdGeomPlane
Definition at line 215 of file tokens.h.

2

It’s a shame that flags like this have to wait for a gatekeeper to even acknowledge it, before having a chance at getting passed on to @Klandar etc, to consider it.

3

+1 vote

1 Like
5

still the same typo as of v36.20

(UnrealEngine.com/Diagnostics:)debug_draw.DrawBox has

(/Verse.org/SpatialMath:)vector3 Extent

but

(verse.org/SceneGraph:)collision_box still has the typo

(/Verse.org/SpatialMath:)vector3 Extents

I suspect the former is the correct one, it also lines up with USD specs for their box types.

6

FORT-935712 has been added to our ‘To Do’ list. Someone’s been assigned this task.