Two possibilities :
- Send message through the socket the client is listening on (dont know if its feasible, just try to mimic what servers do by looking at their code)
or :
- Inject a dll
- communicate with that dll through cross process communications (pipe, socket, events, whatever)
- when u receive signal, call the lua function or underlying c++ function.
You have to use some kind of synchronisation since u re using multiple threads. Either find the object Wow uses for LUA synchronisation if there is one, or the one of the underlying c++ function. If there is none then those functions are not supposed to be called from different threads, then u have a serious problem.
- In the external application just connect to the dll through cross process communication and send signal to print messages.

edit :
why do you want an external application anyway? LUA can do whatever you want, just go with it.

working on a VS extension to add compiled c++ code directly into exe and override or add functions  8-)

Seems many people have problems to know where panels are located so I updated first post with more informations.

I realize implementing bsp tree and collision in python is madness but well... got no choice. So it can be a bit long, and even make blender crash because of recursivity limit so be carefull when playin with node max size. From my tests i found 150 was a good limit but if u wanna change it u can

Having an error

thx for feedback, fixed it, as well as various other errors

Can't test it, how you're supposed to install that plugin ?

just copy io_scene_wmo to C:Program FilesBlender FoundationBlender<blender version>scriptsaddons

If this feature will exist the plugin will be very very inconvinient for WoW modding because the model will be full of useless doodad placeholders.

Select => by type => empty => H key.

Is it that annoying really?  :roll:

Then thats up to u if u want to keep them or not, but people (like me...) may want to at least, preserve doodads during import => export

If blender support layers. You could create a layer for every doodadset and import the m2 in there.
Then name them with full mpq path if possible.
Now people could move them around. Dont knkw how to handle size.
During export you fetch the layers by name and create again the sets, calculate the doodad positon and add them to set. Then an import m2 funtion added and it is perfect. We can then even add another doodad group by addin a new layer with correct name. And machinima guys have full model.

yep thats it, but im thinking of groups instead of layers. U could even import m2 models, hide them in an other layer, but still make the empties display the m2 at their position, so u can rotate and position doodads perfectly, then export them.
Just need an m2 import script, but if i remember correctly, there is already one somewhere...

anyway I added basic export. Does support geometry and materials. Doesnt export collision. I also removed liquid import for now...
Seems to work correctly.
/! - Mesh must be triangulated before export
- Vertices must have only 1 uv coordinate, else the result is unpredictable  :? if u have to deal with seams just separate mesh parts in 3d view

Added light and liquid import, vertex color now work correctly.
But hey WTF lights are not even used in game?  :shock: seems its only done through vertex color, m2 lights and dbc lights.

plop,
i looked around a bit and it seems theres no proper import/export WMO script for blender 2.5+
Well there was an old script for 2.4x but this version is pretty old now and it didnt support export anyway.
So i started one



can just import materials and geometry for now.

edit : Updated

problems facing :
- Since blender doesnt support texture format plugin, textures have to be png files and be in wmo's directory for them to display correctly
- M2 doodads inside wmo gonna be the hard part, I still dont know how to get this work.

/! Should work for 2.5+ but only tested under 2.7

Feel free to help, just tell me so we can organize

https://www.dropbox.com/s/62k5rul2mj7o3 ... n.rar?dl=1

Informations

Options related to wmo are given through custom panels in the properties window. Each has the name "Wow <something>" and can be enabled or disabled.

There is currently 4 panels available.



Wow WMO group panel is in Object properties, it shows options relative to wmo groups.
Group name/desc are optionnal and are just referenced from inside wmo, seems to have no effect.
This panel MUST be enabled when exporting, else export will fail.

Wow material panel is in Material properties, it shows options relative to wmo shader. The only options that are exported are shown in this panel (blender materials / texture are not exported)
Materials are displayed on faces assigned to this material.
If the panel is disabled, the material is not exported and assigned faces will not be visible in game (it can still collide though)

Wow collision panel is in Data properties and are only visible when selecting a mesh. It shows options relative to wmo collisions. "collision vertex group" specifies the vertex group whose faces will be allowed to collide.

Wow light panel is in Data properties and are only visible when selecting a lamp. It shows options relative to wmo lights. This panel will probably change later.
Lights are not exported for now.

UV
Only the active UV layer is exported. UV data imported are stored in "UVmap" layer.

Vertex color
Only the active Vertex Color layer is exported. Vertex color data imported are stored in "Col" layer.