No one wants a 100 versions of the same model. With .m3a files you can just add what you need to the same model.
why would an animated model create 100 versions of itself? Do you just talk and not know how things are actually made or... do yo- nevermind there's no other option than you not knowing how 3d models are animated.
Importing the very same Leor_Chest_Rare.app thing? Can you attach your .obj, did you try... repeating it again? For some weird reason it might be messing up, I don't really know. But yeah, seeing the stage the exporter is in I've also encountered models that turn out like yours but really, it happening in the same model I used for my example is just too weird.
Ironically the model format was cracked like 5 days after the beta launched, it's the .tex for textures that took longer, and even that one has been figured out for a couple of weeks now.
And yes, I never know how to end my videos so I kinda just started spamming the model for no reason untilI realised so :P
Do character models work (i.e. Wizard, Demon Hunter, Monk, etc.) ????
Character models should work, except that since the converter is just starting up (really the game hasn't even been released :P) the only supported format for output is .obj. Which means that the model will not have any bones or animations. So you'll really just have an animationless character. If you could animate them yourself that's always a possibility.
For now the expoter will only export geometry info and uv coordinates. So any particle effects, emissive effects (does this game even has such thing?), animations, bones, ribbons, etc will not be available.
EDIT: last time I tried the exporting script (Like a month ago or so) it still had problems exporting some meshes, my guess is that there's still some problems even if this version should be more advanced than that of a month ago but still, you'll have lots of useful stuff.
Hey wait a sec I just saw that note now... and conveniently I also noticed "Last edited 34 minutes ago by Sixen"... HMMMMMMMMMMMMM.
looks away*
Also, I have no idea how they figured it out. I tried hacking my way to .tex files but all I really got to know is that they were .dds files stacked together and some header information. Even got dimensions on some :P but then again I don't actually know anything about programming to make something useful. I'm just happy other people do :P
EDIT: You guys REALLY need to stop editing my posts :P
In this tutorial we will do EXACTLY what the title says, really I should just post the youtube link with a description whatsoever. Though, I figured I also wanted to do a mini-text tutorial for those who don't want to view the video.
First of all, if you have not already you'll need to download an MPQ Editor and the D3 model tools pack.
1. Extracting the files:
- Open up the MPQ Editor and find the Diablo III Beta MPQs, they should be in C:\program files\Diablo II Beta\Data_D3\PC\
- Appearance models are usually found in the ClientData.mpq and textures are usually found in Textures.mpq
- For this example we used the a1dun_leor_chest_rare.app so, go ahead and open the ClientData.mpq and find that file. Extract it to wherever you wish and you should now have extracted a diablo III model file. .app files are usually found in the /appearance/ subfolder within the MPQ.
- Now we need to extract its corresponding textures, so go ahead and open up the Texures.mpq and find the a1dun_leor_chest_rare.tex, Diablo III textures are .tex files (Assume it's short for textures). When you've found the file, extract it and you should be done extracting the files.
2. Converting the files for use in 3ds max:
- Inside the D3 Model Tools Pack there's a folder called D3AppConvert2Obj, go inside and there should be a .exe called D3AppConvert2Obj.exe Copy this to your main drive directly, in my case it's C:\. So I went to "Computer" then Double clicked my C:\ drive Icon and pasted the D3AppConvert2Obj.exe in there. You should also copy your extracted model into the same place the application is in, in this case the C:\ drive (See note 1)
- With the application now in C:\ run cmd.exe with administrator privileges. (use the windows search function to search for cmd.exe and then right click it and "run as administrator") The reason we do this is cause the tool writes a .obj file, and it will need permission to run and wite in the C:\ path.
- Now that you've run cmd.exe you're probably going to be in the windows command line console in some path like C:\Windows\System32\ if you are type in "cd.." without the quotes as many times as it takes until you're just in C:\
- When you're in C:\ type in "D3AppConvert2Obj.exe -f a1dun_Leor_Chest_Rare.app" Press enter and it should convert and output a .obj file. What we just did here is told the command line console to run D3AppConvert2Obj.exe and the -f is actually a command of the program we just run (the application to convert to objs) the "-f" stands for file and the following should be the model name to convert. So in theory it's like this "C:\D3AppConvert2Obj.exe -f [filename]"
- Now with your .obj ready we need to convert the .tex file to .dds. To do this just find the other tool in the package the one in the D3textconvert_v0.9 folder and simply drag and drop a .tex file to that .exe. That simple! The application should run the console and you'll just press any key and it will have outputted the .dds and another .txt file which is the atlas information.
3. Converting to .m3 (Starcraft II Model):
- You have a .obj and a .dds file. If you don't Go back, re-read and follow the tutorial again.
- Import the .obj file to 3ds max. Using the MAX file button->import and select your .obj. You should have your model inside 3ds max now.
- Go to the material editor ("M" is the hotkey) and create a new Starcraft 2 material.
- Go to the maps and in the diffuse map slot add your converted .dds (a1dun_Leor_Chest_Rare.dds) as a Starcraft 2 Bitmap.
- Apply this material to the model and convert the model to a mesh (Select the model and right click in the viewport and select convert->editable mesh)
- Use the M3 Export Plug in to export the model as a .m3 which you can import to the starcraft II editor.
4. Importing to Starcraft II:
- You have a .dds and a .m3 file. If you don't, Go back and follow the tutorial again :P
- In the Starcraft II Editor, go to the import module and import your texture IN THE RIGHT PATH which should be "Asses\Textures\" without the quotes.
- Save your map and now import the model (the .m3 converted with 3ds max) to wherever path you want.
- Save your map and now assign a unit/model to your newly imported files and place it away! You should now have a Diablo III Model inside Starcraft II
Note 1: The reason we did this is cause the application runs at command line and I find it easier to just put it in the C:\ directly than having to cd my way to the folder the application is in.
Note 2: You should really just watch the video, I'm not even sure I'd actually understand myself in this wall of text :P
Still only static.
why would an animated model create 100 versions of itself? Do you just talk and not know how things are actually made or... do yo- nevermind there's no other option than you not knowing how 3d models are animated.
...or animate the models themselves for that matter. No need to do an m3a since you're not adding animations, but rather, making them from scratch.
I have no idea, I'll check tonight and get back at you.
@patrickwobben: Go
Yeah, you probably need to update your importer plug ins for 3ds max
@patrickwobben: Go
Importing the very same Leor_Chest_Rare.app thing? Can you attach your .obj, did you try... repeating it again? For some weird reason it might be messing up, I don't really know. But yeah, seeing the stage the exporter is in I've also encountered models that turn out like yours but really, it happening in the same model I used for my example is just too weird.
@Triceron: Go
Ironically the model format was cracked like 5 days after the beta launched, it's the .tex for textures that took longer, and even that one has been figured out for a couple of weeks now.
And yes, I never know how to end my videos so I kinda just started spamming the model for no reason untilI realised so :P
Character models should work, except that since the converter is just starting up (really the game hasn't even been released :P) the only supported format for output is .obj. Which means that the model will not have any bones or animations. So you'll really just have an animationless character. If you could animate them yourself that's always a possibility.
For now the expoter will only export geometry info and uv coordinates. So any particle effects, emissive effects (does this game even has such thing?), animations, bones, ribbons, etc will not be available.
EDIT: last time I tried the exporting script (Like a month ago or so) it still had problems exporting some meshes, my guess is that there's still some problems even if this version should be more advanced than that of a month ago but still, you'll have lots of useful stuff.
looks away*
Also, I have no idea how they figured it out. I tried hacking my way to .tex files but all I really got to know is that they were .dds files stacked together and some header information. Even got dimensions on some :P but then again I don't actually know anything about programming to make something useful. I'm just happy other people do :P
EDIT: You guys REALLY need to stop editing my posts :P
In this tutorial we will do EXACTLY what the title says, really I should just post the youtube link with a description whatsoever. Though, I figured I also wanted to do a mini-text tutorial for those who don't want to view the video.
Tutorial video can be found here:
Additional files
D3 Model Tool Pack: Link Removed: http://www.mediafire.com/?08m5vk9xc938pl3
NiNToxicated's M3 Plug ins: http://www.sc2mapster.com/assets/m3-export-plugin-3ds-max/
You will need:
- 3ds Max with the M3 Plug ins
- Diablo III Beta MPQs.
- MPQEditor, whichever you want, I used Ladik's MPQ Editor for this: http://www.zezula.net/en/mpq/download.html
- Starcraft II editor
- D3 Model Tool Pack that I compiled
Diablo III Models (.app) to Starcraft II (.m3)
First of all, if you have not already you'll need to download an MPQ Editor and the D3 model tools pack.
1. Extracting the files:
- Open up the MPQ Editor and find the Diablo III Beta MPQs, they should be in C:\program files\Diablo II Beta\Data_D3\PC\
- Appearance models are usually found in the ClientData.mpq and textures are usually found in Textures.mpq
- For this example we used the a1dun_leor_chest_rare.app so, go ahead and open the ClientData.mpq and find that file. Extract it to wherever you wish and you should now have extracted a diablo III model file. .app files are usually found in the /appearance/ subfolder within the MPQ.
- Now we need to extract its corresponding textures, so go ahead and open up the Texures.mpq and find the a1dun_leor_chest_rare.tex, Diablo III textures are .tex files (Assume it's short for textures). When you've found the file, extract it and you should be done extracting the files.
2. Converting the files for use in 3ds max:
- Inside the D3 Model Tools Pack there's a folder called D3AppConvert2Obj, go inside and there should be a .exe called D3AppConvert2Obj.exe Copy this to your main drive directly, in my case it's C:\. So I went to "Computer" then Double clicked my C:\ drive Icon and pasted the D3AppConvert2Obj.exe in there. You should also copy your extracted model into the same place the application is in, in this case the C:\ drive (See note 1)
- With the application now in C:\ run cmd.exe with administrator privileges. (use the windows search function to search for cmd.exe and then right click it and "run as administrator") The reason we do this is cause the tool writes a .obj file, and it will need permission to run and wite in the C:\ path.
- Now that you've run cmd.exe you're probably going to be in the windows command line console in some path like C:\Windows\System32\ if you are type in "cd.." without the quotes as many times as it takes until you're just in C:\
- When you're in C:\ type in "D3AppConvert2Obj.exe -f a1dun_Leor_Chest_Rare.app" Press enter and it should convert and output a .obj file. What we just did here is told the command line console to run D3AppConvert2Obj.exe and the -f is actually a command of the program we just run (the application to convert to objs) the "-f" stands for file and the following should be the model name to convert. So in theory it's like this "C:\D3AppConvert2Obj.exe -f [filename]"
- Now with your .obj ready we need to convert the .tex file to .dds. To do this just find the other tool in the package the one in the D3textconvert_v0.9 folder and simply drag and drop a .tex file to that .exe. That simple! The application should run the console and you'll just press any key and it will have outputted the .dds and another .txt file which is the atlas information.
3. Converting to .m3 (Starcraft II Model):
- You have a .obj and a .dds file. If you don't Go back, re-read and follow the tutorial again.
- Import the .obj file to 3ds max. Using the MAX file button->import and select your .obj. You should have your model inside 3ds max now.
- Go to the material editor ("M" is the hotkey) and create a new Starcraft 2 material.
- Go to the maps and in the diffuse map slot add your converted .dds (a1dun_Leor_Chest_Rare.dds) as a Starcraft 2 Bitmap.
- Apply this material to the model and convert the model to a mesh (Select the model and right click in the viewport and select convert->editable mesh)
- Use the M3 Export Plug in to export the model as a .m3 which you can import to the starcraft II editor.
4. Importing to Starcraft II:
- You have a .dds and a .m3 file. If you don't, Go back and follow the tutorial again :P
- In the Starcraft II Editor, go to the import module and import your texture IN THE RIGHT PATH which should be "Asses\Textures\" without the quotes.
- Save your map and now import the model (the .m3 converted with 3ds max) to wherever path you want.
- Save your map and now assign a unit/model to your newly imported files and place it away! You should now have a Diablo III Model inside Starcraft II
Note 1: The reason we did this is cause the application runs at command line and I find it easier to just put it in the C:\ directly than having to cd my way to the folder the application is in.
Note 2: You should really just watch the video, I'm not even sure I'd actually understand myself in this wall of text :P
Note 3: I hate onetwo (and so do I)