Hi there, I'm new here.

I recently got interested in quake/idtech again and went from zero to this in the last couple of days

http://i.imgur.com/VyVhPgp.png

I'm really proud because I tried to achieve the same thing at least 10yrs ago but my comprehension was lacking then.
I learned to use blender for modeling and uv-unwrapping on youtube (DarrinLile has some great tutorials)

http://i.imgur.com/CoNfA8k.png

The model is fairly simple and the texture is just a material bake. Next step is painting the skin.
I used the mdl exporter by taniwha and arcane dimension's misc_model entity to make it show up in quake.

* Im still not sure how to properly scale and align the mdl to the floor (any advice on that?)

* Regarding animation I assume I'll set up an IK-rig, animate stuff and then export with the mdl exporter. Next I'll have to learn quakec and tell quake what to do with the stuff (Is my thinking correct here?)

* I've found no comprehensive tutorial on all of this, just scattered information all over the web. Is there like a goto tutorial for creating a monster for quake?

* Also do you guys have an irc channel to hang out at? 

IRC chan is http://webchat.quakenet.org/ #terrafusion but it's usually fairly empty. Best to post here most of the time in my experience. 

What I do is importing in an existing quake model, and scale/position mine from this one.
You'll need this plugin: http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/Quake_mdl 

Is 24 units below origin.
Small boundingbox is 32 wide, large boundingbox is 64. Small to fit. 

Scale to fit. Man, android autocorrelation really sucks. 

I give up 

 

Preach had a great tutorial on the QuakExpo2008.
This link is now in use for the QuakEpo2016.
I think it is somewhere on his site now, you should take a look.
Here is a short overview I made of it, still a must have for everyone who wants to make Quake1 models.

PreachModel 

Madfox may have forgotten that he actually helped me put this back online by filling in the gaps in my own archive of the tutorial.

https://tomeofpreach.wordpress.com/qexpo-tutorial/

The version above has bonus "annotations" where I now disagree with something I suggested in the original tutorial, so I think it's worth seeing. Nowadays it might be preferable to do everything in Blender because of the opportunity to export directly (personally I still use GMAX) so there's plenty of room for someone to better that tutorial.

Other recommended reading:
https://tomeofpreach.wordpress.com/2012/11/24/a-modelling-pipeline/ - how I make models currently
https://tomeofpreach.wordpress.com/2013/08/01/skin-maps-for-mdl-format/ - information on how skin maps work in mdl format
https://tomeofpreach.wordpress.com/2013/08/19/normals-in-mdl-format/ - mdl format has smoothing groups, get the info 

In time, when I was making the screenshots I thought myself about industriously because the pages still would be on the QuakExpo site all time.

Now I'm glad they are still be conserved as there is not that much info about the subject.
I use it when I'm off line, but the one on the site is much more readable. 

thank you very much for the link. there's some great info there (the whole site). this saved me a lot of time searching :) especially about animation and qc.

Thanks also for the tip about the -24 unit floor height. That worked well. 

Already made some progress on the skin.

http://i.imgur.com/rMyzykI.png

My UV seams are shit. I need to understand this better. Next time...

Also I've tried Krita ( https://krita.org ) for the first time. I was always looking for an opensource/linux-native photoshop alternative but I hate gimp. So far Krita works really well. 

flp that is really creepy! 

I myself use the Blender mdl exporter because I love Blender. If you want to add more skins, you have to use Preach's java script. It works well but figuring out how to get the thing to run...I always forget. Something about the pyshell maybe? Or dragndrop onto the pythongui? And where in blang's dame did I install python at again...

Wish it was as easy as just having it as a little exe you dragndrop your .py file onto /<complaint>Pleaseplease<complaint>/. 

I use 3dsmax. I then use the snapshot tool inside 3dsmax that generates a mesh for every frame of animation. I then use Keens Batch Exporter to save each frame to an ASE file.

Then I use NeroMd3 compiler to import all the frames and save it to MD3 which I then convert to MDL using Preaches command line tool. It takes me less than 15 seconds to do all this. I love batch tools. 

I'll have to check out that NeroMd3 compiler! I've always wanted to add more anims to the existing monsters. 

I'm starting again with the basics of Blender again. I'm trying to export/import mdl files but with the plug in I can't seem to handle.

Usually I make my animations in AnimationMaster and export them to 3ds, obj or dxf after first having made my most comfortable base file.
Then I import them into Qmle, and start rescaling the base skin tex to heigh 300 x */64. It's my way, as everyone has its own.

What I learned is that MeshLab is a good program to help low polymodels turn up right in Qmle. When importing a model from Q2 or 3 they are easy to controll the verts and tris to lower patterns. 

Where I'm leaning at are the so called *.bhv files that can be imported in Blender. It are drawn movements of easy animations and free downloaded at animation street site.

I'm searching a way to translate these to a model, but it is a rather complicated way to attache the drawn animation to a model.

If it would succeed it would be a practic way to add new poses to a model. 

I ment *.bvh files. 

Import your animations in Blender, make sure to assign the material on it:

1) Go into edit mode on your mesh, and on the properties section click the button with a sphere (Materials)

2) Click the + button near the top to create a new material, then click the assign button to apply it to your mesh.

3) Still in properties, click the checkerboard button next to the sphere (Textures), and scroll the control back up to the top.

4) Click the + New button to add a new texture to your material.

5) Scroll down to Image, and click the picture image. A list of images appears, pick your g_infg.bmp image from the list.

6) Scroll even further down to Mapping, and click the button right of "Map:", then select your mesh to import its UV map (there's usually just one choice).

Then export to .MD3, and then use Preach's tool to convert to .mdl https://tomeofpreach.wordpress.com/2014/08/26/md3tomdl-0-4-released/

Finally open the model in QME. If your texture is messy, just import it in there, and save your model. 

You're assuming his Blender is set to Internal Renderer. If, like me, you only ever use Cycles, you will need to change the dropdown at the center of your files tab (usually very top bar in default blender layout) before you will be able to follow Daya's explanation. 

I wish I could follow your edit way, but for now I only can import a single 3ds file into blender.

This is the base file, all add on files clip the first one so I don't see a way to import a cycle of files. 

http://image.noelshack.com/fichiers/2016/06/1454944158-shotcyclerwip.png
Based on Q2's SSG viewmodel 

I'd like to collect all the good quality remakes of Quake models that are compatible with vanilla and put them into one PAK. They should also be appropriately licensed so I am allowed to release this collection, naturally with appropriate credit to the original authors.

I currently have the new knight model and the very recent shambler model to put into this collection. What other models could I add? Vanilla Quake only, please.

I'll release this compilation via Quaketastic once you've answered my question. And I'll update it later if new models are released that I can add into it.

It's nice to have one pak you can just drop into the data directories you want, if for example you want to keep your original Quake files unmodified. 

There are a bunch of remade models in the Makaqu engine's PAK10.PAK file.

And there's also the dog and the grunt from capnbubs. 

 

I found a collection of several models compiled into one package by user NightFright on QuakeOne forums. It doesn't include the new Shambler, since the pack was created last year, but does have player, grunt, rottweiler, knight and rotfish models, and also a knight statue thing for the Mission Pack with the knight statues. (I can't tell them apart anymore. Maybe I should replay them.)

http://quakeone.com/forums/quake-mod-releases/works-progress/9573-authentic-model-improvement-47.html#post157901

The package is at Quaketastic:

http://www.quaketastic.com/files/models/auth_mdl11.zip

The parent directory has something weird going on. It is

http://www.quaketastic.com/files/models/

and when I try to look at it, it just gives me a file whose entire contents are apparently this text:

TAh....Who dey waba

This isn't how other directories at Quaketastic work. It's a bit weird to say the least. And it does mean I cannot upload an updated version into that directory.

I couldn't locate any recent versions of Makaqu to have a look at its models.

I will add the new shambler model to this package and release the result in a similar format soon. I don't have an account on QuakeOne forums, but I could see that NightFright hasn't been active there for several months. So, it's easier to make my own version rather than try to contact him and ask for an update.

I'll just have to write a readme with appropriate credits, and I'll post an update here. I'll put a preliminary version up on my Dropbox and the nask you folks where I can upload it permanently, because of that thing with the Quaketastic models directory.

(Update probably tomorrow.) 

Here: https://code.google.com/archive/p/makaqu/downloads 

Thanks. Should have looked more carefully. 

I'm now done texturing my little model

http://i.imgur.com/rrM3DdG.png

This work is really hard. I've learned a couple of things that I might do different with the next model.

1. To start with a concept. Not having any idea what I am going for lead to me staring at the blank texture not knowing how to proceed too often.
2. Work on the whole texture all at once. I did single parts. Then detailed them. Then I was afraid to touch these parts again avoiding major changes.
3. Make better seams. I'm not sure how I will do it but hiding these seams was a horrible task. This probably goes with *1 because if there is a concept I might know spots where it might be easier to hide the seams beforehand.
4. Closely watch the color range I use. I've found myself in not utilizing the full range of brightness values. I confined myself to the upper half. When exporting to quake the whole thing looked off and too bright. Had to use filters to fix it in the end.

