Talk:Material surface properties: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
Line 3: Line 3:


::just add an entry to surfaceproperties.txt. Sorted! [[User:MLSTRM|MLSTRM]] 14:45, 21 September 2009 (UTC)
::just add an entry to surfaceproperties.txt. Sorted! [[User:MLSTRM|MLSTRM]] 14:45, 21 September 2009 (UTC)
== Portal 2 custom textures ==
I was trying to put in custom textures in portal 2 and when I used a snow $surfaceprop hammer stopped working (portal 2 hammer doesn't have error reports; IT SHOULD; but I think that the code used to read $surfaceprop in portal 2 is different from the orange box so when you use an "invalid" $sufaceprop it stops working when loading the resources at startup, because as soon as I took out the texture in question of the materials folder it worked fine) so is there a way to import the "invalid" $surfaceprops from the orange box or should I compile a list of "valid" $surfaceprops and stick to it

Revision as of 21:04, 23 July 2011

Is it possible to add one's own $surfaceprop to the game? My coder and I have been looking but with little succes. We wanted to add some more types of metal to our mod. Any suggestions? --18px-ri.png-Jimius 12:12, 4 Jul 2005 (PDT)

just add an entry to surfaceproperties.txt. Sorted! MLSTRM 14:45, 21 September 2009 (UTC)

Portal 2 custom textures

I was trying to put in custom textures in portal 2 and when I used a snow $surfaceprop hammer stopped working (portal 2 hammer doesn't have error reports; IT SHOULD; but I think that the code used to read $surfaceprop in portal 2 is different from the orange box so when you use an "invalid" $sufaceprop it stops working when loading the resources at startup, because as soon as I took out the texture in question of the materials folder it worked fine) so is there a way to import the "invalid" $surfaceprops from the orange box or should I compile a list of "valid" $surfaceprops and stick to it