my approach is:

MDL
QME3.1 -> export .dxf frame.
Import .dxf into MAX

*animation stuff here*

Export all frames as .dxf
QME3.1 -> batch import frames 

thanks for the mdl importer, Preach. I'm not familiar with max as I'm just learning the basic lessons. I'll try them out!

I never had the idea to make the files mdl2 or mdl3. I do use the old q2mdlr9b which can import and export Q1 /2 files. 

I seem to remember that, but it brings back memories of the mdl exporting not being 100% reliable, and it isn't an ideal tool for creating animations in either.

I also remember the first times I was trying to make models like this, and I also got frustrated with the exact same pifalls: tools changing triangle orders, messing me about, declaring the conversion to mdl impossible all of a sudden. Things got much easier once I had some reliable tools to import and export models around, and a good editor like gmax to do all the editing. One thing that it really takes experience to know is exactly what kind of models you can make which will still convert to quake format. Once you have that down, it's much easier to do everything in a high-end editor and leave the conversion to the end. 

And I really have to add that the most valuable thing I learnt is MD3 format is really your friend when it comes to exporting time.

As long as your MD3 is a single mesh*, then it can be converted to quake with only a loss of accuracy in the animations, the skinmap, smoothing and frames can all be converted. So seriously, find an editor which can export to MD3(blender, gmax, 3dsmax, maya all do), give it a try, and I'll bet you won't go back.


* "A single mesh" here doesn't mean that all the triangles have to be connected in a continuous object. It's a technical thing about MD3s, you can have multiple "meshes" making up a single MD3, which then get joined together with tags. Each of these meshes can have it's own skinmap, but MDL format will only accept 1 skin, and can't do anything with the tags. I'm not saying that it would be impossible to combine the skinmaps side by side and line up the tags, but it would be a bit hard for an automated tool to do well... 

That makes things a bit clearer. So it seems that mdl2 and md3 are the extentions I have to look for.

The qmld2r9b seems a good programm as it comes to exporting 3DS. I have never come further then in and exporting extentions in it, as the skinpainter is weird with the pal format and I never knew how to add bones.

The only trick i do is importing in AM2000 so I can attach bones to make the animation. While exporting back to QMLE the verticecount doubles, but as I'm making a new model from base that won't matter.

I surely need more knowhow of Max or Blender.
But as I bought AM2000 I have the import ext:
dxf lit seg mdl(own to program) ply 3ds av2
which are quiet a lot.
Export extentions are only four:
ply 3DS av2 mdl (own to program ie not the quake mdl). 

Had a quick steamup with max3d and now I've managed to import an enforcer into max with a 3ds file.

I'm on the point that I have bones which are roughly devided over the model. But before going further I decided to check if my model still is on the same count.

Then I see I can only export 3ds and it has one vertice less?
So I import an enforcer
222 vertices 424 triangles
and it comes out as
221 vertices 424 triangles 

have you tried importing the enforcer and then exporting it again without doing anything at all in a completely fresh document?

if you're still losing a vertex then i'm not quite sure what's up... it shouldn't merge vertices on it's own. :S 

That's wierd.

The safe, but tedious, option is to export all frames to max then create a new .mdl - treating it as a completely new model. 

Here are some screenies to fill in the case...
I import an enf.3DS in Max3D and export it unchanged back to QMLE:

http://members.home.nl/gimli/max3.jpg
http://members.home.nl/gimli/max4.jpg

Nothing wrong.
Then I import the model and make my animations, export it to 3DS:

http://members.home.nl/gimli/max1.jpg
http://members.home.nl/gimli/max2.jpg

Max3D shows the right count but Qmle seem to import it different.(?!) 

You've actually gained some triangles there too. I wouldn't expect the import/export process to actually create an identical model though. If I followed my pattern of import cia MD2, then export via MD3, I'd expect the vertex count of a regular quake model to increase quite a bit, because you'd lose all the onseam information, as no other format supports that.

It's just another advantage of recreating the .mdl file from scratch each time, rather than trying to import new frames into an existing one: You don't have to worry if there's an extra vertex or if the triangle count has changed, you just start with a blank slate each time. 

hey just two questions.

How do I add custom skyboxes to my quake maps? I'm using WC 3.3 and the Darkplaces client for my Quake maps. I have a sky texture in my dev.wad called "sky", and I added the "sky" key in the worldspawn entity with the name of my sky texture as the value.

I have 6 sky texture files in my quakedir/mymod/textures dir with the names followed by the recommended HL mapping suffixes of bk, ft, rt, lt, up and dn.

However, when I test my map, I get a black box around my test level.

