popViewer potential bug with lookupAtt

POPs
1

Please correct me if I’m missing something intentional here. In the Overview.452/proximityNeighbor example, I tried to use the popViewer COMP to verify the nearest neighbor positions but encountered an issue. When dragging the lookupatt1 POP as the Parm: POP, and turning point numbers on, it still shows the default donut points.

image
image1536×904 149 KB

When dragging neighbor1 onto it, it seems to fix the numbering, and even when putting lookupatt1 back onto it, it looks like it still has the correct numbering, but maybe its just not updating at all.

image
image1604×887 115 KB

image
image1611×884 113 KB

Is this maybe a problem because the lookupatt has 5 point attributes and the popViewer isn’t designed for that?

2

Hi BB, Are you by any chance not playing forward? Some things don’t cook properly when paused in the timeline at the bottom, or the power button at the top.

3

:man_facepalming: :man_facepalming: another riveting mystery solved! (unable to recreate so i was likely paused at the time)
:man_bowing: Please excuse my incompetence :pray:

4

no, we should handle paused timelines better. our apologies.

2 Likes