charonos

Wow, maya scripts as well, that is fantastic news Ohara! Thanks for letting us know! Looking really forward to the release of the tools.

Off course if you happen to have access to both software packages (Maya and Max) you can just export .OBJ from maya, import OBJ into max and then export from max as a .3DS and import into O2 as a .3DS. If it works also with ArmA that way, only time will tell.

I have to add that it is not possible to export 3DS from Maya directly (maybe there is a plug-in that i don't know of), there is tools for conversion like unwrap3d or Polytrans http://www.unwrap3d.com/formats.aspx You have to reduce your model to a mesh, before exporting from maya or the converted model is said to be troublesome. Hope that helped.

I have never tried it, still on my to-do-list there is OBJ2P3D http://www.ofp.imro.pl/program....&page=1 But it doesnt look promising in terms of it's vertex restriction, there is people that manage to successfully import p3ds from 3d-studio, so maybe exporting out of maya as a .3DS and importing into max and then using some kind of script will do. It's a bummer ,cuz i am so much better with maya than i am with max when it comes down to modelling. Let us know if the tool worked for you.

That's too bad, what a pitty. Do you have an insurance against burglary? Life is sometimes hitting hard, but don't let it drag you down man.

I fixed it, using the exact code from the ArmA weapon config was the issue, those classes have a slightly different syntax than the one used in an addon config.

Out of curiosity, i have tried to declare individual ammo settings in the config of an addon, but to no effect. Even just using the same code from the ArmA weapons config in a magazine class with the same class inheritance would not work. It seems like that specific class inheritance has to be different for addons. Anyone else got that working?