GLBasic forum

Main forum => GLBasic - en => Topic started by: bigsofty on 2015-Mar-29

Title: X_OBJFREEEXTRA()
Post by: bigsofty on 2015-Mar-29
Anyone used this command, there does not seem to a reference in the manual to it?
Title: Re: X_OBJFREEEXTRA()
Post by: mentalthink on 2015-Mar-29
It's the first time I see this command, but seems something to free memory of a 3D obj.

Really I don't know about the existence of this command...
Title: Re: X_OBJFREEEXTRA()
Post by: MrTAToad on 2015-Mar-30
No, I didn't know it existed either - haven't looked through the command list for a while though...
Title: Re: X_OBJFREEEXTRA()
Post by: Kitty Hello on 2015-Mar-30
It removes internal memory that was only used for loading/writing.

Gesendet von meinem GT-N7100 mit Tapatalk

Title: Re: X_OBJFREEEXTRA()
Post by: kanonet on 2015-Mar-31
Sounds like we should always use it after loading an object? Or does it automatically get called?
Title: Re: X_OBJFREEEXTRA()
Post by: Kitty Hello on 2015-Aug-14
It also removes temp data used for collisions. Ao if you call x_coll.. it takes longer to rebuild that data.
Title: Re: X_OBJFREEEXTRA()
Post by: Hemlos on 2015-Aug-15
Let me get this right G...

It releases all memory for some ID.
Thats the whole purpose?

How is collision data significant other than completely freeing memory?
Title: Re: X_OBJFREEEXTRA()
Post by: kanonet on 2015-Aug-15
Quote from: Kitty Hello on 2015-Aug-14
It also removes temp data used for collisions. Ao if you call x_coll.. it takes longer to rebuild that data.
So is it advised to call it after loading an object? How many space got allocated on loading an object that is never needed again? And why does it not get deallocated automatically when the loading function goes out of scope?
Title: Re: X_OBJFREEEXTRA()
Post by: Kitty Hello on 2015-Aug-15
I'd not call it. But if you're low on mem and need not to save/collision/X_get... you may.