2023.32139 bug and crash from Examples Overview Trail_POP M3 MacOS

POPs
1

Thank you for adding me into this group!


I’m working on MacOS M3 Max Sequoia 13.3 and looking your examples inside Overview toe examples i discovered that Trail_POP base COMP gives me bad crash after i try to enter in it when i enable to cook it. Not sure why, but Touchdesigner doesn’t give me any crash report after it to send you.


I tried to remove each base COMP inside of it to understand if it is based from one specific example. I discovered that JoyDivision, trailExperiment1 and 2 are working properly but cacheVelocity not. I attach here the screenshots

Screen 1
Screen 11816×1410 248 KB


Screen 2
Screen 22924×1114 407 KB

2

Hello @Alaghast
Thank you for reporting the crash. The errors you are seeing might not be related to the crash. You getting this crash every time you try to navigate to the Trail POP examples?
Thanks

3

Hello @Guillaume.L ,
yes, if i enable cook on Trail POP example COMP and then i navigate in it, my system goes crash. If i remove the cacheVelocity example and do the same i don’t go in crash.
These popViewer of pictures i shared fluctuates the CPU Cook time from 7~25ms in chopped way. If i remove the popViewers and substitute them with the one in palette i don’t receive any errors.

4

A GPU related bug happening in cacheVelocity was fixed recently. This should be available in the next release.

1 Like
5

Also you have an error and it is unexpected with this version on macbook pro m1. Please repeat and capture the error. There is a crash report that you might envy.

Captura de pantalla 2025-03-26 a las 13.42.09
Captura de pantalla 2025-03-26 a las 13.42.091920×1239 110 KB

6

Hello @gnomalab
I’m also able to replicate the crash with the particlePopBananaDisolver sample on OS X (build 2023.32139). The crash seems to be fixed in our current internal build and it will be available in the next release.

Thanks

1 Like
7

I’d like to thank you for fixing this issue — the node viewer component feature inside POPs, COMPs, and the Geometry pane is really neat!

Also, I wanted to point out that in the cacheVelocity example, the popViewer nodes cause a significant FPS drop until I delete them and undo the operation. I’m attaching a video to show the issue.

Cheers,
Edwin
2025-04-19.mp4.zip (2.7 MB)

1 Like
8

Thanks @Alaghast, we will look into this.