new linux xml2g (glexemel)

[titi]

Hi I wrote some scripts that makes the handling of xml2g
much more easy. NO MORE DTD is needed next to converted files!

simply call
xml2g mymodel.xml
or
g2xml glestmodel.g3d
wherever you want!

With (un)installscript and precompiled linux 32bit binary!
( you can use your own binaries too ! Rename them to xml2g.bin/g2xml.bin | put them in the glexemel dir | then call included install.sh )

http://www.titusgames.de/glexemel/glexe ... 386.tar.gz

( What is xml2g? https://docs.megaglest.org/Converter )

[attachment deleted by admin]

[modman]

Hey, could you post the source code for that program?  Maybe I can improve it in some way...

[titi]

the sourcecode ARE the scripts!
xml2g and g2xml are not changed in any way

[Idanwin]

thx, finally got it working!
however I still have some problems, the Z&X axis have become the ground level (so I have to turn around every of my models) and the bigger problem: There are no textures!

[titi]

I asume you are not using blender for modelling( I saw this rotation problems when imported from other editors ).
If it's shown correct ( the orientation ) in Blender, it should be exported correctly.

For the texture look here: ( handling of textures )
http://www.glest.org/glest_board/viewto ... 178#p17178

and you should also have a look here:
https://docs.megaglest.org/Blender_Modelling
and especially here:
https://docs.megaglest.org/Glest_Blender_Hints

[Idanwin]

No, I am using blender (2.48 linux 32bit).

About the textures: There is no UV selection mode! (I just split an area, opened UV/Image editor, selected the verticles in edit-mode went to texture paint mode, went back to edit mode, opened the texture and saved it...)

[titi]

ok, you missed the last part with the material.
Go to object mode, select your object add a material like shown in the video...

[Omega]

Is there a Windows version?

[titi]

No, but I think you can use cygwin to use it ( but that is a bit tricky )

[Omega]

I dont even know what that is, so I guess I'll wait forsomeone to make a window version.

What I want to see is a wizard that imports and exports (directly to g3d) all on its own... I think it might be possible by combining all the existing importers/converters/exporters together somehow...

[modman]

You have to use command prompt.

And assuming that you know how to program, Titi, is there any was to get a program with an interface that can convert?
Also, I think that's PERL, right, and I have NO knowledge of it, whatever languege it is in.

[mictes]

There was an glexemel-gui, but it didnt working. Maybee you can fix it ?

[wciow]

Windows support is poorer compared to linux. Someone should build the all-in-one Blender to g3d import/export script. It feasible to do this based on the scripts that are available now but someone just has to join them together.

I would suggest a Python script in Blender which can run the exporter feed the info directly to Glexemel and dump the g3d and texture to a folder. If anyone ever makes this I will be happy    

[Omega]

Yeah... I'd love that, but I'm no good at pythons. Titi is probably the best at them, but he has a Linux OS, so it might not be Windows Compatible...

[titi]

Its no python its a bash-shell script. "Bash" is an extension of "sh" the standard unix shell, which (I think) is currently the default for  most ( all?) linux distributions. Its something comparable to the commands in a .bat file, but it can do much much more than windows .bat files can do.
Thats why it will not run in windows.

[mictes]

I forgott the name, but I read about a programm that allows you to run .sh scripts on windows, too. It's not really a programm, its an extension.
A other possibility:
There are programms which give you the possibility to convert .bat into an executable exe.
Maybee this is possible with .sh scripts, too ?!

[titi]

That's cygwin, a unix like environment for windows.
http://www.cygwin.com/

[Yggdrasil]

or use MSYS:
http://www.mingw.org/wiki/msys

btw, i patched the blender export script to run xml2g right after generating the xml file. i haven't tested it really because i have no model and no time. so can just one try it out.

the patch:

Code: [Select]

[url=http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py.diff]http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py.diff[/url]

Code: [Select]

$ patch g3d_xml_exporter_v0.1.7.py g3d_xml_exporter_v0.1.7.py.diff
and here the patched file:

Code: [Select]

[url=http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py]http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py[/url]
Copy the patched file, the converter 'xml2g' (on Windows 'xml2g.exe') and g3d.dtd in the scripts folder of Blender.
Now you should be able to export "directly" to g3d.

Hope it works and helps.

[wciow]

Thanks Yggdrasil!! This is fantastic work  

I did a simple test on a simple untextured cube and it worked fine. I'll do some further testing with textures/multiple meshes/animations later.

Two small point, Firstly windows users must copy ALL files from their Glexemel directory into the Blender/scripts directory, not just the g3d.dtd file.

Secondly, the script says v0.1.6 in the blender export menu. Is this script built on the old 0.1.6 or the newer 0.1.7 script that Titi made?

[titi]

oops   my fault.
I forgot to set the to 1.7 in my script.
I fixed it now....The current one should show up with 0.1.7

[gameboy]

i tried it but i keep getting the runtime error.

[titi]

Good job!
This works fine for me Yggdrasil !

BUT:
If there are any problems, like if you forgot to convert quads to triangles for example, you don't see any errors now!
Probably you know a trick how to fix this too? ( is there any trick to show up blenders console messages for example? )

[Yggdrasil]

BUT:
If there are any problems, like if you forgot to convert quads to triangles for example, you don't see any errors now!
Probably you know a trick how to fix this too? ( is there any trick to show up blenders console messages for example? )

I'm not sure how to reproduce that and if i understood you correctly. Do you want the error messages from glexemel in Blender?

I now catch the error stream from glexemel and show it in a popup menu. Maybe not the best solution but it should at least indicate problems. The links are updated.

the patch:

Code: [Select]

[url=http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py.diff]http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py.diff[/url]

Code: [Select]

$ patch g3d_xml_exporter_v0.1.7.py g3d_xml_exporter_v0.1.7.py.diff
and here the patched file:

Code: [Select]

[url=http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py]http://www1.inf.tu-dresden.de/~s1445051/g3d_xml_exporter_v0.1.7.py[/url]

[titi]

COOL! Works perfect!
( Sorry that it took so long to test it! Why does nobody else test it? )

One last little wish:
If you can display the messages of the xml2g call, can you display the console messages of the export script itself too? You often miss important errors which are reported in blenders console. Best of all would be a combined console window. But the current Vresion is already good enough for a new release!
But with this new feature we get a little problem: Do we release 2 scripts from now? One which produces xml files and one which produces .g3d .
Or should I switch to a combined glexemel/script releases ( but what about different operating systems/binaries? )
Any ideas / suggestions?

[Yggdrasil]

One last little wish:
If you can display the messages of the xml2g call, can you display the console messages of the export script itself too? You often miss important errors which are reported in blenders console. Best of all would be a combined console window. But the current Vresion is already good enough for a new release!

Yes, it is possible but i don't think you want the whole output. I did it now only for the triangle warning.
Hint: To get a console window on startup change the command in the menu entry to:

Code: [Select]

xterm -e 'blender -w'(for window mode)

But with this new feature we get a little problem: Do we release 2 scripts from now? One which produces xml files and one which produces .g3d .
Or should I switch to a combined glexemel/script releases ( but what about different operating systems/binaries? )
Any ideas / suggestions?

I changed the script once more. It now checks if glexemel is available or not. If yes, you have "direct" export, otherwise only the xml is exported. So, you can release it separately.