momentary_rot_button (Half-Life) Last edited 16 years ago2008-06-11 08:13:47 UTC

You are viewing an older revision of this wiki page. The current revision may be more detailed and up-to-date. Click here to see the current revision of this page.

This article was converted from a previous version of TWHL and may need to be reviewed

The formatting may be incorrect due to differences in the WikiCode processing engine, it needs to be revised and reformatted
Some information may be out of date
After the article is re-formatted and updated, remove this notice and the Review Required category.
Some older articles are no longer useful, or they duplicate information from other pages. In this case, delete the page after merging any relevant information into other pages. Contact an admin to delete a page.

Brush Entity

The momentary_rot_button was designed to control the momentary_door, or, thanks to the Door Hack, another momentary_rot_button. The door (or door-hack button) moves relative to the posistion of the momentary_rot_button controlling it. i.e., if the player lets go of the button, the door begins to close.

Attributes

Name (targetname) - Property used to identify entities.
Pitch Yaw Roll (angles) - Sets the pitch (up / down), yaw (left / right) and roll (bank) respectively. The compass in WorldCraft / Hammer corresponds to Yaw. The settings are not always (or not all) used.
Render FX (renderfx) - Gives objects special render effects. Think of it as modifying whatever the Render Mode puts out. The options are as follows:

[list]
[li]0 = Normal

1 = Slow Pulse
2 = Fast Pulse
3 = Slow Wide Pulse
4 = Fast Wide Pulse
5 = Slow Fade Away
6 = Fast Fade Away
7 = Slow Become Solid
8 = Fast Become Solid
9 = Slow Strobe
10 = Fast Strobe
11 = Faster Strobe
12 = Slow Flicker
13 = Fast Flicker
14 = Constant Glow
15 = Distort
16 = Hologram (Distort and Fade)[/li]

[li]Render Mode (rendermode) - Controls the type of rendering that is used for an object. Options are:

0 = Normal
1 = Color
2 = Texture
3 = Glow
4 = Solid
5 = Additive[/li]

[li]Master (master) - The name of a multisource (or game_team_master) entity. A master must usually be active in order for the entity to work. Thus they act almost like an on/off switch, in their simplest form, and like an AND gate in the case of the multisource.[/li]
[li]Targeted Object (target) - Normally, the momentary_door you want to control.[/li]
[li]FX Amount (renderamt)[/li]
[li]FX Color (rendercolor)[/li]
[li]ZHLT Lightflags (zhlt_lightflags)[/li]
[li]Light Origin Target (light_origin)[/li]
[li]Speed (speed) - Speed the button will turn.[/li]
[li]Sounds (sounds) - sounds values 
<TL>0 = None 
1 = Big zap & Warmup 
2 = Access Denied 
3 = Access Granted 
4 = Quick Combolock 
5 = Power Deadbolt 1 
6 = Power Deadbolt 2<TC>
7 = Plunger 
8 = Small zap 
9 = Keycard Sound 
21 = Squeaky 
22 = Squeaky Pneumatic 
23 = Ratchet Groan 
24 = Clean Ratchet 
25 = Gas Clunk</TL>[/li]
[li]Distance(deg) (distance) - Distance in degrees the button will rotate.[/li]
[li]Auto-return speed (returnspeed) - Speed at which the button will return to its starting position after being used.[/li]
[li]Minimum Light (_minlight)[/li]
[/list]

Flags

Door Hack (1) - With this flag enabled, multiple momentary_rot_buttons can have the same Target value, and they will all move when one is used.
Not useable (2) - Button must be triggered to work.
Auto return (16) - Button returns to its starting position automatically.
X axis (64) - If enabled, the rotation will be on the X axis.
Y axis (128) - If enabled, the rotation will be on the Y axis.

Inputs

Outputs

Notes

If neither of the axis flags is enabled, rotation will default to the Z axis.

An origin brush needs to be part of the entity to specify its axis of rotation.

This entity is pretty similar to the func_rot_button.

1 Comment

kimilil

Commented 8 months ago2024-03-28 09:56:50 UTC Comment #106092

Findings:

Door hack flag makes the entity un-use-able but solid (default is useable but not solid)
Not useable flag has no effect [not implemented?]
[bug] the entity only works well with positive distance (clockwise opening). Negative distance makes the internal value "start open". The linked momentary_door will always be opening when the momentary_rot_button moves clockwise and vice versa.
- solution: have all linked momentary_rot_buttons have positive distance, and rotate the entity's yaw 180 degrees to make it spin counterclockwise (and now lighting needs to be taken to consideration)
[bug] [Related with negative distance also,] if there are 2 or more linked momentary_rot_buttons and the other has different signed distance then the other button will keep spinning past the end (and the internal ratio value would go past the 0 ≥ x ≥ 1 range)
- solution: same as above
If 2 or more linked momentary_rot_buttons have different distance/speed the one being USEd will dictate the speed and distance of the others. Then when it reaches the full distance all the others will snap to their fully opened/closed positions.
As per RUST: Creating Proximity Doors triggering the momentary_rot_button every 0.1s does move it at the prescribed speed, but if "auto return" is not set it'd just continually ping-pong between opening and closing.

[2024-06-05]
This is common knowledge amongst pro mappers but the momentary_* setup is used on Uplink and Blue Shift for the dialing-in sequences through an off-the-playable-area setup where the momentary_doors push a func_pushable through several trigger_multiples that have "pushables" flag set. One of them is the "correct, dialed in" position, the others unset it.

One very basic application for this that I can think of is replicating HL2 Route Kanal sliding gate setup locking at its open position by having a trigger_once at the very end of the momentary_door, and when the func_pushable touches it, kills the momentary_* entities and replaces them with func_wall_toggles of the setup frozen at their final positions.

You must log in to post a comment. You can login or register a new account.