InsideQC Forums

Gah, end of december, no word of how to compile still

I do it all the time, I am pretty sure all you have to do is export the quake skin from qme, then put the model in quark and export as .md2

then import and you should be fine

Maybe I can help ya with it

I compile as quake 2 md2, and then convert in qme, but I just wanted to know if there was another way

I know how to export models to quake, but I see a compile quake 1 model option in milkshape, how does that work? What would a qc file look like for it?

sorry if this was asked before

Hey, I just found out dquake also has shadows! r_shadows 1 does the trick, looks great for enemies. It does not draw too much frame rate from what I can see.

I wish crowbar would release his compiler/ someone find out how to compile this engine soon. It could use a bunch of fixups

I really like your engine, baker, but external wad support would be great to have, besides the fact of the memory usage

md3 removes the jiggle factor to animated models for quake, when converting.

You could also use a high quality skin for normal quake models externally

put textures in that folder

put the textures in the same folder. If there are multiple, just throw em in the progs folder too.

or try .tga if bmp doesnt work

well, if you are in dark places, just rename the .md3 to .mdl

It should work You're joking, right? That doesn't change *anything* except the name of the file. The model isn't automagically converted into a md3 from an mdl. md3 is completely different from mdl in almost every way.

Why you would ...

well, if you are in dark places, just rename the .md3 to .mdl

It should work

I had a problem with some qc on that engine that I didn't even know why. Try it with stock quake qc...

What? That never happens to me

Its the qc

Thats really a personal problem though...