Up next is animation. I haven't done this before so this might take a while. I plan stick to the original dog monster (regarding ai and animation) just to get it done while not overestimating my abilities.

PS: I discovered a neat website called sketchfab. It allows you to share modeling work in 3d. Animation is possible too.

https://skfb.ly/KSDT 

Looks like some kind of mount! 

That's very Hexen II-ish. I'm curious about how the animations will turn out. It looks well done. 

Looks like it needs another face on its buitt and it moves by tumbling end over end. 

buitt = butt 

Hey everyone. I had a weekend and did stuff.

I also made a model collection for myself to use with vanilla Quake the Rogue Mission Pack 2 (Dissolution of Eternity), based on a model collection by NightFright to which I added Skiffy's Shambler model.

This is a link to the zip in my Dropbox. This isn't a permanent link.

https://www.dropbox.com/s/yo98meyxvgrj574/auth_mdl_p12.zip?dl=0

Let me know if this is useful thing to share with others in the current format. I'll do so, and upload them somewhere permanently if anyone else is interested in it.

Let me also know if there are any mistakes or problems in the file, or you have some changes to suggest. THere is a readme inside.

I decided to not add any models from Makaqu after looking at them. I wanted to keep my package monster and player models only, and I like the ones in the NightFright's collection best. I used the zip format because it's not a large file and almost everyone can unzip it without any special software.

So, gimme feedback please! And tell me if there is another place than Quaketastic that I could upload the zip file to. Otherwise that is where I will put it, if anyone says I should do share it with others. I hope it would be useful to others too. 

the readme says it requires an advanced engine, why is that? I thought most of these were vanilla engine compatible. 

It was in the original readme, which I copied as a basis for my own. I took the entry to mean that it is asking whether an advanced engine required, and putting in Any means "No, any Quake-compatible engine will do." However, it's not necessarily how other people will read it.

I should change it to say "Should work with any engine" and test the paks with some other engines besides QS, so I actually have some basis for saying this. I have the GoG version of Quake with some version of DOS Quake to run in DOSBox and Winquake, so if the models work with those, they should really work with anything, right?

I'll update the readme and the zip soon. Can't start playing with DOS Quake right now, as tempting as the idea is :) 

very cool. I've been wanting to do something similar based off this n' that 

That first pic is some proper late 80s/early 90s golden age Realm of Chaos stuff as I'm sure Shambler will agree. 

http://i.imgur.com/agAjuK8.gifv 

 

This is how the dog and grunt models look in GoG-packaged WinQuake or GLQuake. Whatever it is that it wants to run with a glide wrapper. They don't crash the game, but that's not really a good look.

http://imgur.com/fqZczna

In turn, DOS Quake 1.08 fails to start when I have the pak file in the id1 directory. Sadly, I can't see what error it prints before exiting. I'd need to find out how to run it from command line instead of in a window that closes immediately, so I might get back to you on how it goes. (The problem might be that the skin is too big?)

I have found out that DOS Quake can handle the Knight model by Lunaran, but the Shambler model makes it quit. I worked this out from being able to play on E1M3 in Normal mode (no Sham-Shams) and not in Hard mode (with three Sham-Shams), while using a pak with only the knight & shambler in it.

So, I have modified the entry to say it requires an advanced engine after all. Since this is such a minor change, I replaced the previous file, and the link is same:

https://www.dropbox.com/s/yo98meyxvgrj574/auth_mdl_p12.zip?dl=0

Please check it out for any dumb mistakes. Is this package worth releasing now?

I will upload to Quaketastic and write up an announcement in a couple of days, unless someone suggests more improvements. I made this mostly for myself, but I can share it with the hope other people find it convenient. Small thing really, with all the work being done by the actual modellers. Thanks to them for their work. 

Btw the gl quake thing could be due to outdated mesh cache -- gl quake stores on disk optimized copies if the model files that it generates only if they don't exist already, so if the mdl file changes and the cache isn't cleared, it looks like gibberish in game. I think you can find and delete the files in a "glquake" folder inside your id1 folder 

Shambler works in Winquake... and the expansions 

yeah. here is a demo video

https://youtu.be/sDa8cVHDhP4

Even though this is not the greatest model I feel a great sense of achievement having successfully gone through all the steps to get a model in game. Animation and especially the running/walking ones are pretty hard to get at least decent looking.

AI wise the monster behaves exactly like the vanilla dog with a little more health since I didn't want to make anything special except getting it to work. Although I gotta say playing with quakec is where the real fun begins. First thing I did was throwing 500 gibs instead of just 3, which looks awesome. Then I replaced those gibs with ogrenades which in turn was stupid. In the end I left everything pretty basic though.

Except for the soundfx (which a buddy of mine made) I used open source software (blender, krita, mdl exporter, fteqcc, slade3) and I didn't need much else really.

I'm going to zip everything up (including, qc and blend files) and then upload to quaketastic I guess?

I'd very much like to do more of this. Next time with a little more effort. Are there projects in the making that need some models/monsters? I wouldn't want to just create something random that in the end doesn't get used. 

this is great, grats on doing the whole thing from start to finish. 

If that's your first model, it bodes very well for the future. 

I like the way the skin is smoothly animated. 

 

http://shoresofnis.com/temp/objExport.PNG

mdl -> obj exporting!
need to clean up the code and probably fix bugs, but hopefully should have a new download for my shitty model editor soon.... mdl to obj is not overly useful, but might be nice if you plan to kitbash the stock models and want to preserve the UV mapping. 

Nice work, that looks great! 

necros

Wow, so they put the texture seam on the fiend in the most visible place possible. Smooth. :) 

In most cases they just cut model in half, so you have front and back UV isle. No packing, no mirroring, ugly seams etc.
http://www.textures-resource.com/pc_computer/quake1/texture/1700/ 

I think I need to offset all the uvs by half a pixel due to the way quake vs everything else displays them, so that seam is worse than it should be. 

but I put it in the wrong directory. I meant to put it in the models directory.

http://www.quaketastic.com/files/mon_knut.zip
http://www.quaketastic.com/files/mon_knut.png

Can I move it? 

Maybe it is not the greatest model, but it is working, has its own style and finished. I mean it is not using some placeholder checker pattern instead of texture or same animation for all states.

<cough>write a tutorial</cough> 

Animation can be improved indeed, but it's a solid model. Good work. 

Where would I go if I wanted to find custom models and resources as a mapper? Be it enemies or static meshes. Is there a goto place?

@DeeDoubleU

I could write a bit about some technicalities, prerequisites and workflow. But I'm no expert in any of this. 

flp, preach has some nice models on his website -

https://tomeofpreach.wordpress.com/category/models/ 

Yes, just write down your experience like in a blog. It's always helpful to others. Also, you can get opinions, corrections... 

hey guys, as promised, here's my shitty model editor:
http://shoresofnis.com/post.php?postID=9

to convert, just open an mdl or obj, then File->Save / Ctrl+S.
You need to use the file extension drop down. Just typing it in will not work.

You can also mess around with UVs a bit too and batch rename frames with a text file.

the idea is if you are importing your model with a bunch of separate files, you can do a dir /b in the folder and dump the output to a text file.

yes, i know, this is super primitive and just awkward. mainly it was to learn 3D picking and Open GL, but it does let you bring models into your model editing program with their UVs intact, and I think the UV editor is pretty good... 

oh yeah, you can preview animations by shift+clicking to select multiple frames in the listbox.

also, when exporting to OBJ, only the first frame selected will be exported. 

Really glad with a new model editor. Surely will try it out.
It's hard to find new Q1 model editors.

I was puzzling how far I could go with only two triangles in shape of a squad in Qmle. It seems that without a max or blender I was able to compose e new rune only by adding vertices.

J- Rune 

well.... don't get too excited. my model editor is useless without a modeling program. :(

it started off as a reason to learn open gl and 3d picking. then i wanted to make a better UV editor. then i needed to batch rename frames for sock. then i needed to convert an mdl to obj and preserve UVs for a model I am making...

basically, that editor only contains things I needed. i posted it in the hopes that maybe someone else needs the exact same things. :3 

@fifth
thx for the link. I just then discovered there is an "older entries" button.

@necros
the 3d view doesn't work in linux
Exception in thread "3DViewThread" java.lang.UnsatisfiedLinkError: Can't load library: ./ne_modelEditor0.04/natives/liblwjgl.so

I dig the colorscheme of your website though

@tutorial
I did write the tutorial

http://pnahratow.github.io/creating-models-for-quake-1.html

and have put some effort into it. It's quite a wall of text. If you care to read the whole thing I'd very much like to hear feedback. 

