News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
Yep 
you can stack multiple lights, just be aware that they will both add together in the central core. 
Thanks 
There seems to be also different kind of light entities.. globe, light, marsh, fluoro.. best way to see results, might be just trying each of them how they look. Is it fine to try out multiple types, or are there limitation or error from using too many types and so on? 
 
I guess those are almost the same as normal Light, light seems to act same way.. maybe those has different attributes or something then.. globe seems to have a sprite ball or something, and marsh has bubbles effect. 
Light Entities 
The various light entities mentioned above are all just the same as a regular light, except that they also have something else attached to them, like a model, particle effect or sprite. You won't be able to achieve any different visual effects in regards to color or attenuation/dynamic properties with them. 
 
Is there a way to get multiple sky textures into a certain map? I want to use a regular sky texture once but also have some void bits. So far I'm just using a non-sky black texture for the void, but it doesn't absorb shots like a sky texture does.

I do know a partial solution for Quoth only: a trigger_void brush seems to absorb projectiles, but does *not* absorb shotgun blasts for some reason. 
 
Something did just occur to me: just put black func_illusionaries in front of the actual edge brushes. Bullets would disappear through them.

Carry on (though it wouldn't hurt to hear other ideas!). 
 
As far as I know, it's not possible for most (all?) quake engines to load multiple skyboxes/textures at the same time; which one is used will be determined by whichever was defined last. 
 
There might possibly be some trickery (QC code or hack) to get the sky to change, but in standard Quake you can only have one.

To get an all black sky just use TexMex to add a new all black sky to your texture wad. It has to be 256x128 pixels and the name has to start with sky 
 
Quoth allows you to change the skybox through trigger_command. In most cases this is unfeasible, because skyboxes are larger files and can take a couple seconds to load, which would break immersion. However, the void skybox included with Quoth is tiny (it's literally six 16x16 images), and loading it through trigger_command is instant and seamless.

You can also use trigger_command to switch back to the regular sky texture by passing this command:

sky "" 
Cool 
I did not know Quoth could do this...

You could go through a sky sight blocking tunnel or elevator to mask a sky change. I know that's a trick with changing fog for AD at least. Damn, that's a pretty nifty feature! 
Multiple Skyboxes 
I construckted large spheres to turn as static entity. They're a bit wobbling, but create an option for more than one skybox
 
you could make them rotate using the same model flag that rotates weapons, this way there is no wobble. 
Didn't Think Of That, 
but I suspect the speed will be too high, concerning the weapon rotate.
I don't know of a way to slow it down.

The mdl tree goes to 240 frames, almost the maximum.
Slowing down the rotation with
{self.nextthink = time + 0.99;};
didn't haver the desired effeckt, only the decimal work, not the 0.01.
I could get no better result available than the youtube version. 
Rotate Flag 
Is there a method for slowing down the flag that rotates weapons, or is it hard coded? 
Get In Here Preach. 
I tried ages to get something that works, be best I could do was change the initial angle.

But really, we all know who the person is to ask. 
Be = The 
apparently 
Allah Djin 
I think it is hard coded, otherwise another dude had come up earlier with the idea. 
Anybody Know How To Make Infinite Telefrags? 
I'm trying to make a mockup teleporter appear as if players are continually porting though it and being telefragged. I'm having some trouble with some bits.

I can use an info_(not)null to execute a PlayerDie command, which gibs when the entity has less than -40 health. Which is fine, but doesn't reset it's initial coordinates, the second triggering occurs where the head landed. At the moment I've boxed it in with skip brushes to keep it contained. I could kill target it, but I'd like the entity to disappear and respawn at the origin that it was placed.

Is there a way to execute two functions on a single entity? SUB_regen looks promising, but doesn't appear to work as a "think" value, unless I'm doing something wrong. SUB_Remove seems to work (or it just breaks it) when it is set to the think value, but it doesn't retrigger. I assume that this does the same as killtarget.

I'm also using the spawn_tfog function, to give the teleporter effect, but this only spawns at coords 0,0,0.

Any ideas? 
Multiple Functions 
There are several "slots" that you can use for a function on a hacked entity, but each one runs for a different reason, so it can be tricky. Quick summary of the main ones:

use: Runs when the entity is used
think: Runs when the entity's nextthink time is reached, in general only useful for a one off activation
th_die: Runs when the entity's health is reduced to zero
th_pain: Runs when the entity's health drops, but doesn't hit zero
classname: Runs on the first frame of the game
touch: Runs when another entity collides with the entity in question
think1: Runs when the entity runs SUB_CalcMoveDone

Complicated hacks often involve different functions in two or three slots, and finding a way to get all the functions you need is a balancing act.

Luckily today we can exploit the weirdest one on the list, think1. Put PlayerDie in think1, set use to SUB_CalcMoveDone, and set finaldest to the coordinates that you want the gibs to spawn from.

How does it work? SUB_CalcMoveDone is a function which does three things, any of which might be useful, and then lets you run another function. The three things are setting the origin of the entity, setting the velocity of the entity to zero, and setting its nextthink time to -1. Today, the first one is useful and the last two are harmless, so we get away with it. 
Thanks Man 
 
Interested 
I am interested in use the lava shambler of "Source of evil" for my project, I need permission of author? 
#16910 
@madfox 
The rotation speed for EF_ROTATE appears to be hardcoded in the engine :( 
So 
it stays allahdjin. 
 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2025 John Fitzgibbons. All posts are copyright their respective authors.