[muttlieb]

Hi Pavol,

I've successfully used the new command parameters to enter additional command line flags, but the idcpu flag is not working for me. It always defaults to 0. Also, I notice if you open an .mxs with mxcl, it automatically generates a random IdCpu number each time. Is it possible for the plugin to assign the random IdCpu upon export?

Thanks.

[pelias]

I will check this with NextLimit experts - it doesn't appear to be a plugin bug though.
I remember this post from Mihai:

The idcpu is initialized to a random value when loading an mxs, you shouldn't set it yourself.

I am getting the same result no matter how the idcpu is set (plugin, studio, mxcl command line)...

Pavol