oh... that would make sense since the libraries are windows DLLs. :(

i'll try to figure out what I need to do to get it to work in linux. 

looks like it's more complicated than just putting in the .so linux libraries. :( 

Thanks for logging what you did. It works as an overview that gets one quickly in the right direction. Congrats on the model too. 

the .so libs worked fine for me.
the app crashes a lot on file selection though.

https://drive.google.com/open?id=0ByZIVx6Ii7ooVktPX2N5Nk1JSWc 

Damn, I get errors when I tried on my emulated Ubuntu... 

I didn't get it to run even after downloading libs because I was trying lwjgl3

it worked with this:
https://sourceforge.net/projects/java-game-lib/files/Official%20Releases/LWJGL%202.9.3/

looks nice. And seems handy when browsing animation frames. 

I'm currently working on some kind of enforcer thingy as an enemy for base maps. I feel like there are a lot of enemy types for these gothic maps but base maps lack visual variety in enemies.

http://i.imgur.com/gABFNPE.png

I'm thinking of a bulky guy that maybe alternates grenades and blaster projectiles. Carrying the gun on the side like a minigun. Slow but deadly.

Not sure if I stick with whats in the sketch. Armor still seems kind of boring. 

The description seems like a tech version of the ogre which is pretty cool. Even the quake icon on the chest plate just like the ogre.

Look forward to the progress! 

Nice! I would love to model this. 

I wouldn't mind sharing work on this but the boots are still lacking definition/a general ideas plus I myself would have to do the sideview before I could start modeling. 

I hope I will be able to shoot pineapples into those pants and have the back pop off. 

naaahhhh... I won't steal pleasure from you :) I have to finish my stuff anyway. 

flp: good concept. Maybe give him a thunderbolt instead of a blaster. Use the thunderbolt on medium range, grenades on long range and a kick as a melee attack. 

I'm very happy with the the result.

http://i.imgur.com/VaJcIX2.png

I also made a lot of in between saves to document the stages later.
I might be able to reduce a little geometry on the boots and then do a weapon.
I hope it will fit in the quake poly limits 

That looks great! Nice going and looking forward to the progress! 

flp, looks very solid so far. 

Nice one flp. Give him a big gun like a mini gun or something! 

I went with Bloughsburgh's idea about the base ogre a bit and made some sort of chainsaw/grenlauncher fuse.

http://i.imgur.com/MPgv3TR.png

but I'm not entirely sure about it.

Do you know if it is necessery in quake to merge the model geometry with the weapon?

All quake models that have weapons seem to be one solid object. Could I have disconnected geometry in my model? 

Taking a base frame of the soldier in account show a model, a weapon and a gun blast. The weapon looks attached but it is diverted.
So it is best to keep the weapon apart, and the blast fire later will be used for attack scenes. 

I just reexamined some of the models in necros editor and they actually aren't connected.

I also didn't realize that there where muzzleflashes. They seem to be hidden inside the model also detachted.

Thx, now I know how to proceed. 

I think I'll stick with it. It's kinda cool.

http://i.imgur.com/OkWRNGx.png

Blender's riggify is awesome. Rigging took 10mins and it just works.
The model (including gun) currently has 681 verts, 1366 tris which should be just okay. 

I like it. Enforcer but with a chainsaw 

flp, looks nifty :) 

 

if you are making a muzzle flash, best to hide it in the gun, near the muzzle. some engines will lerp the muzzle flash and if you stick it in the body you can see it moving between those two spots which can look bad. 

Really cool to see the idea come from concept drawing to model! 

that's a spicya meataballa 

I'm currently texturing at a sluggish pace.

http://i.imgur.com/d3KFLaG.png 

Needs more brown I think? 

You are right. It's very hard to get the colors right. I don't even think there's very much blue in quake at all. I will change the weapon. I've tried color picking from the original textures to find base colors. Seems like quake in general is a world of brownish mud.

http://i.imgur.com/SpciqRk.png 

Model looks great but I'm concerned that such polygon density will cause a lot of the detail to just collapse once you run it through the meat-grinder that is 8-bit MDL vertex precision... 

 

These are just wip shots. The polycount is well in quakelimits and the model looks good in quake too.

The texture resolution is double the targetsize and also in truecolor because thats just the way I paint. There is a lot of detail that will get lost in translation. Luckily this includes some of the dullness and subpar painting.

Here's a screenshot of what it will look like after the conversion.

http://imgur.com/VHsPzeh 

The polycount is well in quakelimits

It's not about polycount - it's about vertex density, and you'll only see the collapsing verts once all the anims are done, not with a t-pose test.

However, you seem to know what you're doing so I'll stop being annoying now. 

It's about vertices that are to close to each other?

I actually didn't think about this :( Well I'll just hope for the best then. 

Really liking the progress flp! 

Basically, imagine finding the maximum X, Y, and Z extents of the model, over all frames.

In each dimension, the vertex coordinates are then quantized to adopt one of 256 values fitting inside the maximum extents.

I don't know if I've explained it well, but if you have two vertices that are very close to each other relative to the model extents (remember it's over all frames, not per-frame), then they will collapse. 

Quote: "I don't even think there's very much blue in quake at all."
http://www.simonoc.com/images/design/sp/1000cuts3l.jpg 

It should be possible to get rough aproximation with single frame by adding temp triangles on min/max values for each axis extent, correct? 

If you can reasonably guess what the biggest mins/maxs are gonna be for the animated version.

Melee attacks and death anims are usually the worst offenders in my experience. 

@Kinn

thx for the clarification I didn't know that about quake. That's probably why these idle animations seem so wobbly most of the time. Cause the animations are so small that only a few vertices skip the treshold to the next interpolated point.

Well I'll make sure there are no van damme splits in my animations.

@PyroGXPilot
Are those stock textures. The enemies sure seem to pop out of the picture. 

Hah no they're not stock. :-)

There is tho an interesting amount of blue, red, and green in Quake... it just depends on the episode/theme (and they're all earthier tones of course).

For basemap style enemies "tan" is definitely the dominant environment. 

an interesting amount of blue, red, and green in Quake
E2M5 E3M6 E4M7 Blue Article 

That's a great article BTW, it's cool that you take the time to write those up. 

yeah, i just read it for the first time too. Great, detailed post mortem. 

Wow, thank you @JohnnyLaw & @metlslime, always good to get feedback on my articles, took me forever to create it. Made my evening! 

would a touch less dithering look better on the "shirt" area? 

@Shamblernaut
The shirt area needs more detail. As of now the shirt is almost one solid color without dithering. I plan on some leather straps and more variety and then I can get rid of this awfulness. I tried a few different conversion algorithms but I might need to push pixels manually in the end.

I've also prematurely documented some of the process while procrastinating.

Here's an overview of the stages the modeling went through.
http://pnahratow.github.io/chainforcer-lowpoly-modeling-stages.html

Here is a timelapse video of some texture painting.
https://youtu.be/SlOZWpu9t7o 

Really digging everything you're doing. 

Is there some sort of hybrid between nearest neighbour and dithering that works well?

It's been probably a decade since I had to use the (I'm showing my age a little here) reduce colour depth function in Paint Shop Pro.

Also, until I started watching your video just now, it never occurred to me just how silly it is shading on what really should be a dynamically lit model. 

@ Bloughsburgh, KillPixel
ty, very much!

@Shamblernaut
... it never occurred to me just how silly it is shading on what really should be a dynamically lit model

I must say I really disagree. Sure eventually you're going to be right. But given the years of ugly plasticy looking video game renderers we witnessed ever since normalmaps entered the jungle the handpainted artwork is one of the reasons why I like quake/old games so much.
Sadly, nowadays this kind of stuff has drifted a bit into the cartoonish world of games like Dota or Lol. 

True, the tech needs to be able to emulate what you would have been able to convey with shading. The benefit is that it is dynamic. Things like the reflection on your models visor should be dynamic rather than static.

But yeah, it was a comment on the ideal situation, certainly not what is best for quake. 

Strong reflections do look very good in modern games and painting that stuff is in fact silly. 

There is an updated version of the Authentic Models package after all. I didn't find it earlier, so I went ahead and made my own candidate version a while ago. This one is dated March 2nd and contains the new Shambler model.

http://www.quaketastic.com/files/models/auth_mdl13.zip

I don't need to make and publish my own after all. This one is by the same guy as the previous versions. 

Hello, I am Hiro-Hamada from Quakeone.com

considering this is a request fourm, here is my request:

I am wanting to import a giant crab into Quake 1 darkplaces as a new enemy, and call it 'Macra'.

More info about the crab mod here:
http://quakeone.com/forums/quake-help/general-help/12114-hello-new-guy-here.html

crab can be found here: https://3dwarehouse.sketchup.com/model.html?id=aa0b6c19c73e14c269c25319f5f1c1e1

also, I am wanting to port a Special weapons Dalek that shoots rockets. It is to be a static model 

Oh! forgot a few things!

here is the special weapons dalek model:

both Macra crab and Special Weapons Dalek are from sketchup.

also, I want the crab's pinchers (the part connected to the claws) to be a bit bigger, EXACTLY like in this image: http://orangecow.org/who-sprites2/macra-sm.jpg . I also once tried before to put the .DAE model of the crab into sketchup, but look how it turned out I was told that the conversion apparently went wrong... http://quakeone.com/attachments/forums/quake-help/general-help/2137d1461374844-hello-new-guy-here-crab-error.jpg 

^^ This Hiro-Hamada above is a ZDoom modder and he's picked up QuakeC real quick and already made a couple of nice weapon mods (no kidding -- he's a quick study).

He wants to convert models to .mdl or .md3 for DarkPlaces.

Told him not too many people who know modelling participate that much @ quakeone.com lately.

Can someone give him some pointers? He definitely seems the type that if someone gives him some tips, he might make something awesome. 

Oh! yes!

