Early Platform Shooter

This forum is currently in read-only mode.
From the Asset Store
A pack of 76 platform designs for a platformer game with a mushroom/jungle theme
  • Hey People...

    I'm making a small game in order to learn Construct, I intend the game to be a platform shooter. First of all, I'm amazed by Construct -- coming from MMF (actually I started out way back in ZZT.. But I digress) it definitely seem more robust and more agile... However, that also makes me weary in regards of if I'm doing stuff in an effiecent , sane or "right" way. So, I have a small question to you well-seasoned .cap-jackers; could you take a quick look at my .cap to come with some feedback, no-no's or general tips on doing the stuff I attempt on doing? Basically, I'm leeching on your expertise for a sanity check:)

    Lastly a question -- How is the in-built platform movement working with regards to Time Delta and V-synch? Is it bulletproof to FPS drops?

    Warm Regards,

    Julmusten

  • Lastly a question -- How is the in-built platform movement working with regards to Time Delta and V-synch? Is it bulletproof to FPS drops?

    All of the built-in movements in Construct use timedelta, and no it's not bulletproof to FPS drops:

    http://sourceforge.net/apps/mediawiki/c ... #Drawbacks

    But the good news is that if you're careful about how you design things and you don't go crazy with shaders then FPS drop shouldn't be too much of a problem. Here's a page on optimization that should help you out a bit:

    http://sourceforge.net/apps/mediawiki/c ... ation_tips

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Thanks for the reply, so basically I don't have to worry that much about using events 100% logically as long as they work as intended? Because the things that will make the fps drops are most likely shaders or GPU heavy operations?

    Thanks,

    Tomtedricka

  • Things that drop fps in my experience (Cpu items/events):

    1. Very heavy collision checks. (by this I mean hundreds,sometimes even thousands, per frame. Overlapping at offset is one of the heaviest events.)

    2. Intensive loops. (usually when collision checks are involved.)

    3. Thousands of sprites on screen. (construct is extremely fast with this, so don't worry about it unless you have over 1000-2000 objects.)

    Shaders are the main culprit for slowdowns in most cases, but large and complex games without shaders often have to be careful with events. By shaders, I mean fx files that require a pixel shader version-greater-than-0 compatible graphics card. PS 0.0 effects don't slow down games and can be abused.

    Tips:

    -Avoid large sprites as much as possible (i.e., over 512x512)

    -When dealing with massive amounts of objects with complex movement properties, try to incorporate behaviors as much as possible, as they are faster than events.

    I took a look at your cap, and it seems logical. At first I couldn't understand the player object lol, it's so confusing. Only one circle moves, so I thought it was three circle sprites, but then I realized you were precisely rotating a single sprite with three dots. I would say that's a bit confusing, but if it works for you, then go for it. Also you don't need to set the bullet angle to the player angle upon creation because spawn object does that automatically. Also, you should use sub events instead of needlessly repeating conditions like "up arrow is down".

    <img src="http://dl.getdropbox.com/u/1010927/Forumpics/subz.png">

  • PS 0.0 effects don't slow down games and can be abused.

    Actually, this isn't entirely true. Sprites with PS 0.0 effects do take longer to render. I've done some tests and I've found that the engine can render on the order of about 2.5 times more sprites without effects before the framerate drops below the VSYNC rate.

  • Actually, this isn't entirely true. Sprites with PS 0.0 effects do take longer to render. I've done some tests and I've found that the engine can render on the order of about 2.5 times more sprites without effects before the framerate drops below the VSYNC rate.

    Hmmm, interesting. I assumed they just used a renderstate so they didn't affect performance. I never noticed a slowdown using many of them, but i'll take note of your test results, thanks Linkman.

  • Davioware - Thanks for you run down! It will definitely benefit me a lot!!:) As far as my cap goes, maybe a brief explanation is in place -- The body and legs are supposed to be different meshes so the legs can run forward while you aim around with the arms. So the three dots represents head and arms, basically The subevents you show makes sense, it's a different way of thinking I need to get my head around!:) Thanks again, your tips are invaluable!

    Thanks!

    ~Julmust

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)