User Inputs and Outputs
page nero start smart free download cymbalta side effects samsung sgh z710 site fireplace used rolex cheap anniversary clocks ontario airport parking dog the bounty hunter olympic airlines kitchen curtain justin boots rv motorhome questionnaire muscular men 1955 chevy boat pontoon trailer used cheap ticket ringtones for nextel marlboro 2007 nissan altima adware spyware removal video paris hilton first national bank of pa adult film francesco biasia handbags edmonton alberta pneumonia symptoms amitriptyline holiday south africa phone directory blackplanet backgrounds vans shoes hi8 player credit card numbers burberry raincoat person search buy a used car tera patrick anal cheap international flights porn webcams chicco suzuki vitara videosex ringtones for rogers index bird tattoos orlando restaurants muscle pain motorola ringtone dell coupons music gifts for godparents sharon stone nude best bank cd rate gambling web site sexy men nokia unlocking softwear bank of america online florida cheap southwest airline tickets sylvan learning centers lcd review samsung tv cheap beads linen outlet vanities american girls wifeysworld com big black dicks buy zithromax spa pump reef sandal cell free phone prepaid ringtone fish hair care designer handbags houston plastic surgeon top ringtone software full movies free legal forms patio umbrella tours pokemon games jenna jameson nude home exercise equipment free ecards play shooting games online prom theme mattresses kathy van zeeland handbag sex pictures wholesale designer handbag free samsung ringtone gas powered scooter ti 89 graphing calculator honda prelude used how long does xanax stay in the system anniversary invitations sealy mattress last minute travel deal 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).