User Inputs and Outputs

rust remover in the end piano keys bucks county community college song love is all around youth saddles eureka tent spanking blog bpdaily starhoop titanic boobies po browning rifles jumbo loans how old is andy milonakis aviation accident information embarrassing teen moments jerk off websites susan ward nude shaving legs tree houses pc shooting trouble gsmls easy guitar tabs end of daylight savings telemarketing management non exec sea turtle armpit her angular force big booties dte shemale models masturbation techniques armored bighands club free sex video trailers logitech quickcam ordinary people seed sprout kinder xxx rami charity hot ass girls zzz so dimm ddr2 moms for anal sex pc tv cards reviews sweet child of mine pornagraphy keisha evans chet baker xxx lesbian porn tawny kitaen doctor sex hockey pants gorillas florida marlins male exam point blank spaghetti nicole wood monte carlo simulation verification sending street latinas i fucked my own daughter nude shannon elizabeth teen camera shower albuquerque chamber of commerce square meters conversion square feet website design brisbane wake me up when september ends a birthday wish for child premium audit thriller michael jackson in the end piano keys miki illinois senate district map jennifer anniston nude jak 3 climate change blouses fit lads infrared heating systems star wars episode 3 trailer vivid girls website hosting services skateboard shops women bend over gothic graphics candid crossed legs emma watson sex stories new album releases for 2005 arkansas commercial real estate spark plug wires seanna teen rochester post bulletin sa adelaide language centre rc hobby accessories naked and mature women extreme fucking teen crossdresser 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).