hello everyone, thank you for your great work and contributions to this amazing software!
please excuse if this is a stupid question, but is there a way to reference a POPs .numPoints like with SOPs e.g. (op(‘sphere1’).numPoints) or can you only do it via the analyze?
completely unrelated: does it also happen to someone else that the cameraViewport mousewheel functionality in a panel often suddenly stops working and you have to untoggle/toggle it in the project panel tab to make it work again?
Thanks a lot for the nice words, and glad you’re enjoying the software!
Replying regarding numPoints, it is documented in the python help, please see
It is now a function with a couple arguments, simple default use would be .numPoints()
For POPs with point count info on the GPU this might cause a stall so you can get it with no stall and a one frame latency with delayed = True (similar to next frame download on TOP to CHOP etc)
Thanks for the report on the cameraViewport. We’re not aware of that issue, but I’ve made a report to look into it further. I assume you’re pointing the cameraViewport comp to your own panel comp? Are you on windows for mac?
thank you as well for the quick reply… the viewport comp points to an out TOP in the project1 comp with “.. “ as Refpanel / Refrender is left blank.
please excuse my error if this is not the correct way to operate the viewport
speaking of which… another maybe stupid question: is there a way to access the xform and view settings of the viewport comp (yellowd out) i.e. sending them values while still using the mouse functionality? (i guess this makes no sense, but I still wanted to ask if there is a workaround to combine dynamic camera changes and still be able to operate the viewport)
gotta get this one off the chest as well: the ramp TOP (used as bg via operand: under / type: circular / extend: hold) sometimes glitches out, i.e. the area “outside” the hold starts to flicker. i think i saw this mentioned somewhere else as well with the nvidia drivers mentioned, but i am running a fairly current driver and it still drops out sometimes), unfortunately this is hard to reproduce consistently
Thanks for the extra details. I’m not clear how things are working if the Refpanel parameter is blank as you mentioned. That should normally be pointing to the Panel COMP that is receiving the input to move the camera. If you can share your project here maybe I can better diagnose what is going wrong.
As far as the xform and view settings, those are set as read-only because changing them will break the normal functionality of the cameraViewport. The preset system does allow you to blend between the user set position and fixed presets if that is helpful. You could also try nesting the cameraViewport inside another geoComp which would make the user controlled camera relative to where their parent geo is set to.
Hope that helps.
I’m not aware of the Ramp TOP bug at the moment, but I’ll make a report on that too.
I am using this in a lot of networks, and the bug with the mouse wheel happens at random moments, could not find any regularity, after mouse wheel toggle off and on again it always works again
thanks for the pointer to the nesting technique, will try that!
not sure if you saw my latest reply, also sorry if I am using the forum not correctly here, I am still new to it.
is there any solution for the glitching ramp top?
also another thing I am experiencing quite often, so this is really POP related… in some networks, once i make an attribute POP and set it to color (or even if I made one and just open it) and click on the colour picker, TD will crash.
Sorry for not responding earlier. I’ve made a report on the Ramp TOP issue, but we haven’t been able to reproduce it yet so unfortunately I’m not sure of a solution.
As far as the crashes you are getting, does it produce a dump file? If you can send those to support@derivative.ca then we can possibly get a better idea of what is going wrong. If it does not produce a dump file then you could try running the WinDbg tool which can catch more errors. We have some information on using that tool here: Using WinDbg to Debug Crashes - Derivative
You might also want to check if you have any extra software installed that could be interfering. Some utilities that try to adjust graphical settings can cause instabilities and artifacts with TouchDesigner.