Hello there,
Posting the third release of the POP examples I’ve been calling now “POPs guide”.
This is an update to make things compatible with latest changes on alpha 6.1, plus some examples for nodes that were missing.
Some info about color-coding:
- Blue indicates that an example is available.
- Orange means an example still needs to be created.
- Black signifies that an example isn’t necessary for that node (e.g., Null).
A couple instructions:
- Press h to re-center and set the camera to default state.
- Click the show network button to invoke a pop-up with the network for a given example.
Here’s the link to the third release:
TouchDesigner Build: 32484
Almost there. There’s only 6 node examples left to go! 
Best,
Darien
(Edited post-release in the link above) 
- Fixed the parameter bug for the grid example post-release.
- Deleted a ton of unnecessary backup files.
- Removed GLSL create which is deprecated.
- UI opens in perform mode
- Explanation fixed for the file in example
- Removed unused parameter in the Group example
- Pre-emptive fix for double window on “show network” on MacOS (let me know if still an issue)
- Changed overall camera mode which seems to be better for rotations.
- Force Pop was missing. Now added as “to do”
- Point file in POP had wrong info reference
- Primitive POP had wrong info title
6 Likes
Hey Darien, thanks for updating those!
A bug that was introduced recently regarding parameters eval made it in 32484 and is affecting your Grid POP example. It has been fixed since.
Otherwise GLSL Create is deprecated and will be removed in next release, so one less for you to do!
I’ll let you know if I notice anything else.
Cheers,
Vincent
2 Likes
Hi Vincent,
Thank you for the heads up!
I’ve updated the link with a workaround for the parameter bug until next build comes out. Also removed also GLSL create from the list
(now only 6 left to go
)
Best,
Darien
1 Like
Hi @Darien.Brito, thanks a lot for your beautiful examples.
I’d like to share some feedback with you. I’m not sure if these are bugs in the POP Alpha, like the ones i exposed here: Bugs Reference, or just issues with the example files.
Just to note, i’m running it on macOS Sequoia 15.5 with an M3 Max, using your POPsGuide.0.0.1398 backup in TD Alpha 2023.32484.
- When i open the toe file, the UI doesn’t launch automatically at start, unlike in other released examples you shared. Is this intentional?
- In the “File In” example, there’s a cool violin asset, but the instructions still refer to the previous skull example

- The “GLSL Create” example hasn’t been removed. I’m still able to open it, and it shows the Analyze example.
- In the “Group” example, there’s a “group param” control, but changing it doesn’t seem to do anything.
- When I click “Show Network,” the system opens two output windows. I’ve recorded a video using the File In example to show you more clearly:
Double Window Output.mp4.zip (2.6 MB)
Best,
Edwin
1 Like
Hi @Alaghast,
You are welcome! Thank you very much for the feedback. I’ve fixed all these bugs and uploaded a new link above, in the original post.
The only one I’m not sure of is the double window you are seeing. That one doesn’t happen on my end (Windows machine), so not sure if something funky is happening because of the OS version. In any case, I’ve changed a bit the logic inside to see if that fixes the issue on your end. let me know!
All the best,
Darien
1 Like
Hi @Darien.Brito,
I’ve checked POPsGuide.0.0.1410, and the double window issue is now resolved!
Besides the bugs I mentioned here (which still persist), I just wanted to point out a few additional things:
-
The Force POP example is missing; it currently links to the Analyze POP example instead.
-
The Point File In POP info still references the previous Stanford Dragon .ply file, instead of the new boat asset.
-
The Primitive POP info still refers to the older Create POP node.
Best,
Edwin
1 Like
Hi @Alaghast,
Fantastic, thank you for keep on checking for mistakes! I’ve just fixed this new set, new link above with POPsGuide.0.0.1412 
The bugs mentioned here are MacOS specific. As I read, they will be fixed in upcoming Alpha 6.2 release.
Let me know if you notice anything else!
Best,
Darien
3 Likes