Sweet, when I first checked out Plexus this past winter I thought āOh Iāve got to build this in Touchā Stoked to check out what youāve done. I started getting into a little C++ last winter, maybe Iāll be able to add some functionality to this and the Bullet chop when I have some time at the end of the summer.
I have made some enhancements to the DistThresholdCHOP.
It now supports specifying both a minimum and maximum threshold, and an alternate mode where it finds connections from one set of points to another set of points, optionally limiting the number of connections from each source point (though there might still be some bugs with that part).
Cool! Iāll check it out. I made some as well in the same vein as yours but it was in a rush for a project so I didnāt take the time to update the repositoryā¦
I eventually rewrote it here: [url]https://github.com/t3kt/threshold[/url], which uses shared code that can work either in a TD C++ chop or in openFrameworks-based C++ applications.
There are still some bugs though. If you want to fork the repo and fix things, you can submit pull requests and Iāll merge your changes into the main repo. Otherwise you should be able to report issues in the repo (probably in the āthresholdā one, rather than the older āDistThresholdCHOPā repo), Iāll try to get around to it when I have time.
The debugging process with C++ OPs is rather cumbersome, so at this point Iām leaning towards doing it in a GLSL geometry shader of some sort, though Iām still figuring out how that would work. I also put together a really basic version of it in a ScriptSOP, though itās way too slow to use for anything big.
Hey tetkin, it looks like a wonderful project. However I opened with my 099 and it kept saying .dll import fail. I checked the path and looks everything is correct. Do you know the reason?
File an issue on Github and Iāll take a look [url]https://github.com/t3kt/threshold/issues[/url].
Include as much info as you have such as OS version, TD build number, 32 vs 64-bit, details of error messages, etc.
Aside from reducing the number of input points, I donāt think thereās a good way to get around it.
Itās probably possible to reimplement this whole thing using a compute shader but I havenāt gotten that working yet.
Hi ! Sorry to necrobump this thread but iām trying to test this custom chop and no lines appear. I grabbed the latest version on github and am using touch 2020.24520. Could this be the update broke something ?
Hello, there were some changes to the instancing, you have to change the instance count mode on lines geo to manual and put op(ālinesChopā).numSamples, the automatic doesnāt work anymore in this case since the instancing attributes are not used (the shader moves the lines in the right place using samplerbuffers).
I am getting it working without the expression above,
but my points at slightly apart from the lines, I can live with that but itās an observation, see pic, cheers, P
TD version 2020.2450