You mean it goes too slow, or skips frames? How much cpu does it take in Resource Meter?

If it's more than maybe 300 lines it'd be better to just post relevant parts instead of expecting people to wade through the whole thing, but I get the impression you have no idea what part is at fault.

Just try one or the other, and if nobody answers very quickly it's probably that nobody who's seen your questions is sure of their answer.

I don't really see anything that stands out as being wrong. Although 100 enemies might be a problem depending on how big the sprites are.

I tried compiling it myself to try it out (using some random images to substitute) but it lacks "objects.h" and I don't see the code to load the images.

The enemies sprites are 64x64, that get resized to a random number between 40 and 60.
yeah I understand pkcrel, and I've had a horrible time going over it and I cannot understand what I did wrong, unless its some form of bad coding that I have not learned yet.

Objects.h is a seperate header file and contains the following:

It still won't compile because it's missing stuff like initBackground() etc.

There aren't any prototypes or definitions for what a Background is, nor a header file to do those things. Maybe your program is garbling things as a result, due to passing incorrect types or something.

[EDIT]

Yeah, when I asked how much cpu in Resource Meter I meant how much processor utilization, not how much memory it took.

You could put everything in a zipfile and use the Drop Attachments Here button

{"name":"608968","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/6\/8\/68ba347dffbacfa2bcb6f72dfbd5795a.png","w":492,"h":274,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/6\/8\/68ba347dffbacfa2bcb6f72dfbd5795a"}

and it'll show up next to your name as a paperclip, which you could then put in a link with Formatting Help if you wanted.

I get these warnings, maybe fixing them will fix the problem. Find out how to enable warnings for your compiler.

main.cpp:316:79: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
   else if(joystate.stick[0].axis[0] >= -.3 && joystate.stick[0].axis[0] <= .3 && Cntrlr[LRIGHT] || Cntrlr[LLEFT])
                                                                               ^
main.cpp:324:80: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
   else if (joystate.stick[0].axis[1] >= -.3 && joystate.stick[0].axis[1] <= .3 && Cntrlr[LDOWN] || Cntrlr[LUP])
                                                                                ^
main.cpp: In function 'void drawPulse(Pulse&)':
main.cpp:599:16: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
      if(i == 0 && pulseAttack.timer >= 5 || i == 1 && pulseAttack.timer >= 6 || i == 2 && pulseAttack.timer >= 7 || i == 3 && pulseAttack.timer >= 8)
                ^
main.cpp:599:88: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
      if(i == 0 && pulseAttack.timer >= 5 || i == 1 && pulseAttack.timer >= 6 || i == 2 && pulseAttack.timer >= 7 || i == 3 && pulseAttack.timer >= 8)
                                                                                        ^
main.cpp:599:124: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
      if(i == 0 && pulseAttack.timer >= 5 || i == 1 && pulseAttack.timer >= 6 || i == 2 && pulseAttack.timer >= 7 || i == 3 && pulseAttack.timer >= 8)
                                                                                                                            ^
main.cpp: In function 'void initEnemy(Enemies*, int)':
main.cpp:688:13: warning: statement has no effect [-Wunused-value]
   enemy[i].x;
             ^
main.cpp:689:13: warning: statement has no effect [-Wunused-value]
   enemy[i].y;
             ^
main.cpp: In function 'int main()':
main.cpp:338:15: warning: array subscript is above array bounds [-Warray-bounds]
   {keys[SELECT] = true;

I also see that player.cpp is 0 bytes? Is that a mistake?

Also, allegro.log is 2.8 megs, probably leave that out.

I see there's a Project1.exe in debug, but my virtual XP machine says it's not a valid Win32 application?

Right now I'm getting a crash in initPulse because the case of the image and the string in the program don't match (linux case sensitive).

I'll play with it a bit more, this is just an update.

[EDIT]

I finally got it to run, it hovers around 58-59 fps, and I don't see any choppiness, but it certainly does look... odd.

{"name":"608970","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/9\/d99b5c5b1dc6274e768323eaf57a8f1a.png","w":1440,"h":900,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/9\/d99b5c5b1dc6274e768323eaf57a8f1a"}

[EDIT2]

Compiling without debugging info makes it drop to around 45 fps. Uninitialized pointers?

AHA! I see one bugaboo now, you're loading bitmaps meteor1.png and meteor2.png in startEnemy() and it's in the loop, so you're loading bitmaps forever. You should load bitmaps to an ALLEGRO_BITMAP at initialization and only use the ALLEGRO_BITMAP * from then on.

Right! you can also load on request only if the bitmap is nonexistant yet.

But, which this kind of thing shouldn't memory usage skyrocket? Correct me if I'm wrong but this should happen also in debug version.

I was going to start working on a player .cpp and .h, but ran into troubles. I have put that aside for now until i understand how to call them easier in my main.cpp file.

wow so picky! it is SO much cleaner though. thank you for putting your time into that, ill fix it all soon

I will do my best to clean the code up tomorrow when I get up. Thank you for your time tonight. Hopefully you'll be around tomorrow sleep well!

I don't know if you noticed one of my edits above, the post wasn't old enough to send to top

Hey guys, I have been working for some time now to fix things. Still seems to stutter here and there, but overall its not as bad. Do you know how I could turn on the warnings that you are getting? I am currently using Visual Studio 2012.

I have fixed the bugs that was posted in your comment earlier, and removed the infinite load of bitmaps in the loop. Still having issues, but ill continue to change some of my code up in the mean time to see if it helps.