Unfortunately, the X format is notorious for compatibility issues between products, even when dealing with the same version of "X". If you can remember, back in the 3D Rad days, the only way I could get my static MD2's converted to X and have them actually work properly in 3D RAD (or even DB) was to write my own MD2 to X converter, which I released to the RAD community years ago. Back then just about every modeling program would screw up the X format and with it in an ASCII & Binary format back, then, it only added to the compatibility problems.
Trying to get X animations that will work with B3D is rather hard. Trying to find any modeling program that will properly import/export the animated X formats is even harder. I am not 100% sure, but I do not think that the animated X format supported by B3D can be easily converted to an animated .b3d model. I think the .b3d format is far more advanced than what B3D's X implementation is.
I think you would be better off exporting from Pacemaker as a .b3d file and using one of the third-party tools for Milkshape to import the .b3d format? Community import/export/converters:
http://www.blitzbasic.com/sdkspecs/sdkspecs.php
Somebody more knowledgable please correct any mistakes ;c)
Trying to get X animations that will work with B3D is rather hard. Trying to find any modeling program that will properly import/export the animated X formats is even harder. I am not 100% sure, but I do not think that the animated X format supported by B3D can be easily converted to an animated .b3d model. I think the .b3d format is far more advanced than what B3D's X implementation is.
I think you would be better off exporting from Pacemaker as a .b3d file and using one of the third-party tools for Milkshape to import the .b3d format? Community import/export/converters:
http://www.blitzbasic.com/sdkspecs/sdkspecs.php
Somebody more knowledgable please correct any mistakes ;c)