Level of Detail (LOD) API for USD Proposal Feedback

[jjzanin-SMS]

Here are some thoughts and questions I had while going through the proposal:

• Since the LodApi is the LOD manager, I wonder if it should be called LodManagerApi or LodGroupApi.
• Why have version attribute instead of using schema versioning?
• The definitionOrder doesn't seem to be needed because lodLevels relationship defines the order.
• Is levelType useful? I worry about determining the levelType in code. You would have to traverse the hierarchy for an LOD and inspect the prims to see what category it falls into. Or you put the burden on artists to set it and that might not match what is actually there.
• The collisionProxy relationship should not be part of LodLevelAPI. The hierarchy of prims that make up an LOD can have collision geometry and any other type of prim, I don't think there should be a special consideration for collision.
• Why is index a token and not an integer?
• Is index even needed? Having a separate attribute runs the risk of it getting out of sync with the order of the lodLevels relationship and the index can be determined by the lodLevels relationship.
• The example USD has the LodHeuristicAPI applied to a prim that is separate from the prim that has the LodApi. It seems like you would want to apply both APIs to the same prim to make finding the LodHeuristicAPI easier.

[meshula]

Thanks @jjzanin-SMS ! The proposal has been updated, and has resolved your concerns :)