Monster Racer Rush
Select between 5 monster racers, upgrade your monster skill and win the competition!
4.18 / 5.00 3,534 ViewsBuild and Base
Build most powerful forces, unleash hordes of monster and control your soldiers!
3.80 / 5.00 4,200 ViewsI've built a game using AS3, and I've heavily optimized it. However, although it runs smooth as butter on most Windows machines, it slows to a crawl on a Mac. After searching for hours as to "why", the only answer I've got is "because Macs HATE Flash."
My question is, does anyone know of any methods (or links TO methods) of ways to optimize a Flash game specifically for Macs? Methods that one could use to make it run better using Mac OSX? This is very frustrating, I've Googled for AS3 optimization on Mac and haven't found anything. Any help?
Have you tested it on more than one Mac, because it might just be that one? I've never heard about Flash lagging on Macs before...
At 1/22/11 06:14 AM, Kirk-Cocaine wrote: Have you tested it on more than one Mac, because it might just be that one? I've never heard about Flash lagging on Macs before...
Anybody want to test this on a Mac?
http://priorgame.com/
Also, in Googling I found a lot of people complaining that their Macs run Flash slowly. Don't get me wrong though - I HOPE it's just the one machine ;)
At 1/22/11 06:32 AM, chronicADRENLIN wrote: Anybody want to test this on a Mac?
Doesn't lag on my macbook at all. Pretty fun game.
Smooth as silk for my Macbook Pro too. I've found it's usually alpha fades which macs dont like.
It has a memory leak. Would crawl as soon as it reaches the RAM capacity.
At 1/22/11 10:10 AM, GustTheASGuy wrote: It has a memory leak. Would crawl as soon as it reaches the RAM capacity.
Gust is right, it just ate up my RAM, as soon as I closed it up my RAM went back to normal.
Considering Macs usually have less RAM, this would explain what causes it to lag.
At 1/22/11 10:10 AM, GustTheASGuy wrote: It has a memory leak. Would crawl as soon as it reaches the RAM capacity.
Could you guys let me know exactly where the game started to crawl? I'll pick the game apart trying to find something wrong with the garbage collection, but if you could give me a place to start that would be super helpful.
At 1/22/11 01:08 PM, Chickumbleh wrote: Considering Macs usually have less RAM
Since when? most macs sold have 4gb standard, the most popular (being the 13" MBP) comes with 4gb as a standard whereas most PCs skim by with 2 or 3 then theres occasionally a jump to 8gb for gamers for every 500 standard PC users (offices etc) I would say they have roughly the same.
unless you mean less available ram, in which case state that next time :P
nobody
At 1/22/11 01:08 PM, Chickumbleh wrote:At 1/22/11 10:10 AM, GustTheASGuy wrote: It has a memory leak. Would crawl as soon as it reaches the RAM capacity.Gust is right, it just ate up my RAM, as soon as I closed it up my RAM went back to normal.
Considering Macs usually have less RAM, this would explain what causes it to lag.
Haven't looked into it but I'd suspect it's because most memory in Macbook's has a max speed of 667Mhz, I know mine does at least. Mac's don't generally have less RAM.
If you guys have Macs, think you could do me a huge solid and give the game a test, and tell me exactly where (if) the game starts to chug? This problem is the only thing keeping me from releasing the game, and I have no way of testing it myself. Thanks?
Well, I do know Windows slightly hates Flash, Mac hates Flash and Google hates flash too. Macs don't allow hardware acceleration in Flash but Windows does. This might cause your lag on Macs.
I have a 13" MacBook Pro, and it doesn't lag at all (2.53GHz with 4GB DDR3 of RAM).
Vexagon is dead. This is VanVeenGames!
At 1/23/11 07:46 AM, VanVeenGames wrote: Well, I do know Windows slightly hates Flash, Mac hates Flash and Google hates flash too.
So... in other words, flash just sucks in general?
#include <stdio.h>
char*p="#include <stdio.h>%cchar*p=%c%s%c;%cmain() {printf(p,10,34,p,34,10);}";
main() {printf(p,10,34,p,34,10);}
At 1/22/11 09:20 PM, chronicADRENLIN wrote: If you guys have Macs, think you could do me a huge solid and give the game a test, and tell me exactly where (if) the game starts to chug? This problem is the only thing keeping me from releasing the game, and I have no way of testing it myself. Thanks?
You mean the memory leak. Fix it.
To see it monitor the memory usage. Likely every time you switch areas something is not cleared and remains in memory.
At 1/23/11 08:50 AM, GustTheASGuy wrote:At 1/22/11 09:20 PM, chronicADRENLIN wrote: If you guys have Macs, think you could do me a huge solid and give the game a test, and tell me exactly where (if) the game starts to chug? This problem is the only thing keeping me from releasing the game, and I have no way of testing it myself. Thanks?You mean the memory leak. Fix it.
To see it monitor the memory usage. Likely every time you switch areas something is not cleared and remains in memory.
Thank you, that's the closest thing to an actual answer I've gotten. This has turned into a "Does Flash suck or not?" thread.
Anyway, I've tried monitoring the memory usage that and I'm not getting anything weird - on my system everything is clearing fine. That's why I'm wondering where people start seeing any problems.