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
The amPose->materialTable.set() calls in App.cpp uses an explicit OBJ name (core/icosahedron_default). This is a problem if we want to allow the new target defined modelSpec to use OBJs without this internal name. For now our new cylinder model just uses this name internally. In the future it would be good to get this OBJ name rather than hard-coding it if possible.
The text was updated successfully, but these errors were encountered:
If we keep following our current method of having models that include a flipped border geometry outside, we are probably okay having a specific object mesh/material designed to be the object and another designed to be the silhouette. Since we started with a icosahedron target, core/icosahedron_default was the material, but we could go in and change that to a more logical name like core/core or something.
I suggest we de-prioritize this fix until someone needs a wide variety of different target models since that would give us more information about how much we'd be able to modify the .objs vs. just use .objs made by someone else without modification.
I agree that this is not a high priority considering our (somewhat unique) approach to winding-order based geometry, I also agree that we should move to a more generic name (maybe core/target?). If you'd like we can keep this issue around as a reminder to transition to a more generic name.
The
amPose->materialTable.set()
calls in App.cpp uses an explicit OBJ name (core/icosahedron_default
). This is a problem if we want to allow the new target defined modelSpec to use OBJs without this internal name. For now our new cylinder model just uses this name internally. In the future it would be good to get this OBJ name rather than hard-coding it if possible.The text was updated successfully, but these errors were encountered: