Posted by TheSchwartz on Mon Jan 3rd at 8:24am 2005
TheSchwartz
member
30 posts
33 snarkmarks
Registered: Dec 7th 2004
Location: Denmark

Occupation: Project Lead Process Improvement
Posted by Leperous on Mon Jan 3rd at 11:15am 2005
Leperous
member
3382 posts
788 snarkmarks
Registered: Aug 21st 2001
Location: UK
Occupation: Lazy student
Posted by Petrarch on Mon Jan 3rd at 1:45pm 2005
1. There are very few existing button models.
2. Not everyone wants the trouble of making their own.
3. Using a model for a button limits the size of it, whether it moves or not, the direction it moves in, and how far. Doing it the old way with brushes and animated textures does not.
I'm less than happy at the way that the work of a mapper has been significantly reduced and given over to modellers and suchlike.
Posted by Leperous on Mon Jan 3rd at 1:53pm 2005
There was some sarcasm in my message, but the point still stands- hopefully soon there'll be too many button models floating about for us to know what to do with ![]()
I don't know the texture specifics, but obviously you can use two func_wall_toggles, one with the 'on' and one with the 'off' texture on it, and cycle between them with a simple toggle output...
Leperous
member
3382 posts
788 snarkmarks
Registered: Aug 21st 2001
Location: UK
Occupation: Lazy student
Snarkpit v6.1.0 created this page in 0.0203 seconds.

