Alpha 2
PropertyQuery fails (silently 
) if reading BoundsType from a SIM Ember.
BoundsType is a six element int array in the parameter block and Ember/Magma doesn’t have a comparable type. This case could probably get away with a bit array, but I suspect the property query would need to expose the individual elements of the array.
Yeah, 6 booleans would do. The bit array might be ok, but using magmaflow to convert the bit array to 6 booleans… eh, sounds like a something you’d only want to do once and then promptly turn into a blop.
In reality, I didn’t need the BoundsType, I had just added it whilst adding the BoundsMin and BoundsMax and even though it was not connected to anything, it was still causing my magmaflow to silently fail.
Fixed internally, but you can grab the file from here and try it out.
Now ArrayParameter properties will be exposed as array elements in the List, and you can add any of them as output sockets.
I tested it with the BoundType and since they are booleans, they comes out as Integer 0 or 1. Thus you can convert to Float and output as a Density, or connect to a Logic>Switch or something.
In addition, dragging a wire from Position input socket finally makes a Position input channel node now.
Ember_MagmaFlow_20120730.zip (75.9 KB)