Also, I have a water texture in my wad with the name "!water", and it's 64x64 (as recommended), but in the game it shows it as one solid tiled chunk, and I cant swim in it.

Any help is appreciated. Thnx. 

The skybox images have to be in /mymod/gfx/env and liquid textures require "*" in front of the name (not "!"). 

can't have a filename with * in it, so i think you use # instead. 

nevermind, if it's inside a wad file, you use '*' as post #8276 says. if it's an external texture file, then use '#' 

Bareback baby! :P

Just check out one of my maps, I think they all have skyboxes except for the speedmap and the remix of e4m1. But off the top of my head i think I just called them duskeft, duskebk or whatever.

I downloaded them from kell.quaddicted.com, I remember having to delete a _ from each one. 

maybe i didnt have to even delete the character if i had put the key "sky" "duske_" 

Cool thanx for the info, I'll try it out later on today and get back to you on it. 

Ok, I got the water working, but I still dont have a skybox.

I have a "sky" key with the value "skybox_" in my worldspawn entity list.

My sky textures are in mymod/gfx/env/, and are named as:

skybox_lt
skybox_lf
skybox_up
skybox_dn
skybox_ft
skybox_bk

and they are in 24bit .bmp format.

any suggestions :) ? 

Ok, if I load my map and type in "loadsky skybox_" in the console, then it loads it, which asks the questiosn of whether or not WC is even taking into account the entity list change that I made in worldspawn. Also, I found out that the key should perhaps be "loadsky" instead of "sky", but I dont know if this is correct. And finaly, if I add "skybox_" with qoutes as the value to the key "loadsky", the map compiler says that it cant find mymap.bsp in the compile directory. Wierd huh? 

Ok, got it fixed, I changed the key to "sky" and the value to "skybox_". The sky loads now, but there are visible seams, which I'm guessing is because it's loading the wrong textures on the faces of the skybox. 

That is a JoeQuake syntax. Isnt it?

Well my skyboxes (Kells skyboxes) are not of .bmp format but TGA.


skybox_lt
skybox_lf
skybox_up
skybox_dn
skybox_ft
skybox_bk

the first line "skybox_lt" should be "rt" although I believe this is just a typo that you put into the post.

Try removing the _ from the value in the worldspawn and the names of the images.

Dont worry, it will work eventually :)

Darkplaces, AguirRe's GLQuake and FitzQuake all definately work with the key "sky", that is the normal way of doing it.


And finaly, if I add "skybox_" with qoutes as the value to the key "loadsky", the map compiler says that it cant find mymap.bsp in the compile directory. Wierd huh?

Big can of worms - "compile DIR". Just make sure that all of your bsp and map files, as well as the tools you use are inside "quake\id1", and that Worldcraft is set accordingly. Then you will avoid any annoying "file not found" errors.

Also in WC save your map and click "export to map file", then open the map file in Notepad or a text editor (not Word). The Worldspawn is right at the top of the file. You can edit/add keys/values this way, just save the file.

Learn to use your compile tools with a command prompt also, as the WC process window can be buggy as hell.....

let us know what happens when you remove the "_"s and make sure that the skyboxes are 24 bit targas (TGAs), leave the key as "sky". That should work really...... 

Try your map with different engines. Im not sure all of them will load BMP files as skyboxes. Also JoeQuake and some other engines (Qrack, Tomaz, QMB) might not load the skybox, and you'll have to type loadsky blah.

Darkplaces AGlQuake and Fitz should all work though :) 

Thnx for the info. It works now.

I got all of mt sky textures as skybox_lt, skybox_rt, etc, in my mymod/gfx/env/ dir. All of the sky textures are in 24bit .tga file format. I put in the "sky" key in the worldspawn along with the "skybx_" value. I got everything to compile fine.

I should make a note that I'm using hmap2.exe for my compiling, which i think is written by LordHavoc for use with DP.

The only slight bug I have with the skyboxes is that there are big visible seams, because the textures are not aligned properly, but this is due to the fact of what I think is the case of my saying "skybox_rt (right)" and DP saying "skybox_rt (left)". I'll fiddle with that and get backt o you.

The reason for all of this sudden commotion is because I started working on my mod. I'm experimenting with making HUGE maps (as in they go way off past the grid in the WC editor). I want to make GTA-like city levels. I got a few ideas I wanna try out. 

But remember that if you make the level too big it will take infinity to visually optimise (vis) so keep an eye on your details (marksurfaces, clipnodes etc etc). 

Yeah, my coagula map is already starting to kick my machines ass in VIS time. Grrr...