I am also a big Zdoom modder!

correct you are, baker!

I am also a teen with a bit of a short attention span, and big-time autism. So I must be able to understand the explanations fluently.

I have decided to do a different type of Macra crab model. The model itself does not exist, but these pictures provide what it looks like.

https://whoflix.files.wordpress.com/2015/02/macra-terror-shawcraft.jpg

http://vignette2.wikia.nocookie.net/doctorwho/images/0/01/Macra_terror.jpg/revision/latest?cb=20120222195739&path-prefix=es

http://www.dalek6388.co.uk/images/macra.png

here is how the macra crab moves regularly:
watch 11:02 to 11:37.
https://youtu.be/1M_t6okgEa0?t=663

To attack, it could reach out and snatch at it's opponent, this crab is not slow, but not too fast.

when he dies, his claws slam down, then his anntennes and eyes slowly look down, as if it's a robot shutting down.

and That's it for the Macra crab Description. 

Correction:

tried to turn the grenade launcher into a flame thrower, but failed. all I can do so far, is go into .QC files, attempt to mess around with them (usually ends up failing), edit death messages, and change sounds. 

crab model needs more pixel density, less HD crab.
Go on! 

but flp posted a tutorial recently: http://pnahratow.github.io/creating-models-for-quake-1.html 

well, it could be turned pixel density by lowering the model polycount. which crab are you referring to? the one with visible legs, or the one that i showed in the 3 images (the one that has a big mouth, and 2 antennas) 

https://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/Quake_mdl

How do i install the exporter/importer into python. 

I also agree that the first model you posted was too high poly for q1. The second concept (from the video you posted) looks would fit it to sewer maps or tight maze maps perfectly. 

Perhaps you could use it as a base? 

https://www.quaddicted.com/reviews/housp.html 

Yes! I think the Classic Macra would fit in good!

but could someone (other than me, for i am not too good at all at making models) make a model for it? 

I've found out that several custom models out there have inverted lighting normals. This screws up with directional lighting in engines that supports it.
Here's a video.

Can this be a Blender exporter issue?

Rescaling the model in qME makes qME recreate the lighting normals, but the smoothness across non-continuous areas is lost, so it isn't a proper fix. 

That is some old skool investigation. Interesting. 

Ok, so, conidering my last post, what happens if you request someone to do a model the way I did on my last post, by simply asking (after giving info) Also, what is the best Quake 1 map editor out there? 

Jackhammer and TrenchBroom are the most commonly used map editors.

http://www.celephais.net/board/view_thread.php?id=60335&start=1284

http://www.celephais.net/board/view_all_news.php

Also: you are very new, the emphasis of this thread is more self-help and a good storage of information and helping someone already familiar with modelling figure out how to get them into Quake (which can be quirky). You can make requests, but the thread info also cautions those "may well be met with silence".

(i.e. if you are real lucky someone might "do it for you", but those would probably be something like a knight holding a different weapon or something simple and someone owes you a favor or likes your existing body of Quake maps that you have built).

You might consider getting familiar with map editors, maybe play some Arcane Dimensions (its open source, has a lot of monsters) and do some QuakeC tutorials.

http://www.celephais.net/board/view_thread.php?id=61270

https://www.youtube.com/watch?v=8YsKfkV6LV4

Doom monsters are just sprites right? Quake is far more complex than Doom and you probably should level up on mapping and QuakeC before walking down that hard road. Arcane Dimensions has quite a number of new monsters and the source code is with the download.

Arcane Dimensions has so much it can do, it should entertain you.

There is also Quoth:

https://www.quaddicted.com/webarchive/kell.quaddicted.com/ (Arcane Dimensions has some of Quoths monsters in it). 

i know that the 3ds to md3 converter i use didn't generate normals at all unless i explicitly clicked a button to do so. i never actually noticed until sock pointed it out to me though. 

Ok, most quake modding tools request a file called 'QUAKE.EXE'

What is the 'QUAKE.EXE' Of Darkplaces? 

 

now, what are the:

-Base Game Directory

-Source Maps Directory

and

-Model Viewer

for Darkplaces Quake 1 Jackhammer? 

-id1
-where you put the maps you're working on
-where you put the model viewer software you're using, like qmE 

qme 3.1 https://www.quaddicted.com/files/tools

Scroll down to qme

https://www.quaddicted.com/files/tools/qme31.zip 

And if you don't have pakscape already, you better have it available.

https://www.quaddicted.com/files/tools/pakscape-011.zip

And probably texmex:

https://www.quaddicted.com/files/tools/texmex_34.exe 

but how do i use it? it says for windows 95 only, I am windows 7 

There is a qmelite.exe

Double click it. I am on Windows 7 and it works for me. 

Lastly:

As far as I know TrenchBroom doesn't have docs (nothing does except for ancient Worldcraft 1.6)

But entity stuff applies to any editor:

Tutorial: http://www.quake-1.com/wc16a-tutorial/

Entity reference: http://www.quakewiki.net/archives/worldcraft/entity/standard/standard.shtm 

@Hiro-Hamada, I would recommend starting with the design of the monster first before modelling, especially if you plan to create the QC.

Think about its attacks, range or melee or both! Does it have any special ability? jumping, charging or stomp attack! What scale is the monster going to be? Can it fit through small gaps, drop off ledges or will it require special wide doors? What speed is this monster going to be? How aggressive will it be towards the player or other monsters?

All these considerations will affect how the monster is used and what animations, sounds and additional models it might need. 

