Hi Paolo, thanks for reporting this bug, I have fixed it up now for the next v2 beta.

There is a workaround for it in the current version - if you run ArrayDir on the object first before running ArrayCurve (you can cancel out of ArrayDir instead of finishing the command), then when you do the ArrayCurve it should work properly. That won't be necessary in the next release where this is fixed though.

Also if the objects being arrayed are loaded from a file rather than freshly created within the current modeling session, it will also happen to avoid the problem in the current release.

- Michael