Yeah I know about change the preference setting, but the ylaz or seneca script to drop object into the "ground" is still take Y as the up axis, therefore instead of drop to the ground along the Z axis (cryengine use Z as the up axis), the object will move to the left/right along the Y axis.
Kind of strange it doesn't work. As an alternative have you tried changing Modo's up axis? Not sure what version you're using, but if you go into preferences and select the 'Units' tab, you can change the up axis where it says 'Coordinate System'. If you set it to X that'll hopefully reduce the need for a script.
You might be better off using the axis rotate tool. I've found it gives more predictable results when run via macros/scripts... I've also turned this into a Python script rather than a macro. Just easier in my eyes. #pythonimport lxlx.eval('tool.set actr.origin on')lx.eval('tool.setAttr axis.origin axis…
Hi guys, recently I try to teach myself about cryengine and found out that modo and cryengine have different up axis that give a slight problem here (even though I know UDK also have different up axis then modo, but the exported geometry fbx seems fine and not lie on d ground like cryengine did). Wasn't able to find an…
Alright! after playing with copy/ paste/ type/ re-type/ etc. finally I realise what is the thing that cause problem with James' code, on line 11 and line 21 somehow create a problem and modo don't really like them, so I remove those 2 lines and all work perfect now! no more "Command Disabled" error anymore haha! My…