Szico VII

Sponsers?

Well, I meant that I would need to tie the entity to only 1 brush of the elevator and not all of them. 

No it doesn't - the connector line will go to a specific brush but you'll notice that actually its targeting the entity, not the actual brush. (the "targetname") of the entity is targeted by the "target" of the trigger_multiple.

As for realistic elevators with opening doors, can be done with scripting - examples below:

http://jkhub.org/files/file/210-the-matrix-unleashed-submetro/

http://jkhub.org/files/file/1337-the-matrix-unleashed-lobby/

Yes, You can also do right click>ungroup entity to return something to worldspawn or right click>add to entity to add new brushes to a pre-existing entity. You just select the entity first, then the new brushes if you're doing that...I think. (might be the other way around)

Arent there just tickboxes for the various spawnflags on 1.5.0? Much easier than manually figuring out the spawnflag value...

In which case all you need is a trigger multiple at each end which targets the func_door. Easy peasy! Give the triggers a wait time of approximately how long it takes the lift to move from top to bottom (as determined by the speed you give it) so people arent able to make it spaz out.

Just set a "wait" key for the number of seconds you want it to stay in the open position if you dont want it toggled at each end manually.

The best way of managing this (in my opinion) is to make a func_door instead of a func_plat.

You can then have this door be triggered by a trigger at the top and bottom of the shaft. You can use direction Up and a lip value (of positive or negative, depending on whether it starts in up or down position) to determine the amount it moves. You can also specify a soundset for making noises if you like.

Oh right, yeah, system/ladder doesnt do anything in JA, never has for me anyway.

How does clip make a ladder that can be climbed?

Theoretically yes, but would have to be split into smaller md3 as theres a max vertex count of ?1000 per model

So, to confirm...ladders work in JK3? Thats news to me

Ladders work in jk3?

Fit is working as it should - you just need to rotate it 90 degrees by pressing the rotate left or right button twice (when its set at 45 step) to make it go around the curve of the patch. Set will allow you to do things like 2x3, 2x4, 1x2 e.t.c as fit is auto 1x1

If you want them going straight (in relation to the walls) then cap, as you already saw, works for that.

As for save and compile issues, id be tempted to swap to radiant 1.6.4 (see downloads) or use a q3map2 frontend like q3map2tools (also on the download section)

NB: The horizontal and vertical stretch arrows will increase/decrease the texture size from whatever you have set it to using fit/set/cap e.t.c

You have to actually select the patch, not try and select a single surface like you would a brush

Some images would probably be helpful at this point. Did you do SHift +S and then hit "Fit" or try set and you can do like 2x1 or 3x1 instead of fit (1x1)

For simple decals just use decals

Your best bet really is to fade the two textures together using alpha mods, because this eliminates need for an alpha channel and you can have your lightmaps.

http://www.simonoc.com/pages/articles/terrain1_2.htm

http://jkhub.org/tutorials/article/91-creating-curved-corner-cylinders/page-3?

There you go, then you just need to "Fit" your texture to the patch and it will bend it to fit the patch. Much easier than making a round texture, especially as radiant round curves aren't actually perfectly round so never match up with a texture that is.

Hah, I dunno. For me part of the fun is trying to get it to do shit that it doesn't make easy for you

Well, theres a lot of features of newer games and engines that obviously are fantastically superior to JA

I think its addflagged f (for function)

Bots will auto press useable things when they go near them.

 

 

j - The bot will jump while trying to get to this waypoint.
d - The bot will crouch while trying to get to this waypoint.
c - A camping/sniping point, the bot will often stand here if it has camping properties.
x - Same as 'c', except the bot will crouch while camping.
f - Wait for a func brush underneath this point before moving onto it. This is useful for elevators, moving platforms, and other such items so that the bot will wait until the object is under the point before advancing.
x - This creates a one-way forward point. The bot will travel past this point, but when reversing on the trail, once he reaches it he will turn back and go forward again. This is a good last resort if you want the bot to jump off a tall ledge he can't get back up. However, use these points sparingly, as they make the bot much less efficient in getting places.
y - This creates a one-way backward point. Same principle as the above, except the bot will only pass this point when following a trail in reverse order (5, 4, 3, etc).
n - The bot will not perform visibility checks when moving to this point. Should also be used sparingly, as the bot can easily get stuck when moving to these if something prevents it from getting there.
m - Sort of reversed from 'f'. The bot will only move here if there is NOT a func brush underneath this point.

http://www.simonoc.com/pages/articles/terrain2_1.htm

Was going to make it into a cod zombies style thing, but by all means, SP it up..

If moonbase is done, can add that in...Got some annual leave in November...might be possible

Perhaps @ might consider making it into a site tutorial for you?