I'm guessing the problem is the actor is like a monster, so it's using walkmove/MOVETYPE_STEP to move instead of velocity. This makes it a lot harder to predict, as basically it can move different amounts each animation frame. Also, in standard engines the entity will literally jump position each time a new frame is called. In engines with motion interpolation, the model itself is interpolated smoothly between points, but I believe that the origin still moves in discrete steps.

Anyhow, I'll take a look at the doe ending.qc and see what can be done, and if you would upload your version I'll examine that too.

mwh, your comments are encouraging, although I had worried that the demo format had the same restrictions. I guess as long as the camera isn't trying to do a fixed position pan, and you keep the movement smooth with velocity code or updates tied to PlayerPreThink you can get something as smooth. Can't help you with the finale problem though, very odd stuff. We need an engine coder in here... 

I've uploaded my variant (progs + ending.qc) here: http://user.tninet.se/~xir870k/doe_bjp.7z . Thanks for looking at it. 

does anyone have a hard copy? Please mail it to me if you do! 

but I have a placeholder at
http://skynet.campus.luth.se/~chosen/bam/curvtutt/
in the mean time. 

I am looking for a decent, or at least different, Boss Monster for my non-base style QSP1 level.

I will need qc source, not just a model. Any suggestions? 

There is one I'm partial too that I have not seen used in a released map yet, the zombie master from Custents. 

in case you don't have the link --

http://www.fileplanet.com/dl.aspx?fatty/custents.zip 

Is it possible to create skill selector buttons like on coagstart in the Coagula contest without QuakeC?

I haven't had any luck having a button target a trigger_setskill that uses a targetname. 

Nevermind, apparently so! 

I'm trying to set up buttons to select a skill level (Easy, Normal, Hard, etc.) and a similar setup in cogstart.bsp functions without the progs.dat, so it seems like it should be possible to do without QuakeC, but it doesn't seem to work for me.

I setup a func_button, set the target name to "skilleasy" and a message of "Skill set to easy". I setup a trigger_setskill, set the skill level (message = {0,1,2,3}) and set the targetname to "skilleasy."

I push the button and it doesn't change the skill level (still is skill "1", the default).

I've checked everything 3 times, I've even dumped the .bsp source and compared to cogstart.bsp.

Is there a secret to this or something obvious I am missing? 

I decompiled cogstart and took a look at it in a map editor. That was hilarious!

Those buttons are merely psychological, they don't actually do anything meaningful (they don't select the skill), the trigger is the proximity. 

Thats what I was thinking. 

Thanks, it looks good and there's quite a lot more in there besides the monsters.

Anyone any other suggestions? 

Hi there :)

I have been playing around with the DarkPlaces engine, and I must say that I quite like it. I began working on a mini mod called SlaughterHouse, which all it really did was change the weapons and how they dealt damage (homing rockets, exploding nailgun bullets, sped up shotgun).

After completing that, I thought I'd start on something more adverturous: A Counter-Strike clone (or something similar). Now, I can add in new weapons, change the gameplay and thigns like that. But, I have no real clue when it comes to modelling for Quake/DP. I can model fairly well in 3ds Max 5/7/8 (and then export to 3ds to be imported into Blender, which supposedly I can use to make Q1 models), but I do not know how a model is supposed to be done for Quake/DP. Are there any resources that I should check out?

Also, this mod adds in a heap of new items and weapons. Rather than changing existing ones, I created some from scratch. I can map fairly well for Half-Life using WorldCraft, but I have never tried mapping for a Quake MOD. I can map okay for Vanilla Quake, using the Qoole editor, but I cannot work out how to get it to work with mods which add in new items/weapons. Can I do that in Qoole, or will I need to change editors? If so, what to?

Thanks heaps :)

-Girvo 

Do yourself a HUGE favour and download a copy of worldcraft 1.6 or valve hammer and use that for Quake 1 mapping, Qoole is the ugliest and worst editor on the planet :D

