I loaded this example in 2012 and while I can see that the selection output using the sphere works in Ember, it’s not getting passed through to PFlow so none of the boxes turn red when they touch the sphere as they should with the split selected op in PFlow. The orientation/spin or scale doesn’t seem to hook up either and has no effect on the PFlow. (Alpha 3.5, Max 2012). The only thing working is that the cubes are following the velocities. Is that all that should be working at this stage?
I would like to emphasize the fact that Ember has been developed completely under 2013 so far, so I have zero experience in earlier versions of Max.
I managed to install 3.5 in Max 2012 (which is not easy given the internet connection I have at the sea resort here 
).
Playing back with Nitrous was pretty much impossible due to the slowness of Nitrous with geometry particles, but reducing the count to 100 showed the particles entering the volume and turning red (in other words being sent out to the next event, so that worked).
Then I switched Max 2012 to Direct3D.
It got a bit faster, but still nothing compared to Nitrous in 2013.
The Selection by level set worked as expected, and the Orientation channel which was set originally in the Ember Follow seemed to work right too, but it did not show up in the list of the Ember Follow operator. This was a bug in the Siggraph build (which 3.5 is based on). Our internal build for 2013 has this fixed already.
Then I set the Spin channel to the Spin from Ember and got it to work too.
Before you ask, I opened the Map Browser and the Ember Texmap WAS there. No idea why it does not show up in your case…
Everything works for me in Max 2012, using the alpha 003.5 build posted. While painfully slow in the viewport, I do see the effect of Orientation & Spin & Selection when enabled. Also I didn’t have any issues with the lists like Bobo mentioned …
I downloaded a fresh copy of the example file, opened it, and jumped to frame 25 and got this:
The behavior you describe (as well as the missing Ember Texmap) sounds like you aren’t using the 3.5 build. Double check the plugin.ini and the folder its point at to make sure its actually the build I posted. You should delete the old version completely before extracting the new one (maybe the overwrite didn’t work?).
Ok, I don’t know what I did wrong before but after re-installing it again it does work. Sorry about that.