@Huge i think floating point operations can be done by hardware on android.
I think there is a parameter for the compiler of the ndk.
Not 100% sure if there is automatic software fallback for compatibility.
Did you test that?
both versions seem to be nice. Don't see why they should exclude each other? But if thats the case I would like that you choose the one thats easier for you.
To my original question. What I meant with orienttopath was somethink like this:
I tried compiling Haxepunk with nme to windwos cpp. Had the same "issues". Some additional findings:
1. in engine.hx I removed
if (HXP.console != null) HXP.console.update();
cause it prevented the world from being updated
2. the Function HXP.clear does not clear the Array in world.hx This seems to be a bug on (windows) cpp.
HXP.clear(_add);
trace(_add.length); // for example 3 Bug
//Fix
var i:Int;
for (i in 0..._add.length)
_add.pop();
trace(_add.length);// for example 0
// End Fix
public static function clear(array:Array<Dynamic>)
{
trace('clear');
var i:Int;
for (i in 0...array.length)
array.pop();
trace(array.length);
}
I think that the array on the cpp side is not a reference. This is strange..
@Joshua is this a known problem?
With the fixes a World with an backdrop and some moving entities runs very smooth...
Not directly related to nme, but wanted to know if its possible in your tween engine to orient the rotation of an display object to the bezier path its moving on?
Thank you for your work on actuate and nme. They are really great tools!
