User Inputs and Outputs

From Valve Developer Community
Revision as of 10:25, 26 November 2007 by LiaceLacel (talk | contribs)
Jump to navigation Jump to search

girls making out yahoo adult profiles cingular wireless phone cheap airline ticket europe amateur striptease flight schedules ann angel norweigan cruise line download movies pet monkeys federal job site picnic table empire earth download full version brylane home avast total gym acne cream ingredient target used car greensboro cheapest flights solid wood baby furniture clark shoes medical terminology amateur free sex video avodart find peoples email address inuyasha ringtones free interracial verizon free ringtones geritol vitamins his first gay sex free paris hilton porn futures broker pay day loans online free ringer downloads girl kissing ups shipping online naruto games carvedilol download mp3 online baccarat living trust hairy bush blue diamond muscle pain car ratings for insurance download win mx for free pill pergo hardwood funny baby picture kitchen cabinets bmw m5 lil kim shoe guaranteed approval bad credit loan celecoxib advantage digestive adult vibrator wedding shoes monstersofcock renault twingo adobe downloads carnival cruise dolce and gabbana liens bob and tom recipe for strawberry cheesecake personal checks apartment rentals oahu atlanta colleges celebrity videos artane discount books bag chloe edith cricket wireless download sex woman porn greek alphabet *3khcvst.html chinese astrology haka jewel quest sexy girls gerl verizon wireless pix place philippine airline ticket *3xtdrrw.html tony lama boot verison wirless prescription drug companies addicting game beauty supply sexy lingrie hayabusa suzuki celebrity porn event jobs trend micro i love lucy checks native american art lung cancer drugs medieval costumes stock The FireUser1-4 inputs and OnUser1-4 outputs are available on every entity that can receive Inputs and Outputs. This set of controls are specially linked to work together. Although they are not used very commonly, User inputs and outputs can be very powerful and make certain tasks far easier to accomplish.

The FireUserN input simply causes the corresponding OnUserN output on the same entity to fire. These are useful for forwarding messages through an entity where the desired target is known to the forwarding entity, but not to the firing entity.

For example, say you have three trains moving along the same set of path_tracks. Each train has a glowing env_sprite parented to it, and on one path_track you want to turn off the sprite on whatever train has just passed. The problem is that the path_track doesn't know which train has just passed, so you can't connect the "OnPass" output to the right one. So, you solve this by connecting the path_track's "OnPass" output to the !activator (the train) FireUser1 input, and then connect each train's OnUser1 input to turn off their parented sprite.

In the past, you could hack around this kind of thing by putting a trigger_multiple for every train on the path_track, set them to only trigger when the matching train touches them, and use the "StartTouch" output to turn off the sprite. Unfortunately, that method doesn't scale to large numbers of trains (as seen in the Citadel section of Half-Life 2).