Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

Bug Reports / Memory Leak with Clone Object and Set Bump Mapping

Author
Message
Wizard007
1
Years of Service
User Offline
Joined: 21st Oct 2015
Location: Lisbon
Posted: 27th Oct 2015 01:37 Edited at: 27th Oct 2015 13:39
I'm experiencing a memory leak with the use of Clone Object and Set Bump Mapping.

+ Code Snippet

Any idea why this occur? And solutions?
WickedX
8
Years of Service
User Offline
Joined: 8th Feb 2009
Location: A Mile High
Posted: 28th Oct 2015 05:54
You need to texture the source object and set bump mapping on. Then you will not need to do this for each cloned object. Try this.

+ Code Snippet
Wizard007
1
Years of Service
User Offline
Joined: 21st Oct 2015
Location: Lisbon
Posted: 29th Oct 2015 01:45
Sorry, I forgot to mention I want to texture the objects with personalized textures for each one.

A workaround solution is to use Load Object for each object instead of use Clone Object because of the memory leak.
WickedX
8
Years of Service
User Offline
Joined: 8th Feb 2009
Location: A Mile High
Posted: 29th Oct 2015 05:44
Quote: "A workaround solution is to use Load Object for each object instead of use Clone Object because of the memory leak."


That will still leak memory. Notice in my snippet, I am using Clone Object with no leak. This BUG is caused by deleting an object that has a shader applied. Some memory is not released.

Login to post a reply

Server time is: 2017-08-24 09:42:19
Your offset time is: 2017-08-24 09:42:19