 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
This mdl I made myself, because the one in the deathmatch maker had a rather plump way of falling down.
Made no sense for such a big object. I find it strange if I see it in Qml or Quark it has a right bounce box, but if I shoot it at the top it won't get hurt.(?) The box you see in quark/qml is the box that bounds the size of the model. It's used by the engine to determine when the model is drawn, but nothing else. The hitbox is determined by the QC, specifically this line:
setsize (self,'-32 -32 -24','32 32 64'); Adjusting these values will give you a larger or smaller hitbox as you require. The first vector gives the coordinate of the lower left part of the box relative to it's origin. The second vector is the upper right coordinate, so it defines a cuboid hitbox. Making it see from a different point of view may be a little more complicated to fix, I'll try and post about that later. preach, I wondered about that quiete a time.
To make it launch from that height was already a fix, it tended to start shooting in angles up and below the player. Knowing how poorly the q1 engine and compiler generally handles slanted stuff, how insane would this be:
I want to design a map that's made of concentric sections surrounding a circular core. Every area of the map would have a gentle (or, near the center, not so gentle) curve to it. All lines would either be radial or circumferential. Essentially the entire map would be designed for polar coordinates, but imposed on a square grid. Insane? Mad? Masochism? You mean like this?
http://www.student.vu.nl/h.e.beck/girl8.gif Yes, the compiler handles stuff like this fine. like I said, you're out of your mind. :) does that even come close to the 8 grid?
handles stuff off the grid afaik. For SM32 I had to rebuild Gibbie's bit because it was on a floating point grid >:(
Radiant handles stuff down to 0.25 I think, and last time I used it you could build I think the plan to make that in Quake is masochism. I built about half of my wolfenstein map at 45 degrees when there wasn't much need for it. It wasn't particularly difficult, just time consuming and annoying to build. Having said that, gibbie's map looks like it is generally at more challenging angles. Gibbie: How about an editor xz view? I want to see how the ceilings were built. Shady xz:
http://www.student.vu.nl/h.e.beck/shadyxz.gif Girl8 xz: http://www.student.vu.nl/h.e.beck/girl8xz.gif In gtkradiant 1.5 you have to turn off "Snap planes to grid" or everything goes wrong. The smallest grid for both maps is 0.125. That is also the smallest grid you can set in gtkradiant. However if your brushes are not on the smallest grid (eg because of clipper usage) i think it will still save them properly. Anyways, most of the time i don't mess on such small grids. I mostly just use prefabs from a curvey thing of concentric brushes i once made, kinda like: http://www.student.vu.nl/h.e.beck/curve.gif This also has pre-aligned textures :) about filling a girl with phalluses?
I really hate during a DP when they rub your weiner up against another guy's junk while they are giving oral, but other than that, nothing! As far as I can tell, the windfly.wav is only used by the trigger_push. Therefore if you are doing a mod you could get away with supplying ambience/windfly.wav in your mod directory where you have a copy of null.wav (from the sound/misc folder in pak0) and renamed windfly.wav. That's a hack.
If you play with Qc it's straightforward to create a flag for noise or no noise. But Preach will probably come up with some wizard way of doing it :) The function that causes the push of the trigger also specifically plays ambience/windfly.wav - unlike doors which play whatever wav file is in self.noise1 for instance. So there's no possibility that the sound could be changed to null.wav by entity field editing. The only possible line of attack would be to make sure that the player's
Are there extent AI mods that would give monsters (I'm thinking an enemy human-type thing) the ability and logic to duck-and-cover and work as teams and stuff like that?
Do you mean 45 degrees down, for example? Then no, AFAIK. Otherwise, yes.
I want two shooters mounted on the ceiling firing in an "X" pattern. Both downward and 45 degrees inward.
Nothing can be easy :-( anyway, straight downward will do. I figured out how to do that at least. Diagonal shooters are easy to do. Info_notnull with these fields
use spikeshooter_use targetname blah wait -1 spawnflags as for desired spikeshooter movedir vec Where vec is a vector in the direction you want the spikes to fire. The velocity the spikes are fired at is 500*vec, so to match standard quake behaviour this should be a vector of unit length. Of course, the advantage of this method is you can actually control how fast the spike fires by varying vec - I hadn't thought of that before. This sets up a triggered spikeshooter, if you want a constantly firing one the setup is a little different: think shooter_think wait n nextthink 3 spawnflags as for desired spikeshooter movedir vec Be warned you need something else in the level to precache the required entities, like a regular shooter of the required type. inertia: AI_Cafe is a good place to start looking, there's certainly an example of making enforcers duck there http://minion.planetquake.gamespy.com/index3.html Working in teams is a bit more vague though, as the quake AI atttacks are basically relentless and crude. There's only so much teamwork you can put into constantly spamming grenades until you die. If you had something more specific in mind, like say navigating more sensibly in packs rather than the current all rush straight at the player and collide, then maybe... I want to have really intelligent packs of enemies, so that the whole "assault a base" thing could be done in a more tactical style.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |