Summary

After you posted the latest build today, on 01-01-2016, on Facebook, I tested it with Stoke and Drag Spacewarp. Drag Spacewarp works great with much lower settings like you suggested. Stoke worked great with one object. However, as I added more objects with same Stoke and Drag Spacewarp, it seemed like the other objects get the same velocities but offset somehow. I sent you a Maxfile where you can try this out.

First try adding just one of the three geometry pieces that look like rocks (labeled Box001_v_*) as a solid. Add the Field Force spacewarp first, then add the drag. Simulate using the record button as you should see the object follow the torusknot (after 50-100 frames). This is how it is supposed to work so awesome!

Next try to add the other two Box001_v_* objects, and add the Field Force Spacewarp and then the Drag. Notice that they don't follow the torusknot spline but are offset somehow. Like they are using the same velocities as the first object but somehow offset. This is not a Stoke issue as if you try to do this exact same thing with mParticles (you'd have to increase the Drag Spacewarp to 35%) all three pieces will eventually settle in and follow the torusknot velocities I setup.

Half the battle seem to be won, as one object with Field Force works beautifull just seems that when several objects are added something weird happens with how the space is handled. Oddly enough one object always works while the other objects are off with Lucid.