amorgan Posted January 16, 2015 Share Posted January 16, 2015 I'm not sure if it is supposed to work this way, but if I assign a procedural texture to something and set the mesh.isVisible to false, procedural texture seems to still be processed and use up resources. This happens also when it is not in the camera view. Using v2.0 Edit: Should specify this is specifically with the fireProcedural. The only other one I've used is marbleProcedural and it does not appear to happen on that one, I would imagine because it is static. Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted January 17, 2015 Share Posted January 17, 2015 Yes they are processed on every frame. You can stop processing a procedural texture by setting texture.refreshRate = 0 Quote Link to comment Share on other sites More sharing options...
amorgan Posted January 17, 2015 Author Share Posted January 17, 2015 I assume it's not easy to correlate the mesh's visibility to whether or not a procedural texture should be processed? Or in other words, when a mesh is hidden, the procedural textures do not get processed. Thanks for the info I will start using this. Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted January 17, 2015 Share Posted January 17, 2015 It is even more difficult than that because a texture can be used by many materials on many objects Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.