Inspecting the target/update OPs with option-click seems to show that the number of Points does actually match, so it seems like this is probably some error checking issue.
Host system is an M3 Max MBP w/ 128GB ram running Sequoia 15.0.1
I was able to repair the feedback and custom force example by adding an OP to create a missing Force attribute and by adjusting the Maximum Particles parameter of the Particle POP to match the amount it was saying it had (9002). I guess this might just be a problem with the examples being stuck in a state they don’t like to be in on load.
Hello @flowb
Please make sure you are opening the samples distributed with the TD version you installed. Some reserved attribute names for the Particle POP were renamed from Alpha Release 3 to 4 and the samples were updated accordingly.
I’m fairly certain that I opened the correct samples. I actually tested the Alpha 4 package on my PC as well yesterday and discovered the same issue. It looks like re-initializing and restarting the ParticlePOP also fixes the issue. So perhaps it has something to do with the way the examples are saved.