GeometryNode 2.0 is still to be finished, but i made some custom nodes with python already
Will evaluate the sound of the video sequencer editor volume, useful if you’d like to create mograph or effect that react to music for example.
This node will grant you the ability to evaluate a line of python code directly from geometry node. Meaning that you can go fetch and synchronise almost any kind of data in blender to geonode ( there’s implicit type conversion fo float/bool/int/vec properties, objects, material, collections etc… `)
Is Rendered View
This node will check if the rendered view shading type is active, it works well with
is Viewportas you’ll be able to have a preview of your final object also in cycles dynamic viewport (it can handle a heavy workload compared to a raster viewport).
Gather information about the scene active camera, or selected camera.
This node was made by @Strike_Digital
Creating your own node with python:
If you’d like to create your own node, you’ll need to lower your expectations ASAP. be warned that the API is still young. So far
bpy.types.GeometryNodeCustomGroup can only be used for two things, creating a simple input node, or managing an existing nodegroup with a custom interface. If you’d like to process data, you can stop your journey here.
Feedback on the socket API:
We could perhaps talk about how the API can be improved? for example it might be interesting if we could evaluate a socket value via NumPy with something such as
socket.get_array() and write it back with
socket.write_array() ? there’s also no way to get feedback when the socket is being used, I believe this was the role of
About the extra node menu:
These two plugins share the same “Extra” menu, perhaps you can take a look in the registration process of this menu, it was made so multiple plugins can use it without conflict. for users i believe it’s best to put all plugin nodes in there.
You are aware of the limitations and you’d like to create your own node? great idea this topic might be the best place to gather information about this subject?
As for potential updates:
-i believe the GeometryNodeSequencerVolume could have an slider to sample data backward or forward in time, it could be useful for users who want to create “time falloffs” of some sort. GeometryNodeSequencerVolume could also be very useful in Cycles/Compositor
ps: some of these nodes are not compatible with this new “strict” share-ability paradigm, just saying