When you drag the file, for example "model.m3" to it, it should do the screen and make model.m3.xml in the same folder as the original model was. However it also doesn't work on some models :/ In that case it does the screen, but no model is created (It even probably writes an error, but it closes instantly ...). I'll try if the Stone Zealot works for me.
EDIT: Both StoneZealot.m3 and StoneZealotSwarm.m3 work for me.
You just drag the file onto that "m3toxml.py" or "xmltom3.py", however now I remember that you need to have Python installed as well for that, but that should probably be no problem, right ?
I don't know, but it should be possible to make a Deprecated version of it, but only while keeping the shape. However it should be possible to make a retextured, glossy version by using the M3addon master, which is pretty much the import plugin for blender.
You just use the convert to XML and then back to M3 after you are finished. While in the XML file state you can use some XML software, I'm currently using some "Firstobject" thing.
Then you can change the material values on the broken Stone zealot in blender and save the file or use some other "golden age" model. Then make XML version of both the unbroken Stone Zealot and the Broken One/Other model and open them. Then just copy the material properties of the broken one to the unbroken one and save.
This way you can make a "better retexture" as you can change the material data and light&particle&ribbon color instead of just the texture. And it will not break the armature. However it also does not work on certain models and of course you can't modify the mesh itself.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
In reply to WingedArchon:
Nice :)
In reply to WingedArchon:
When you drag the file, for example "model.m3" to it, it should do the screen and make model.m3.xml in the same folder as the original model was. However it also doesn't work on some models :/ In that case it does the screen, but no model is created (It even probably writes an error, but it closes instantly ...). I'll try if the Stone Zealot works for me.
EDIT: Both StoneZealot.m3 and StoneZealotSwarm.m3 work for me.
In reply to WingedArchon:
Good :) Hopefully it will work, however it might be a little more time consuming.
In reply to WingedArchon:
You just drag the file onto that "m3toxml.py" or "xmltom3.py", however now I remember that you need to have Python installed as well for that, but that should probably be no problem, right ?
In reply to WingedArchon:
I don't know, but it should be possible to make a Deprecated version of it, but only while keeping the shape. However it should be possible to make a retextured, glossy version by using the M3addon master, which is pretty much the import plugin for blender.
You just use the convert to XML and then back to M3 after you are finished. While in the XML file state you can use some XML software, I'm currently using some "Firstobject" thing.
Then you can change the material values on the broken Stone zealot in blender and save the file or use some other "golden age" model. Then make XML version of both the unbroken Stone Zealot and the Broken One/Other model and open them. Then just copy the material properties of the broken one to the unbroken one and save.
This way you can make a "better retexture" as you can change the material data and light&particle&ribbon color instead of just the texture. And it will not break the armature. However it also does not work on certain models and of course you can't modify the mesh itself.