Doraz_ Posted July 28, 2021 Share Posted July 28, 2021 I think i just swapped saryn with mirage ... and then saryn again. i like this xD Link to comment Share on other sites More sharing options...
Doraz_ Posted July 28, 2021 Author Share Posted July 28, 2021 mmm ... maybe an address bug ??? or a runtime material that gets reused instead of being deleted? It would make sense ... the game ask for a material ( frame ) to be created .... the previous one has not being deleted or flagged dirty or WF equivalent, and gets re-used as it's still in memory xD Link to comment Share on other sites More sharing options...
Doraz_ Posted July 28, 2021 Author Share Posted July 28, 2021 And probably nobody cares, but this is exactly why I think having API to mix ahaders at runtime is pretty hekking cool. A problem of customizations are either them being limited in scope, as developers have to create assets beforehand in little time, or them being un-optimized and buggy. With the right operations, Warframe could have already countless potential designs, born of the mix&match of different texgures and materials, that require no new assets to create. In the case of this bug, no "NEON SKIN" required the devs to create it, bake it and all that nonsense. My knowledge only extends to mking an universal shader with as many modifiers and nodes as possible ... but i'm afraid that is hekking hell on performance and memory xD Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.