Btw. if we want this to work as a new frob someday, ambientRimColor needs to be a stage keyword, not a global keyword, so we can put it in curly brackets with if ( parm11 > 0 ) clause. Also, I see that the shader made into official 2.07 beta, that's great
Posted 20 December 2018 - 04:33 PM
Oh no, a new frob highlight should never be implemented in the mtr file again. This whole thing was just an errorprone hack to begin with. Stuff like that has to be moved to game code, now that we can freely access the renderer.
That's not supposed to mean, that I am against making it a stage keyword, though.
- Springheel, Judith and duzenko like this
Posted 21 December 2018 - 11:51 AM
Having the back renderer to evaluate a couple of extra frob stages for every potentially frobable material in view is bad for performance.
It would be great to get rid of them at some point completely, along with the now unused ambient shader stage
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users