#9103 posted by Rick on 2009/10/05 04:06:32
For a clip brush to be part of a door it seems like the clip brush has to be surrounded by regular brushes, or maybe the door model has to be bounded by real brushes. Something like that. I had a door with two regular brushes at the ends of a long clip brush (looking from above) which pushed some scrags upward and it worked. I removed one of the real brushes and then it didn't work.
I'm Not Sure
#9104 posted by necros on 2009/10/05 06:47:13
but i believe that the clip brush must be within the mins/maxs bounding box of whatever bmodel.
Yeah
#9105 posted by ijed on 2009/10/05 15:19:38
Clip must be 'inside' the normal brush model or they won't collide.
BBOX explanation - the space is defined on the grid with three negative and three positive numbers. so -1 -1 -1, 1 1 1 gives you a 2sq cube.
All objects work like that, including triggers. So don't expect a L-shaped or diagonal trigger to have an Lshaped or diagonal area of effect.
The only trigger that can be triggered in standard quake (I think) is trigger_teleport - useful for the classic black box monster spawning or auto-porting the player when a condition is met (eg. kill an enemy).
Pre Lauching Elevator
#9106 posted by telefragger on 2009/10/06 07:42:30
I made an elevator in the corner of my map to bring you to the top of this little bunker, but it seems to always start moving upwards just before you get on... Is there a way to decrease the 'sensitivity' of it so i can get on first?
No.
#9107 posted by necros on 2009/10/06 09:54:42
func_plat activation trigger is based on mins/maxs of the bmodel in question. the only alternative is to use a func_door + trigger_multiple combo instead which would allow you to set a custom trigger size (or change the func_plat).
GTKRadiant
#9108 posted by JneeraZ on 2009/10/06 14:46:33
This has been covered before I'm sure, probably in this very thread, BUT...
I've downloaded GTKRadiant 1.5 for my Windows BootCamp partition and it's running fine ... except I don't understand where to put my WAD files so it can see them. Any hints? Their documentation is equal parts missing and abysmal.
#9109 posted by JneeraZ on 2009/10/06 16:07:15
OK, after reading way back in this thread I see I need to put WADs into Quake/ID1 but that seemed to be crashing GTKRadiant this morning when I tried that on a whim. I guess I'll try it again tonight. Weird.
Pre Launching Elevator
#9110 posted by Rick on 2009/10/06 17:30:42
It sounds like you're using a door (which is triggered as soon as its touched) instead of a plat (which triggers when you reach it's center).
Give the door a name and make a trigger_multiple to make it start moving. Put the trigger_multiple right on top of the door/plat and make it 32 units smaller in the X and Y directions that way the player will have to be completely on before they touch the trigger.
You'll probably want the delay before reset time on the trigger to be long enough for the door to complete it's travel up and down.
Why
#9111 posted by megaman on 2009/10/06 17:35:45
does the ai use the visible hull? bug or feature?
Not Sure
#9112 posted by ijed on 2009/10/06 17:36:55
But its the cause of fish and scrags sometimes going through walls, although the bugs are slightly different.
Pre Lauching Elevator
It was an odd shaped platform which seemed to be the issue... So I went with the basic square shaped one instead.
Like I Was Saying Before
#9114 posted by ijed on 2009/10/06 20:09:22
If your platform was a Z shape for example, then Quake would just draw a big square bounding box for the trigger. Slightly smaller than the Z, but not following the shape.
#9115 posted by JneeraZ on 2009/10/06 20:19:37
Sorry for the string of noob-ass questions, but I'd really like to be building something by tonight.
Do GTKRadiant users typically compile from a command line or do you go through the trouble of telling the editor where to find your compile tools? If you go through the trouble, how do you do it? Is it a hassle?
#9116 posted by necros on 2009/10/06 20:34:58
not gtkr, but i use sikkpin's qe3 which is essentially very similar.
i never use the menu system, although i believe it's the same thing. i have one of those gamer keyboards, and i have a macro to compile my map bound to one of the keys.
before i started using qe3 (and before this keyboard) i was using gtkr1.4 and i'd just keep a command prompt open in the background and what i wanted to compile, i'd just switch to it and use the previous command button which would launch a batch file.
Hmm
#9117 posted by nonentity on 2009/10/07 11:49:22
As necros said, just use batch files for compiling, the in editor menu gets a bit trippy when compiling for Q1.
Also, you might want to try using GTK1.4 and mapconv, there's a tutorial how somewhere on necros' site [ http://necros.planetquake.gamespy.com/gtkrq1.html ], the interface/creation flow was changed quite a lot in 1.5, for the worse in my (and a fair few others') opinion. You may prefer the 1.5 interface, but I'd suggest trying out both versions and making your own call...
#9118 posted by JneeraZ on 2009/10/07 13:56:17
I set up the in-editor menu. It's pretty easy, you just edit the XML file sitting in the q1.game folder. The one thing I can't figure out how to do is copy the BSP to the right directory and start the game up. So I need a command line open for that regardless...
Oh, and here's a story for the stupid. I set everything up last night and I made a small test room with a light. It compiled, loaded into the game, everything was grand. I then booted back into OSX to resize the partition I gave Windows because it was too small (FYI, 15GB is too small for Windows Vista and a Quake editor). While doing this, I misunderstood something and ended up killing the Windows partition entirely.
So ... I re-created it and reinstalled everything AGAIN. Only this tims I allocated 32GB. Let's hope that'll be enough.
Yeah
#9119 posted by necros on 2009/10/07 23:23:16
windows partitions need about 10gb (or more maybe, for vista?) just for the OS itself and then you're gonna want at least 2-4gb for your paging file.
you never really notice that when you're setting it up on a native windows machine, but when you're splitting between mac and windows, it becomes noticeable. mind you, mac isn't exactly a lightweight either; i spent a couple of days cleaning out all the useless software on my macbook, but i needed about 80gb for my macos partition to be able to work comfortably.
anyway, on the subject of gtkr, i personally hated the 1.5 version of the program. they changed fundamental UI stuffs in there which made it a lot slower to use (eg: operations that used to take 1 key press now would take 2), so even though 1.5 supports q1 natively, i found it harder to use than to just save a q3 .map and have a batch file that runs a converter first (aguirRe's, i believe, is the most up-to-date) and then compiles.
as for batch files, just make a bunch of them (for different compile levels) and put them on your start menu (or get rocketdock which is essentially the mac dock for windows) and you can just click the appropriate one and never have to touch a command prompt.
Lol
#9120 posted by RickyT33 on 2009/10/08 00:53:27
My c: is 80gb
Another Vote For 1.4 Here.
Yes, I'm gonna keep on beating that dead old horse.
Linux?
#9122 posted by Barney on 2009/10/10 06:24:19
I'm thinking about installing Quake and GtKRadiant on this new Linux box I've got.
Can anybody point me in the right direction?
Netradiant
#9123 posted by megaman on 2009/10/10 11:12:03
the gtkradiant based off 1.5 that the darkplaces/warsow? guys use.
FitzQuake 0.85 Question
#9124 posted by JneeraZ on 2009/10/10 14:33:10
Is there a way to make it so I can launch FitzQuake to check out my level without it resizing every window on my desktop? Or is this just a Window wart that I have to accept?
#9125 posted by JneeraZ on 2009/10/10 16:03:41
OK, I guess the answer is to run GTKRadiant in a non-maximized state. That seems to reduce the amount of swearing I need to do each time I test the map...
Willem:
#9126 posted by metlslime on 2009/10/11 01:04:28
if it's fitzquake 0.85, you can run it windowed but with a -height and -width equal to your desktop -- this will fill the screen completely but without your desktop actually switching modes, which might help.
#9127 posted by JneeraZ on 2009/10/11 01:24:47
Ahh. that's something I hadn't thought of. OK, will try, thanks!
|