LOAD ON CALL or Not? Whats the best option?

[Decoamorim]

Hello guys,

I already looked for this in the documentation and forum. And thought that i understood. But i guess not.
Because all my enemy objects were set to LOAD_ON_CALL , and that made the app slower in the device. I removed the load_on_call attribute in all objects.
And the app is running really faster now.
So...someone can explain better the load_on_call config ? And when to use it?

cheers

[paobrasil]

Maybe I am wrong, but in past I read from Anders that this fuction dont works on iOS.....but maybe this have changed.

"This option saves memory, and accelerates loading time of big frames. If unchecked (default option), all the object's data are loaded at the beginning of the frame. For big objects on CD-ROM this can create a small delay when the frame appears.
If checked, and if the object is not created at the beginning of the frame, the object's data are not loaded at the beginning of the frame. They are only loaded when you create the object in the frame. "

[Yves]

I confirm the Load On Call option has no effect in the iOS runtime.

[Decoamorim]

Really? Thats odd... but i also unchecked the collision box: "use fine detection".

Does that have some effect on IOS? The app is faster, and those are the two changes done.

[paobrasil]

disable fine detection? very effective!!!

aways disable fine detection of all objects that you wont check for collision (like buttons, and so on). aways disable fine detection of objects that are boxes actives.....


Or even better....disable fine detection of ALL objects that you create on your game....then, enable just on objects that really need a smooth detection/collision.....this is what I aways do.

[Decoamorim]

Obrigado paobrasil!

Really makes a difference

[paobrasil]

Po to falando contigo em ingles....e vc é de floripa hahahahhaha