Printable View
I am using 16x16 tiles for my game, so the number of backdrop objects are quite numerous. I've noticed recently the frame rate dropping a bit at many points. It took me a long time to figure it out, but when I started removing a couple of backdrops from the frame, the frame rate returned to normal.
I'm wondering if it was wise of me to use such small tiles? Is there anyway I can work around this issue?
I'm using MMF2 Standard R249 HWA.
Actually, many small backdrops is better than large ones. Try updating to the newest build.
That didn't help at all unfortunately.
Try the Background Images object?
Background Images does not seem to be working correctly. That or I'm using it very wrong.
It appears blank no matter what I do, but the collisions still work properly.
background images will do exactly what you want.
I am at a loss. No matter what I do, I can not get it to work properly under HWA. I can use it on Standard MMF2, but that pretty breaks many events that use HWA. Even then the FPS dropped even further with that many Background images.
You should use 32x32 backdrops instead, if possible, that will divide your number of objects by 4.Quote:
I'm wondering if it was wise of me to use such small tiles?
Why don't you use the build 251? I hope that at least you use the latest version of the build 249 because there were numerous beta versions and the first beta versions were slower and had some bugs. You can download the build 251 from the HWA forum.Quote:
I'm using MMF2 Standard R249 HWA.
Why does that matter though, if they're backdrops? If MMF2 uses the same image cache for identical objects, then wouldn't having more smaller objects be more efficient?Quote:
Originally Posted by Yves
As Jacob suggested earlier, I've already updated to 251. It didn't change anything as far as I can tell.Quote:
Originally Posted by Yves
It depends. More objects = more CPU time for scanning the objects, testing their position, adding them to the display list, etc.Quote:
Why does that matter though, if they're backdrops? If MMF2 uses the same image cache for identical objects, then wouldn't having more smaller objects be more efficient?
Oh, Background Images isnt HWA compatible.Quote:
Originally Posted by GameDragon
Ah I see. So does anyone have anymore solutions?
Disabling "Background collisions out of window" makes a huge difference, but of course this creates issues for moving objects.
Could you also disable the moving objects?
Do you mean through runtime options or events?
Actually, messing with the runtime for a couple of objects helped my issue quite a bit. Frame rate still isn't where it was before, but it's defintely an improvement. I'll keep playing around.
Disabling background collisions seems to be my only choice atm, but I can't figure out why it breaks the "paste into background" action. Anyone know why that is?
Try "add backdrop" and see what happens regarding that.
Marv
No difference as far as I can tell unfortunately.
Hopefully this is a good example of one of the problem I'm having. I've tried recreating the problem in a new application but it just wouldn't happen.
This is what I get with "background collisions out of window" on:
http://i.imgur.com/hLpxV.gif
And when it's off:
http://i.imgur.com/eEhry.gif