Actually you can use vertices directly if you are instancing stuff, vertex and point cloud both are kinds of point.
you can use vertices directly if you are instancing stuff
Well I canāt do this
i need to be able to convert a mesh to a point cloud
Because i need to read my instances position from another modifier with the help of the separate componement node
Also, working with vertices directly is bad for attributes, thereās a lot of attribute missing with this and it create a lot of error 
Sorry if this is a bit offtopic, should I start a new thread with that question?
@HooglyBoogly @dfelinto
Anyway, does the developersā team plan to include the Particle nodes system in Blender 3.0 release?
I read a blog post about the discussions and workshops, but no info about whether itāll be included in the 3.0 or rather the 3.1+ release.
Thank you!
Hello, Iām seeing different nodes pop up for variables such as position, normal and index -wouldnāt it make more sense to gather these under a single node ? such as the āgeometryā shading node. I know itās been suggested already. I havenāt seen a response
1 Like
Hi all,
Iām trying to get into Geometry nodes coming from Cinema 4D, thereās a lot of things I like and the new fields project seems great.
One of the first things Iām searching for is Matrices. There are no Matrix nodes, no Matrix math, and I wonder if Iām missing something here?
Iād expect the Points to have a matrix (position and 3 vectors representing X,Y,Z), giving us the ability to work with Vectors or Matrix.
Points have PSR so they do have all the necessary data to compose a Matrix.
Normally Iād use operations such as Matrix Multiplication and Matrix Inversion all the time.
How do users do this?
For example, how would you rotate points including their orientation around an object?
Getting , transforming and setting global or local matrices is not very common in Shading nodes but itās probably important when dealing with 3d instances.
6 Likes
Matrix Nodes would be really cool indeed, even for shaders! I guess it would require a new socket type, I tried to make a little mockup in Python:
Though Matrix Transf. might belong to Vectors, Iām not saying the colours above make sense, the rest could be Matrix Math or something.
The Matrix node above could be named Combine ijk (basis vectors) for 3x3, similar to Combine XYZ + we could have Separate ijk? Not sure how to deal with 4x4. There are definitely way more knowledgeable people than me here, so Iāll leave it at that for now.
4 Likes
Great work!
But I think the Matrix is missing the position component, so it would be a 4x3 Matrix. Based on your mockup:
3 Likes
I actually like the pink color for hypothetical mat sockets! It kinda makes sense to me, I donāt know exactly why.
1 Like
I think the torus primitive has its place. Itās a no less useful primitive than any other, itās nice to have it readily available
1 Like
Iāve been following a tutorial by redjam9 with the Proximity node, and Iām exploring whatās possible: can we get the Proximity Positionās Normals? We could use it for orienting instances or offsetting instances from that surface.
Since there isnāt a normal output on the node, is there another way to get these normals?
4 Likes
@testure It has been committed! The point instance node can now instance geometry directly! Here is the radial array with only one object you asked for:
14 Likes
Great news !
is the material ok when applying the modifier?
this was an issue in the past, materials were replaced with emitter material when instances were destroyed
1 Like
Interestingā¦
I canāt use the original geometry as instance source, but I can use a primitive.
I wonder why.
EDIT: Solved, just an error from an early build, had to redownload.
1 Like
Yeah I reported that bug and Jacques fixed it very quickly.
6 Likes
Fields in master!
Letās celebrate!
Developers ā 
16 Likes
In the commit it says: āNew operator property to toggle edge panning in the keymapā
Just wondering where this is in the keymap editor as I donāt seem to able to find this option in the keymap node editor list.
Search for āMoveā operators in the node editor. Any transform operator in nodes has the āEdge Panā option now
1 Like
Ah, got it, thanks for the reply. Really nice to have all those options now, so thanks for working on this!
some way to extend it to 3dview?? would be amazing to have edge pan while dragging in 3dview.
Feature Request
- Apply geometry nodes modifier with isntances = instances with UVās.
Right now when you apply with instances, the UVās donāt preserve which is unexpected UX.
1 Like