Dealga McArdle

this does work from texteditor ```python import bpy import bmesh def get_surrogate_object(proxy_curve_data): o = bpy.data.objects.get("Surrogate") o.data = proxy_curve_data return o obj = bpy.context.edit_object if obj.type == "CURVE": depsgraph = bpy.context.evaluated_depsgraph_get()...

surrogate object is most unsatisfying indeed.

nice catch @EmergencyTemporalShift . A few things to think over: - from the nodetree there's no convenient way for a user to gain information about the current particle count of...

you could make a exec node that outputs the number of particles. ```python import bpy depsgraph = bpy.context.evaluated_depsgraph_get() for obj in V1: particle_systems = obj.evaluated_get(depsgraph).particle_systems particles = particle_systems[0].particles append([len(particles)]) ```...

hopefully you don't need to use this, but it's an option

the issue of extending lists comes down to an opinionated approach. Personally I advocate for doing the list matching in a separate set of nodes, rather than building it into...

it's a pitty that in that case the warning is now disassociated with the Node where the warning arises.

i'm not sure the above is the way to go, maybe the FilePath Node could take a single `mode` property, and depending on the mode it will fill the filename_ext...

@Durman i was thinking about that approach too.

@ArpegorPSGH another approach (which may be faster than converting to Solid) is to use a combination of a ` Vector P Field` node and a `Point inside Mesh` node. https://github.com/nortikin/sverchok/blob/master/docs/nodes/analyzer/points_inside_mesh.rst...