Already have the monster design (Post # 1296)

It's attacks are described (some sort of claw pinch) a video of it's animations is provided (minus pain, attack, and death) I described how it dies, It's range is a bit far (arm length) It's a bit of an aggressive crab, heck, the pictures of the monster is provided in post # 1296! and I already have all of it's sounds.

Additional Models? 

Monster size compare:

http://quakeone.com/attachments/forums/quake-help/general-help/2143d1461799979-hello-new-guy-here-macra-quake-ranger.jpg 

The best way to do such things is to do it yourself. You're certainly passionate about it, and that's the key to making a really great work. This will motivate you to learn how a modeling tool works, and by working on it yourself you'll be able to tweak all of the little details in it to make sure it'll come out as you expect.

It may seem intimidating at first, but actually it's the best way to get help. When you need to figure out how to do rigging, uv mapping and so on, people can help by giving answers or by pointing you in a direction where you may figure it out.

The creative work of translating such technical skills into an artistic design is something very personal, and the quality of the final result tends to be directly proportional to how involved the person working on it is.

I recommend taking a look at how flp progressed on his model here for inspiration. Follow his replies to see how things worked out for him. There's a good amount of information in that discussion. 

https://drive.google.com/open?id=0B9DxOfPvG2G1WlhGNXFNQ2ZieGs

With two finished weapons in about two years, I really like my chances of making a full replacement pack in this century. 

that looks bloody great. What was the other model you did? 

Ah nvm, I found it... the nail gun thingy that looked like a flak cannon! 

I Made A New SSG
That SSG model would look lovely in the AD MOD!

Is there any chance you could add a second barrel flash for the V model? Also maybe add some more polygons for the firing trigger underneath the barrel for the G model? 

I made both shotguns a long time ago, but I didn't like them, as well as my SNG concepts, so I was discouraged from continuing. A few weeks ago I dug out the shotguns and thought they were salvageable. Although the work ratio between then and now turned out to be about 30/70%.

I'm still treating UV coordinates like vanilla Quake does, so they may be a little off in GLQuake descendants, but it shouldn't be too bad. 

Yeah, I guess I could do both.

BTW, I noticed that animation frames and/or coding of the current double shotgun in AD are slightly off. It's possible to release the trigger and still see the muzzle flash without the gun actually shooting. 

https://drive.google.com/open?id=0B9DxOfPvG2G1aFU2VlJFc1F0ZHM

Seems excessive for MDL and Quake as a whole, but what the hell. 

Thanks dwere for the model updates, I have added them to the next AD update. If you can mail me some credit details that would be awesome. 

TrenchBroom has a full manual available from the Help menu. 

Can't think of anyone else to credit. Maybe except Winchester Repeating Arms, because I totally ripped off their 1887 model.

Unless you mean my name, but I dunno. Russian names look funny in English. 

I was doing some GLQuake skin optimizations, because the target engine is QS. Now I remember why I hate GLQuake. 

https://drive.google.com/open?id=0B9DxOfPvG2G1Z3pGNHVGTmF0Qkk

GL-friendly. Don't like the lever, may still try and do something with it. 

https://drive.google.com/open?id=0B9DxOfPvG2G1Sms0N25CZ3NmbDQ 

If anyone is using my qmdl python module or the standalone fbxtomdl.exe converter, I recommend you trundle over to my blog and download the new versions.

https://tomeofpreach.wordpress.com/

The new versions incorporate several fixes to make exported models compatible with software-based engines, ranging from optimisations to visual corruption and even crashes! Thanks to Sock for his help in identifying the issues. 

Can you add a fix for the skin normals?
A while back I've posted <a href="https://youtu.be/a73Z4JxKPko";this video</a> showing the problem. 

What tool are you using which creates models with the backwards normals? Is it the fbxtomdl tool? Because I don't have the same issues with models I create from the main library. 

Those models aren't from me, they're from Skiffy and Capnbubs.

According to the readme, Skiffy used your MD3toMDL tool:
http://www.celephais.net/board/view_thread.php?id=61285&start=92 

If the normals are backwards does that make them abnormal? 

Hi mankrip, can you drop me an e-mail? My address is on my profile. I wanna send you a model which you can check that the normals are correct on. If that's so, I'll need to get in touch with Skiffy and find out what's going wrong. Unless they have the pre-2013 versions of the tool which did have a bug in calculating normals... 

E-mail sent. 

https://drive.google.com/open?id=0B9DxOfPvG2G1akY3SXFMV3BaSkE

I'll shove everything in one archive from now on. Making two versions of every model is rather butt, maybe I should stop.

Contains recent versions of shotgun, double shotgun, and nailgun. The shotgun has a pickup model that's useless outside of mods. 

I have a question. What are *.ms2 files generated by GLQuake? 

Nothing anyone should ever care about anymore. 

GLQuake reorders the model into the form that it sends to OpenGL (tristrips and fans), the ms2 file is that form cached that to disk.

Both the caching-to-disk (presumably it was faster in '97 to load the file from disk than to reprocess the model) and the rearranging into tristrips/fans are useless nowadays, so no engines do this anymore. 

Okay, thanks.

I was just searching for a way to include GLQuake-optimized models with regular models in a single package that doesn't require tinkering in order to play with different engines. It was a stupid idea, but I wanted to make sure.

This situation with model skins does bad things with my motivation. I wish the habit of shifting texture coordinates died with vanilla GLQuake, but important engines retain it (while other important engines don't), and it's some sort of a standart now (just like not paying attention to garbage fullbright pixels). 

http://i.imgur.com/w0TKakK.png 

Grenade launcher? Like the model. 

What do you mean with shifting tex coords? First time I've heard of that. Just being curious... 

Software Quake (as well as several source ports, including darplaces, strangely enough) places tex coords between pixels. GLQuake shifts them half a pixel right and half a pixel down, placing them at the pixel centers. Elaborate detailing goes out the window. Fitzquake/Quakespasm are also affected. 

Find the Quakespasm thread, do "show all posts" or start at 1 or whatever it is to see every one of the 2000+ posts.

Then in your browser Find look for the word "coord" and you'll find an informative discussion on this from a couple of years ago that discusses the differences that dwere refers to between software Quake and the hardware renderer versions. 

Do you have techniques to minimize the damage? Or do you just work with one engine and hope your model won't look too broken with another? If it's the latter, then which standart do you prefer?

I was thinking about the former, and I can see a way to preserve symmetry where it's needed, but it'd require constructing the model in a certain way. Simply making something decent is hard enough for a novice, and then I have to worry about all this compatibility nonsense.

Why, GLQuake, why? 

When I made the static entity for a convoybelt the hardest part was to make the cell_ammu blocks correspond to each other.

When they all four made the simultaneously movements and I had it right counting on the framenumbers the different engines all made their own movements.

Framegrouping helped, but as each engine treated it accordingly strange effects was the result. 

I'd go with designing your models with GLQuake in mind, for two reasons. The first is that so many more ports are based on glquake, and they're so much more widely used, that they've become the de facto standard now - even if the software vertex placements came first. Secondly, the software renderer has so many approximations and wobbles when it comes to alias models that it's not going to benefit from that level of care and attention.

As your screenshot seems to be going for a pixel-art look, I wondered if you could try doubling the scale of your skin. So each "pixel" on the visible skin would actually be a 2x2 block of pixels. Sure, you've effectively wasted 300% memory compared to the original, but the GL and Software renderings will be more alike. As a bonus, it might look less "muddy" for people not using nearest neighbour in the GL world. 

DirectQ and Darkplaces are using the original way of interpreting tex coords, so it's not that simple.

As for your second suggestion - IIRC, the software renderer can't work with skins taller than 128, so I'd have to redo a lot of things. In any case, I'd rather not resort to something like this.

Thanks for your thoughts anyway. 

I believe the limit is 192? 

regarding max mdl skin height.

MAX_LBM_HEIGHT appears to be 480 in winquake/glquake, here.
Dosquake had a lower limit iirc. 

The limits for skins:

In DOSQuake the max is 200px (so 128px is the tallest power-of-two, the largest sensible size)

In Winquake, that gets bumped to 480px (so 256px is the largest sensible size)

I don't think you need to worry about DOSQuake, I'm pretty sure all the custom software engines start from a base of Winquake at least. For reference, Quoth has included models with 256 pixel tall skins since the first release and nobody has ever complained that it causes a crash.

Bit more of a pain that there are non-software engines emulating the old behaviour. For darkplaces you have the option of creating MD3 copies of your models, with UVs that match the GL versions. Which only leaves DirectQ... 

 

Does anyone still use DirectQ? I stopped using it about 6 month after I joined func_ 

I stopped using it once development/support ceased. I would like to see quakespasm implement the HUD options that DQ had.

DQII was great, would love to see a final build with some of the loose ends tied up. 

I remember a request for tree static entities.
I am using some in my new map so
they may be also in others interest.

Quake trees 

 

forest
<a href=""http://home.kpn.nl/lo2kf8/tree1.jpg">for</a>
<a href=""http://home.kpn.nl/lo2kf8/tree2.jpg">the trees</a> 

for
the trees 

For some reasons statics that are under 1000verts ans 2000 tris won't show up in fitzquake.
Like these trees, there's one that shuts down fiztquake immediately when added to the progs.
It's just the same as the others but it won't fit. 

if not for the entire tree, just the foliage?

The trunk looks quite nice in those pics, but those leaves aren't so hot.

old sprite tree test 

I guess I'll just leave this here: http://www.celephais.net/board/view_thread.php?id=60831&start=994

Would be nice if more engines supported it :} 

Just one fairy sprite and you'll be able to recreate Ocarina in full :) 

I like those...

Madfox, the trunks are ok but the leaves being giant squares don't seem to look right to me. I think what you've created would look good if there was masked texture support (where you put a { before the texture). 

like
these
too 

yes! 

#1372 - Thanks! full-on sprite trees probably aren't appropriate for vanilla quake, aesthetically speaking.

#1373 - those look nice, are the trunks simply brushes? that map reminds of something out of spyro. 

Doesn't look that good. Can't be lit and breaks down when you're close. 

Has anyone done the conversion of the Quake 1 mdl files into a skeletal animation format? The idea would be to use skeletal animation skinned to a rig that would maintain a fairly close match to the original animations, for use in engines that don't support vertex morph animation. 

Thre are engines that do not support changing the values of the vertices of a model? Odd, to say the least... 

I converted several Q1 models into an animation studio by using a redrawn base model of (let's say) a death22 pose frame of a monster.

This is done by using a skeletal base bone and attached it over the new base frame.
From that point I can change it into any pose and export it into any commen format. obj,3ds etc.

So far so good.

I'm not familiar with vertex morph animation. 

I decided to take a break from original content and do something I wanted to do for a long time: touch up the existing weapons so that they look less broken in the modern era of neat, polished visuals.

Then I decided to take a break from that, so I'm releasing what I currently have: all view models except axe, one world model.

https://drive.google.com/open?id=0B9DxOfPvG2G1UDZtLXA1MXVSWlE 

By existing weapons I meant stock weapons, of course. 

some nice improvements. I like the extra shadows on the NG and RL.

The world LG model is really awesome. Love the little touches you've done there, like the cell ammo on the gun at the butt, super nice.

Not 100% sure on the more rounder LG. I think the sharper edges of the original make it feel a bit more violent maybe. It still looks nice but I'm not used to it I guess.

I'd say the SNG skin could be tidier on the bottom of the barrel but is otherwise nice. Similar on the SSG, looks better but the texture blending near the bottom of the barrel is a bit too sharp.

Cant see what's updated about the GL, it's a shame that the v_model was basically a cylinder. Would love to see a touch more depth to the model? 

I made a bit of a modification to the SNG skin to demo what I am talking about, it's not super clean because I'm not sure where the wireframe is exactly (lots of trial and error here).

https://www.dropbox.com/s/ykzofayufsec0vs/v_nail2.mdl?dl=0 

Yeah, the SNG bothers me too. I probably should've left the bottom connected to the barrel itself on the skin, but I wanted to avoid distortions after having problems with SSG. I don't want the barrel to look as monolithic as on your skin or in Arcane Dimensions, but the parts should be connected in a more natural way.

GL is pretty much the same. The mesh is less crooked, the skin was reorganized, the flash was redone, but those are subtle changes.

As for LG, I think it's pretty clear from the skin that those things were supposed to be round. Being square made them weird - I mean, I understand conserving tris, but in this case it looked ridiculous to me. I even considered smoothing them on the pickup model, but forgot. 

I did notice that you had redone the skins on each model, they're much easier to understand now, less wasted space on them.

I think the barrel of the SNG is probably better smoothed off at the end. It's subjective, I never did like the black holes at the bottom of the originals. 

Well, the black holes won't be black holes in any case - the main reason for updating the skin was to get rid of them. 

http://i.imgur.com/vMJuLHR.png

I didn't want to stray too far from the original designs unless absolutely necessary, but I dunno anymore. 

I kind of dig that actually. 

http://i.imgur.com/4bj2m3m.png

Took a break my ass. 

From a technical standpoint that is some really nice texture-work. From a purely subjective standpoint it looks a bit like a mans willy... Dr Manhattan's big blue one.


hahaha... sorry, I know you probably don't want to hear it cause you've put a lot of love into it. ;) 

IMO all of quake's weapons should contain phallic design motifs. The rocket launcher always took pole position in my list of favourite slaying tools, and I like the fact that dwere is enhancing this aspect of the game. 

needs to be usurped from it's big girthy, veiny, throne. 

I was well aware that a certain amount of people tend to see things in random elongated objects. When using elongated objects in art, one can only hope that none of those people would be brave enough to openly admit it.

BTW, don't blame me for SSG. It always looked like balls. 

I see dicks everywhere 

https://drive.google.com/open?id=0B9DxOfPvG2G1Q2Z2a2Izd0ppWTQ

For those of you who were waiting for the Improperly Aimed Quadruple Dildo Gun: I'm sorry, but I had to partially cover it to avoid AO rating. 

these are bloody awesome! The b-models are exceptional. I do hope that the grenade launcher gets beefed up a little on the v-model though, it needs to look as epic as the b-model.

Great work so far though! 

That was me btw... wasnt logged on 

I'm flattered.

I don't know what to do with v_rock. Tried adding a few more polys, didn't like it. I think I shot myself in the leg by making the SNG casing look so elaborate on the view model. Now other things look blocky. 

V rock is OK tbh. Has plenty of polys... It's the grenade launcher that's the problem 

I meant grenade launcher. Rocket launcher is v_rock2. 

There was a high poly one that looked good, cant remember where to get it now though. I think just turning some of the texture detail into actual geometry detail would be enough to improve it. 

http://i.imgur.com/ipWxAWR.png
http://i.imgur.com/i83g8TH.png 

I'd say that's an improvement. I guess it's preference really. 

That's the best solution I've ever seen. Now it's just a matter of adding a small rounding around the edges of the darker gunmetal parts, and it'll be perfect. 

I think rounding would be too much. I'd rather leave it as it is (inlaid wood, simple corners), otherwise I'll have to do something with other models as well. 

You could bevel top edges. 

I know, I did, didn't like it. 

What I meant is to bevel the edges. I didn't know the "bevel" word yet, I'm not a native English speaker. 

https://drive.google.com/open?id=0B9DxOfPvG2G1VmI4ck5HcHZ1Ymc

Axe seemed to have a potential to be a giant pain in the ass for a relatively small gain, so I decided to postpone it and go straight to the software mode testing stage. Some of the models crapped out much worse than I predicted, but I fixed the most glaring issues by adding redundant geometry.

Fixing the less glaring issues would require adding even more crap and mangling the shit out of skins. I felt bad enough while applying the basic fixes, so I probably won't go any further.

Compatibility issues always cheer me up. 

Liking the update so far. I think the bevel works well on the GL. 

After days of tinkering in MAx3d I begin to remember what it was to import a quake1 model.

One is to find the right dxf exporter with quads.
HDXFEXP Export PlugIn
Designed (X) 1999 by hab.

Then after boning the model it seems as if the attachment won't bring up an animating scene.
The bones animate, the model also, but the animation bar won't respond.
It seems I can't make keyframes odf the imported mesh.

So I'm saving every frame for free, which is a rather long way for a pose.

But yes, I can add new models to an excisting original.
stupid ogre 

http://images.imgur.com/3nldAfK.png

Ironically, I spend 90% of my time tweaking things that 90% of people will never see (this is a FOV 110 screenshot). 

Now someone should increase brush count on all vanilla maps. 

Just wondering if there is any updates coming on mods or anything, that shotgun looks like it should fit in quite nicely mega/super super shotgun. I'm not saying that ad mod's version isn't good or anything, but feels a bit out of place. It's interesting to know that many of those guns were actually scanned, and they scanned mostly toys when id was working on gun models, so I can't say is that the most professional way to do it.. but I guess that can make quite unique guns. 

I think I preferred the symmetrical one. Actually I thought you were pretty much down with the models, I've been using them! 

I'm mostly doing compatibility tweaks now, but sometimes I see less under-the-hood things I'm not entirely happy with, so I change them as well. 

 

 

I laughed. Sorry. I have a dirty mind. 

you need boned? 

Heh heh! Is that the same skeleton (recolored, it seems) that's in your Veni Vidi Fuzzi map? 

Static entity of 124 snowflakes on a 512x512 dimension.
Still a small glitch, but if I succeed to break the symetric patron
it could have a flakey environement.

Flakes are 8vert/12tris, the demo model of qmle.
Now there are 21 frames but it could vary to more.
If I lower it to half I could dazzle 248.
Hey Shambler! 

I'm afraid it will break when interpolation is enabled. First and last frame will do a weird interpolation, but I may be wrong. 

you could solve the rain lerping upwards for one frame by having the drop go to zero scale the frame before and after the upwards lerp.

-metlslime, general abuse thread

nice test, madfox. is it necessary for the flakes to be models or could they be sprites? 

That sounds like black magic... but I like this attitude. 

My first test was with a sprite, but as I haven't fixed the viewframe with it, it keeps turning.
When it are models of a small size it's easy to fill up 124 of them or even more. Only bad is animating as the lot gets me dazzled.

Strange falling startframe without framegroups.

in game 

I made the flakes smaller so the amount is larger. There's that strangle sizzle in the animation, as if the interpolation slides along the stroll. It makes no difference if I use framegroups or not.
So far I'm glad with the result.

Now I bit of turbulence. 

Because the uniformity isn't great (I know it's only a test). And the white colour doesn't suit the quake aesthetic at all. It would probably work on a whole new palette / texture set though.

http://www.howtogeek.com/wp-content/uploads/gg/up/sshot4d2ab8c3eb126.jpg

The concept is interesting to me, I'm fairly sure particle effects would look nicer though. And would maybe be more "quakey". 

.. are a little bit too organized IMHO.
This would need a little bit more of randomness to show up like real snow fall... anyway...
Good try ! Keep it up ! 

It's a static entity of 90 frames and caused by a qc-file. Result is a coloured skin I added, but my main concern is the interpolation.

I know it's been a point in earlier statics I made, but the ignorant collapsing of the first frame destroys the view of it.
It seems to make no difference if I framegroup or not, the first frame keeps on falling back.

They are surely too orginized, but I have to take a little care with the amount of triangles. They now are on 1525verts/1830tris.
So it's more a case of seeing the engine can handle the lots of flakes.

Particle effects would look better, but imagine, this static entity carries 305 flakes.
If it would be individual ones 305 entities would be needed. Now they're closed in as one. 

Just an another stupid idea how to make it more optimal.. would it be possible to make circle raycast check or something, from player to some range.. increasing range more and more, grouping snowflakes and giving them different alpha values.. or just making them much smaller until they dissapear from player's view.. after all player wouldn't notice that if done right. But that should make it much faster I believe.

Hopefully you get the point, sorry my terrible English skills. 

Madfox made a model.

Models can't do raycasting. ;-) 

nononono.. I mean program code? 

I trimmed the flakes into a circling motion so the symetry is broken, but by scaling them out the shape of the flakes become to pronounced.

mdl

In game the large shape is rather out of place, or I should try to make them smaller.

@newhouse- I'm already glad I can spawn the static without typo's. My first idea was to use the viewport to project a transparanr sprite, but that wouldn't have depth.
Maybe a sphere that surrounds the player could catch up with a static ebtity, but as far as I know statics are lame. 

http://imgur.com/gallery/K45sm 

https://drive.google.com/open?id=0B9DxOfPvG2G1Y1BSWmRJMkczY1U

New: axe, grenade, nail, super nail.

Changes:

- Lots of tweaks.
- Played around with Edge Split, mostly for source ports that use Gouraud shading in a meaningful way.
- The view weapons should look semi-inoffensive in FOVs up to about 130. In Quakespasm anyway. The value might be lower depending on your engine and settings.

Then there are optimizations of various levels of retarted. They were supposed to make the models look better in software engines, Darkplaces, and the like, without affecting how they look in Quakespasm et al. Results:

- My sources are a mess.
- The result for software engines is underwhelming.
- Darkplaces and DirectQ look serviceable.
- I introduced a very subtle glitch in the intended engines.

Nevertheless, I think it was educational. I probably won't do that again. Making two versions of each model (just like I wanted from the start) would most likely be a better solution. I thought it would make a mess, but now I'm not sure which of the two evils is the better one.

One thing the latter approach would certainly help with is getting 100% OK result for each engine (instead of 99% for half of them, and 80% for the other half).

One thing the current approach is good for is a partial conversion with maps. I wouldn't want to complicate it with two possible setups. Another reason to not redo everything immediately is the fact that I'd have to go over the skins again just to be thorough. Ugh.

Despite all this, I more or less got to the point where I almost don't really hate this thing all that much, so I'm considering it to be one-point-zero. 

 

Incredible work Dwere !!
I like them very much.

If you need some comparism screenshots or gifs, please visit this page:
http://quakeone.com/forums/quake-mod-releases/finished-works/12408-new-faithful-weapon-rework-dwere-da-werecat.html

Thanks again,
Seven 

Heh, wow. Thanks.

Yeah, the gifs are appreciated, since I didn't make such comparisons myself (other than between versions, comparing new models to slightly older new models). 

Very good job, dwere. I'll stick to the hi-poly weapons I have installed but I can definitely see this as a default replacement for id's originals. Well done. 

What is the version you're using ? Where can we find it ? 

https://drive.google.com/open?id=0B9DxOfPvG2G1YXRNZ0JqQVNHdTg

Fixed subtle glitchy seams where I found them. 

I'm using Ruohi's. Check this link: http://quakeone.com/forums/quake-help/general-help/10727-definitive-hd-replacement-content-list.html
They're the first entry in the "Weapons" section. Two .pk3s to drop in \id1, one for the equipped weapons in the player view and one for the pick-ups. If your engine doesn't support .pk3 format, just unzip them in \id1. 

The link is akward to use, and I need a proper .pak file to work with Quakespasm. And I'm on OS X, so I don't have any tools to make pak files.

Please, could you give a link to a proper weapons PAK file for Quakespasm ? 

Awkward to use? Huh! In what way? I can access the page just fine, even on my phone. The dropbox links to the files are at the top of post #2. pk3 is simply a renamed zip, so you can extract the files and build the pak yourself using a program like PakScape - I have no idea what programs exist on Mac, so the research is up to you. If you still can't manage to sort it out, let me know and I'll see what I can do. 

Thanks,

I successfully downloaded both pk3 files and unzipped them. I'm getting several prog and textures files, that I could drop into the prog and textures folders in the id directory, but they don't show in Quake. I'm not even sure that Quakespasm could use them. I'm unable to find any tools on OS X to make them in a proper PAK file for Quakespasm.

Is it possible for you to try to make a PAK version for Quakespasm ? That would be great ! 

Quakespasm complains about the wrong MDL version number. Apparently, these models are in a modified format or something. 

I made a pak with the files and tested it in QS. It doesn't work. Apparently there needs to be some modification to the progs.dat to make them work, but this goes beyond my knowledge. Use them in Darkplaces or search for info on how to make them work in QS. I'll upload the pak if you want but besides that, I can't help you further. Sorry. 

That second (allegedly more faithful) weapon pack works in QS (unpacked), but the external skins don't load. It makes some models black or indistinguishable from the stock ones. 

No need to upload the PAK (unless someone else wants it), since it wont work in QS anyway. This is sad, since these HD weapons look awesome.

It would also be great to have an HD version of the HUD, in Quakespasm (I'm not asking HD textures for the game itself, i.e. monters and maps, since it would look ugly for that old game).

dwere, your weapon PAK is working great. The improvements are very subtle, though. Personally, I would prefer some higher HD weapons, since I have them "in the face" constantly, like the HUD. 

A quick glance at this thread http://quakeone.com/forums/quake-help/quake-clients/12339-quakespasm-hd.html and I found an answer by our esteemed Baker: "Quakespasm doesn't support model replacement textures." There you go. Maybe the Spiked version does?

For QS, use either dwere's pack or NightFright's Authentic Model Compilation. The latter will replace the original models of monsters, weapons and pickups with slightly higher poly versions while using the same textures.

Or switch to Darkplaces if you want to dabble in HD content, that's the best solution for now. 

The improvements are very subtle, though.

Well, that was the point.

I haven't tried myself at HD content yet. Well, excluding some embarrassing crap I made when I first discovered Tenebrae. Luckily, I had enough sense in me to not share it with anyone.

Maybe the Spiked version does?

The changelog doesn't mention it, unless I'm missing something. 

I'm sticking to Ruohi's for DP but your pack is definitely adopted for my QS. I find yours better than NightFright's, especially the axe, GL, RL and LG. Not sure about the big thingie you added on the handle of the SNG though, but I'll get used to it. 

In case you don't know, Seven created this thread http://quakeone.com/forums/quake-mod-releases/finished-works/12408-new-faithful-weapon-rework-dwere-da-werecat.html
There's a guy there complaining that your pack causes the demos not to play on vanilla/PSP. 

Upon closer inspection (I opened the pak file), it would appear that NightFright's pack does NOT replace the weapons. 

I included quake.rc to modify some settings, and I forgot that it was based on an already modified quake.rc that didn't include the startdemos command.

I'll fix it later. 

That's some rapid development!!!

https://drive.google.com/open?id=0B9DxOfPvG2G1YmNPUmRFMDV4YU0

From the changelog:

- Restored the startup demo sequence.
- Brought back the nozzles that were removed from the barrel tips of the nailgun (view model).
- Fixed fullbright seams on the view model of the super nailgun. 

New link added to the QuakeOne page. 

Knowing there's already weather additions to Quakespasm I continued my own versions with a static mdl file.
These were made with a one mdl file on a 512x512 surface.

rain
snow 

I think you should make snow with sprites instead. It's weird to see non-flat snowflakes, and you could use an actual snowflake texture for the sprites. As is, they look more like hail.

As for rain, if it's possible you should make it transparent to prevent this icicle look.

Good job anyway. 

It has rain and droplets when it hits the ground, maybe you should look into that 

Does anyone know if there is a simple skin utility to add skins to a quake 1 .mdl file? Adquedit doesn't seem to be loading the palette correct anymore for me. 

Quake Model Editor 

Thanks Dwere, I'm using your grenade launcher and axe models now. That hand was pretty well done. 

 

I did that "refactoring" I was talking about.

https://drive.google.com/open?id=0B9DxOfPvG2G1NC15bnVkRjlmY0U 

Tweaks must be very subtle at this point, not sure what's changing! 

A pixel here, a pixel there.

Well, it's not that subtle, but, honestly, I don't even remember what I did between the latest versions, other than v_nail barrels being redone almost from scratch.

They look more or less the same though.

Really, 90% of my time I'm dealing with compatibility crap instead of improving the artistic aspect. Rant rant rant. 

Hah fair enough. It would be nicer to have one set of models really. Loving the models, using them mostly as the defaults now. 

 

Check Quaddicted. 

 

Try running the installer in compatibility mode.

Right click > Properties > Compatibility

Check the box and select an old version of Windows (probably 95 or 98/ME)

or use Compatibility Troubleshooter:

Right click > Troubleshoot Compatibility 

The Quaddicted 3.1 Lite download is a .zip file.

I use Win 7, all the executables in the .zip file run without doing anything except clicking them.

What specific file QME 3.1 file is not running? 

My guess was that the installer in qme30_full_installer.zip was the problem.

Often with older software the installer is more picky about the version of Windows than the program it's installing.

I have a strong dislike of programs that insist they must be "installed" and avoid them as much as possible. 

 

These new weapon models are great! Not really a fan of the new g_rock (grenade item model) but oh well.

I'll start making new skins for the Mispack2 (rogue) weapons unless you've already started to. 

Folks at Quakeone already made alternative skins for both mission packs. I still want to make my own versions, eventually, but I haven't started yet.

Not really a fan of the new g_rock (grenade item model) but oh well.

I just didn't know what to do with the old design to make it appealing to me, so I started from scratch (not counting a little bit of Q3 for inspiration). 

I ran the installer in my '98 VM and it went through fine, then I ran the patch so now it says it's 3.1 preview 2. Am I allowed to post a link here? I zipped up the results and I can upload them somewhere if you're still interested Qmaster.

If I were to upload it, what would be a good file host that isn't likely to serve ads or dissappear in the near future. I noticed the http://www.quaketastic.com/ link at the top of Screenshots and Betas, would that be alright? 

 

here you go! 

7-Zip can often open the contents of some installers, if you right-click and go to "7-zip->Open archive...". 

Unfortunately the version of the installer I've found "Cannot be opened as an archive". Regardless, there's a link to a fully patched installation in the post above yours so i'm not sure we need to worry too much now. 

http://i.imgur.com/BhPq3BI.png 

The handle looks a bit out of place. That's all I have to say, I'm not a model or texture artist. 

 

Extremely newb question:

How do I add a custom (static) entity to a map?
I've made a model:
http://67.media.tumblr.com/5437614355495b387dea15a1ea6e3b18/tumblr_ofgk3urXGE1usc8qto1_1280.png

And I got an add-on for Blender which exports to .mdl (seemed to work).
However, I have no idea have to add a custom entity to a map editor.
I tried TrenchBroom, because it seemed the most intuitive, but although I could see a list of entities, I saw no option to add any.

Sorry for asking what is probably a dumb question,
Help is much appreciated. 

Quoth:

"classname" "mapobject_custom"
"model" "progs/yourmodel.mdl"
"spawnflags" "1" // Makes it static

https://www.quaddicted.com/webarchive/kell.quaddicted.com/quoth/quoth_tutorial.html#mapobject_custom 

Thanks for the reply Baker,

I'll try Quoth if I can't get it to work through TrenchBroom.

I found this TB addon, however:
http://leray.proboards.com/thread/3653/add-custom-models-trenchbroom-1

There's not much of an explanation, but the script format (in the def file) looks like this:

@PointClass base(Models) model(":progs/models@bits2@banner@tris.mdl") size(-16 -16 0, 16 16 52) = models@bits2@banner@tris : "" []

So, I thought I could try simply substituting the file path to that of my own.
Loading the def file in TB allows me to place an entity named after my file (just an empty cube), but loading up the map (in Quakespasm) I can't find any model.

(Also, what's up with the @'s in the file paths? Some python convention?) 

Tried adding a couple of entities from the normal ID1 def file (with 3D previews in TB and everything), but none of them would show in-game. 

You should probably ask map editor questions in the thread for that map editor.

I could tell you how to add a entity to a map, but knowing how to use your map editor of choice is something you have to bring to the party. 

Yeah, I wasn't sure this was the appropriate place to ask.

>I could tell you how to add a entity to a map
I'll try your way if you'd be willing to share?

I just want to see if I can have my model rendered in Quake, nothing more complex. 

If you want to do that and do it fast, use Pakscape to open quake\id1\pak0.pak and delete g_rock.mdl (make a copy of your pak)

Then put your model (renaming it) as quake\id1\progs\g_rock.mdl (make the progs folder).

Start Quake, load dm6 and go to where the grenade launcher would be.

That would be the fastest way to do what you want. 

In the future I may need to do this kind of stuff but I intend to map primarily for AD. 

Thanks a lot, Baker!
I'll try that!

@Mugwump
I was trying to edit the AD start.map in TB, without luck. I'm certain I'm just doing something remarkably stupid, though. 

I see the TB add-on you linked is for TB1. You're not using TB2? 

@mugwup see line #222 in the ad_v1_42_readme.txt 

 

line 582 might interest you too. 

Yeah, I was using TB2, but hoped that it wouldn't be all that different. The addon seems to work (at leats it adds entity boxes to the entity browser).

Haven't been able to find any other tutorial...

Which makes me wonder:
How did all you Quake mappers even figure these things out? Back in the day, it must have been an insane puzzle to figure out on your own, but even today there doesn't seem to be much in the way of documentation and tutorials on how to use the map tools online.
Perhaps my google-fu is just weak, but I'm quite impressed with you all. Especially if you made maps through 2D views(!).

Also,
@Baker
Found this in the AD readme:
"Mappers : The editor .def and .fgd files supplied with this MOD require
: the worldspawn entity to have "no_item_offset" set to 1"

Yeah, I suppose I should've just tried a vanilla Quake map. Thanks for pointing this out. 

If you connected to #Terrafusion on QuakeNet (IRC) I suspect that these things that take you hours to figure out would instead take minutes or seconds because it is real time chat and anyone there has either made 10 maps or played 200 of them.

#Terrafusion was always the IRC home of the mappers that live here. 

Dwere,

Just want to throw a thanks for your efforts. I really enjoyed the new weapon improvements you made! 

Thank you, and you're welcome. 

I just emailed spirit with an updated installed for QME so that it will install on more modern machines.

That was one frustrating 3 hour rabbit hole. 

Could it be that modern engines (win7) disturb older programms (qmle) to work properly?

IMHO now I understand a bit why my Abe'sOddWorld wouldn't play
on OS while it went fine on OSX, I blamed the program.

This after trying Wally, Texmex and QME with Win7 and WinXp,
older programs work best on what they were made for. 

So - I have the standard player.mdl, and a g_plasma.mdl, and I got into qme, and merge the g_plasma.mdl into player.mdl because I was to animate it on the quakeguy. The vertices get all fecked up, like so:

[url]http://i.imgur.com/oLYGSfN.png[/url]

[url]http://i.imgur.com/bJ54262.png[/url]

How do I fix this? What other ways of doing this are there? How did other people do it? 

Beat way to fix it by move your object ie. g_plasma.mdl upwards.
Then export your all the frames by export multiple frames to another file.
Start a new object with import the frame you rised the g_plasma gun.
You will get a new model with a better skin file.
Import all frames back to the new model file. 

I uploaded q2mdl29b_alsoq1.zip to quaktastic/tools.
It is Quake2 modeleditor, but Quake1 also.
A bit stiffy, but a good reference in between qmle.
It might be strange, but quark4.07 was one with the first modelstudio.

I use them three when working on Q1 models. 

English slang for an erection!! 

My last convertions of models to quake1.

ncc1701
hubble 

@madfox, can you give me a step by step example as I'm not fully understanding what you mean. Thank you 

You had merged your g_plasmagun into the player model.

I tried the same appearance as your bj54262.png, loading player.mdl to rockrun3 and merge another weapon in.
As result I get a player with the weapon through its head, but on the skinfile I get one weaponskin extra.
In your png I see the right plasmagun skin, but there is interference with the player skin.

I can't restate the effect you result, as mine show the player with the extra merged weaponskin aside.
Can you send me the file of the g_plasmagun,mdl? 

https://mega.nz/#!8Qlg0Lba!FioVUy4_w_1cS8bkjnM40OjJeBZTsIobaIl8aW5IpHM 

That was a bit of a hussle. I'm not exactly sure what happens, but for some reason the g_lavagun skin keeps interfering with the player skin.

I tried different placements of it in the merging file, but even from the corners it kept crunching the player's back.
For me I wouldn't mind, as it's just a small side of the gun. It takes more time to scale it and make it move accordingly the shotgun.(compare before delete).

I don't have an explanation for it, my weapons just load fully aside from the orginal.
Solution I found is load the model in the Quark4.07, clip the brushes in the skin view so you see vertex points light. Then slowly turn them back to left so they don't tresspass the ones of the player skin. Takes some skill

c0burnplayer 

@madfox, you're an absolute star. Thank you very much. 

You're welcome! 

https://drive.google.com/open?id=0B9DxOfPvG2G1RDdoY0wtTzU5RW8

Changes: new hand, improved lighting, skin pixelings. The last one cost me the most time for the least amount of visible change, as always.

Source files are included. Ignore the hammer, it's unfinished. The stock id1 axe wasn't updated with the hand mesh and rigging improvements I made when molesting the AD axe, so it's a little obsolete.

I had to unmangle the original shadaxe from what the MDL format did to it, then the model was animated from scratch, and then it was mangled again during exporting => the shape might not be exactly like it was.

Since the hand that I made takes more space on the skin, I had to cut the second side of the blade. I could make the skin bigger, but I wanted its size to be power of two, and preferably not very ridiculous. I wanted to reinclude the second half for the pickup model, but I'm too tired after doing cruel and unusual things to 7 subtly different versions of the first half.

http://i.imgur.com/xdBH3Az.png 

That looks amazing, I use all of your weapon mdl revamps so I am excited to check this out later! 

The hand still needs work, I think. It was supposed to be the main (or even the only) improvement, but got neglected in the end. 

Dwere,

I want to let you know your SSG model is my favorite. Love the small details done there.

And to Skiffy,

Your HD shambler is irreplaceable and a must have whenever I reinstall quake anywhere. I hope you are still continuing with the vore work but I lost track of any updates/cancellations. 

Which one? I made two sets - one stock-ish, one completely different (lever-action).

Regardless, thanks for the kind words. 

Needs to be made for all these cool models! 

The model with the subtle wooden details on the sides? At least I think it is wood!

Also that reminds me, I recall you talking about some animations or the like you use for Quake and shared them somewhere but I can't find where... 

This reminds me of the sock's updated SSG in AD (view model). Its forestock looks more like wood than the one on the original id model.

I like it, but it's not mine.

I made the 1.5 pickup model though, except the version that's present there is obsolete and I hate it.

Also that reminds me, I recall you talking about some animations or the like you use for Quake and shared them somewhere but I can't find where...

Not sure what those could be. Maybe someone else said it? 

Nope it's yours!

I just tested and compared with 1.5 and then adding your pak. I was mistaken, the brown "wood" is from the subtle brown reflection or what have you that the detailing on the sides gives (My favorite part)

But AD's is indeed wooden I do see that now.

-Hmm, I have no idea about my other question it was just an offering in a random thread...oh well! 

I created a folder using a static model.
Therefore, a space with an additional block, in which there are two entities with their own skin.
The exterior is an animated sky texture space.
When I compile the directory without lighting, so good.
When I using light, the two models are suddenly the animated sky colored texture, not their own skin.

How can I avoid this, or doing wrong? 

Never encountered this effect before with light.exe. 

Models take their light values from the surface directly below them. Even though a sky texture is always drawn at the same brightness, that doesn't give it a light level automatically. Replace the sky brush on the bottom of the map with a normal solid brush, add some lights until it is lit correctly and the models look OK, then place a thin sky brush on top of it to restore the appearance. 

I placed lights right under the info_static, but for some reason these only give a dim glow.
Covering the bottom brush seem to give the light a chance, but as it's such a large distance, I found my skill with the sky light in worldspan.

Thanks for the hint, Preach!

starlog 

I've been modelling quiet some time now for Quake1 models, but there's one thing that keeps on erratum.

After creating my model frames according their position, and adding the corresponding qc in game the model refuses to die.
The first hits relate with blood gibs, but after three shots the model just animates on, without dying.

model 

The error is in wocat_die, and it's something that the function is missing. Compare it line by line to shalrath_die and see what is missing in your function. 

forget statement, me donkey.