Talk:Inputs and Outputs

This doesn't explain how outputs with values work. For example, the math_colorblend entity has an output OutColor that is described as:

OutColor <color255> Fired when the InValue input is received, 
with the remapped RGB color as the parameter.

How is such an output used? —Maven ^(talk) 15:00, 18 Sep 2005 (PDT)

Other examples: the TargetDir output of point_anglesensor and the AngularVelocity output of point_angularvelocitysensor. —Maven ^(talk) 15:16, 18 Sep 2005 (PDT)

Ah! A non-esoteric instance: the OutValue output of math_counter! And in that article is a brief explanation. I'll experiment and do a write-up in this article soon. —Maven ^(talk) 15:44, 18 Sep 2005 (PDT)

I'd like to see something on the special constants, like !player. I'm having trouble finding a list of these. --Spektre1 22:27, 18 Sep 2005 (PDT)

They can be found at targetname. But, yes, they should probably be here as well. —Maven ^(talk) 05:27, 19 Sep 2005 (PDT)

Writing

The writing of this article is really painful to read. A lot of it sounds like an essay trying to convince a company why they should invest in VALVe's superior input/output technology or something. This should focus more specifically on how to use inputs and outputs, or a separate article should be created. Thelonesoldier 17:21, 18 Feb 2007 (PST)

I agree it needs to be rewritten even after the touchups you've made. --Angry Beaver 17:55, 18 Feb 2007 (PST)

Disabled?

I'm a Hammer noob trying to follow the instructions in TF2/Team-Specific Doors. In the leftmost column of the Outputs tab there's a dot-with-arrow icon that is not explained in the article. In my case (unlike the screenshots in this article) the icon has a red line through it. The team-specific door I have created does not work properly either, and I suspect these two things are related. Can someone add info on this icon and its meaning? --TaviRider 13:06, 4 Sep 2008 (PDT)

It means that one or more of the entity's outputs are broken. The error itself will be highlighted in red. --TomEdwards 13:50, 4 Sep 2008 (PDT)

I didn't see any error in red. I just deleted all the components, followed the tutorial again, and this time it worked. Anyway, thanks for the info. --TaviRider 15:04, 4 Sep 2008 (PDT)

Examples

I removed the "setting up a trigger" section because it doesn't tell the reader anything new about using I/O. What it does do is provide a link to triggers, a task switched to my I/O entities section, and explain how to use ambient_generics, which is outside the article's remit - all while being packed full of dense, and for a beginner probably very confusing, instructions.

The problem is that the section deals more with wisdom than with knowledge: it's the kind of thing learnt best from experimenting, not following instructions. I think that a better solution is to explain the purpose of triggers and logic_auto/relay, then point the reader at env_sprite and ambient_generic, or othersuch simple entities, and let them play around as they see fit. This has the additional benefit of training people up in discovering inputs and outputs on VDC.

On the intro, saying that "the same output could also be used to trigger another entity's spawning input" could be read as meaning that certain inputs only work with certain outputs! Discussing the theory of I/O in one para and leaving all specific examples until the next is safer.

(Lastly, where did "connections" come from? I've never heard that before. Although it's technically wrong, everyone always talks about "adding outputs" instead.) --TomEdwards 14:10, 25 July 2009 (UTC)