To add in a custom item/monster/gun whatever to worldcraft, just add any point entity you want to the map, then open the properties for it and you can just type in anything you want into the "classname" field, replacing the entity you created initially. Easy as pie! Then you can use the "smartedit" function to add in any custom key/value pairs you have coded for it.

Good luck 

I'm gonna shamelessly pimp my own work here, if you want a guide to modelling for Q1 then this is a start:
http://qexpo.quakedev.com/booth.php?id=32&page=79

This suggests a different route to making a Q1 model, using gmax and quark. At the time of writing, I didn't know that gmax had been discontinued. You can still download it, and with a bit of trouble get it registered, but the process is involved enough that it should go into the guide. Really I want to tidy the whole thing up with things like that, but it's a task for another day.

Anyhow, there's some useful information there, but if you're using 3ds max, you might as well stick with that. If you can export to md3 in gmax you certainly can with the full version of max, and then do the conversion in quark like in there. The plugin you want can be found at http://www.quake3bits.com/htm/tools_utilities.htm

As for the editor stuff, I'm sure everyone will say change from qoole. I started with qoole too, trust them when they say it'll cause you problems. 

If you're already using Worldcraft 3 for Half-Life, you might as well use Worldcraft 1.6 for Quake.

Does anyone have a download link for him? 

http://www.fileplanet.com/dl.aspx?worldcraft/wc16shar.exe

http://hosted.planetquake.gamespy.com/worldcraft/index2.shtm 

You can also use Worldcraft 3 (or Hammer) for quake editing. All you need to do is to get a fgd file for quake (for example from czg http://czg.leveldesign.org/q/Quake.fgd).
You can edit that fgd file to add any new entities I guess. 

I started using Qoole, as I have my entire editing kit (Quake included) running directly off a 128mb thumb drive :P

Worldcraft 1.6 looks perfect, so I am gonna go get that :)

Thanks for the modelling tutorial, its really helpful :) 

I want to place a killable model in a map, basicly you hit it until it fires a trigger. Unfortunately I have to do this without any coding - I'm running under Qouth. My first idea was to either export the model as geometry and import it to the map with a trigger + health value, (seem to remember an exporter capable of this) or else replace (rename) an existing model with the one I want (one I'm not using) and do the same. But these seem cumbersome methods to achieve the effect. I'm not using the fish enemy, which is an almost ideal candidate for model replacement, except as far as I remember fish die when not in water ;P

So basicly I'd like to know if there's a way to get a model to show up in a map - it doesn't need to do anything at all, not animations or anything (since I can reexport to remove animations if need be).

This is a preexperimentation question, so thanks for any feedback. 

I'm mapping with a quark65 a Quake1 map.
It has 194 ent, 151 lights, 1128 polyhedrons.
Use the latest compilers Txbsp1.12 Vis2.30 Light1.42
No warnings. Plays fine in Fitzquake.

I add some polyhedrons and it compiles fine again, but as soon as it starts Fitzquake I receive a Alloc_hunc failure.

I thought this only happened when one uses more than 620 ent?
What happened? 

Alloc Block : full 

This is caused by lightmaps. Ways to solve this:

1. Reduce total surface area of your level. Each square meter of wall/floor/ceiling/etc. needs lightmap space, so reducing surface area will reduce lightmap needs. (For example, if your map leaks and you have it inside a giant box, closing the leak with make a huge difference becuase the giant box can be deleted.)

2. Scale up textures on large surfaces. Lightmap usage is based on texture scale, so if the texture is scaled up on a surface, the polygons will use a smaller amount of lightmap. For example, if you have large rock walls, scaling up can help.

3. Usemore of the textures that don't need lightmaps. For example, sky doesn't need lightmaps, so if you have a room with a ceiling, changing the ceiling to be open sky will reduce the amount of lightmaps needed. 

i think, because of the relatively small size of the map, it could be you have an infinite brush...