Chadori's Recent Forum Activity

  • SmallBull - Nice Game and very wonderful graphics, especially that you made it yourself.

  • I agree on what ashley said regarding memory usage but you should still destroy non-used objects on the layout on startup on negative(-) coordinates since many objects present on the layout (even invisible) still affects fps and cpu usage. I recommend preload images on startup by putting all sprites(images) or tiledbackgrounds(images) that are going to be used on you layout on the outside part of the layout and destroy on startup , create to insert the outfit & destroy to remove the outfit.

  • Kraplanta - Q3D is a paid set of plugins created by QuaziGNRLnose . It is a combination of plugins and behaviors that will make 3D making in Construct 2 easier/doable.

    This will be a good tool for your creation of 3D Monster Hunter game alike.

    Here is the link:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Very Nice Game. It would also be better if you could add some color.

  • Just saw a link posted in the forum and when I went to the link, I saw the old Scirra Store

    https://www.scirra.com/store/royalty-fr%20...%20plate-2179

  • If it's a new update then cheers!

  • — - Without you knowing, you helped me solve my scml object problem in initializing .

  • — - It is working now. I made a preloader layout to initialize the scml objects on start.

  • Sethmaster - Still the same result still showing the visibility delay, btw. I wrong the whole time that I was thinking that the cause of the short invisibility of the scml objects is the image not being preloaded inside the memory. I retested both versions of my game, w/ preloader and w/out preloader.

    With Preloader: Memory Usage: 28.18 mb

    Without Preloader (Images on the same layout used) : Memory Usage: 38.44

    It seems that the spriter objects were already inside the memory the whole time and the preloader only worsen it since every layout change the memory is flushed out.

    My point is that maybe the memory management is not the issue but the initialization of the spriter objects causes a delay.

    I hope you can still be patient with me. Do you have any more suggestion?

    Edit: I will try it again using preloader for spriter objects for the sake of initializing the scml objects.

    Edit: Great it is working properly now without visibility delay, made a preloader again and separately initialized the scml objects without the destroyoutside behavior.

  • I noticed that many still suggests layout to layout preloader. They use it to preload images of the objects that they are going to create/spawn during gameplay but not initially present on layout startup.

    For example; I were to make an rpg game. All RPG games have so many maps so I need to make a lot of layouts for maps but the player objects are used in each layout but it will be very unorganized if I put the players and bullets on each layout (map). So I will make a preloader layout to store all the players, clothes, enemies, bullets that are going to be spawned during gameplay on the maps (game layouts).

    If you think about this, it will be a very good time saver until you read this on the manual, saying that this is useless:

    Construct 2 only loads the images for the current layout. This avoids loading the entire project in memory which would be slow and consume a great deal of memory. When starting a layout, all images for the objects placed in the Layout View are pre-loaded. This includes all frames in all animations of any Sprite objects. (In other words, Sprites are either fully loaded in to memory, or not at all - they are never part-loaded.) When the layout ends, all images that are loaded but not used on the next layout are released from memory.

    If an object is not placed in the layout view, but events create it at runtime, its images are not pre-loaded. The Construct 2 engine is forced to load the object images at the moment of creation, which can cause a momentary pause in the gameplay, or in extreme cases a constant stuttering (also known as "jank"). In order to avoid this, simply place any objects that will be used by the layout in the layout view. If they are not immediately needed then they can be destroyed in a Start of layout event. They will then not exist when the layout starts, but Construct 2 will still have pre-loaded their images, ensuring that they can later be created at runtime without any jank.

    Emphasis:

    When the layout ends, all images that are loaded but not used on the next layout are released from memory.

    If an object is not placed in the layout view, but events create it at runtime, its images are not pre-loaded

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    In a different angle of view:

    If people suggest adding both images on the game layout & preloader layout so that there will be respect to what the manual said :

    all images that are loaded but not used on the next layout are released from memory .

    So there will be no images that will be flushed from the memory since the images are present on the "previous" & "next" layout.

    The purpose of this is to preload the images of the objects that are going to be used on the next layout. So it will be preloaded without getting flushed from the memory.

    Well I believed this until I tested it. It seems that a huge FPS spike will happen on start of layout that can cause glitches to anything that is created on start of layout. This happened to a test platformer I made with solid ground using a preloader if layout image memory is above (30+).

    *BTW. Correct me if I made a mistake*

    So experts please explain, are we doing it wrong. Did I miss anything? Should we leave this idea or should we continue to use this?

    Thanks .

  • Sethmaster - No I don't get the lag problem. That only happens when I have both objects in the preloader and the main layout. Besides, I don't use events to destroy preloader objects, I use DestroyOutsideLayout Behavior which is fast enough to destroy objects than events. Also, what I am experiencing is a short amount of invisibility of spriter objects when they are spawned on gameplay and not initially present in the main layout on startup (but they are present in the preloader). The reason here as I said above must be because of mobile limitations + javascript garbage collection that objects not present in the next layout will be flushed (so the preloader losses it's purpose). So the result is that there is a short moment of invisibility of the spriter objects. In my case, these are the bullets spriter objects. And Bullets that are invisible on first launch is kind of weird. So I am open for suggestions, thanks in advance.

  • Josek5494 - Correct me if I am wrong. If we use Admob-free 100% of the ad profit are received by us but if we choose Admob-Pro we only receive 98% and 2% to the developer or is it the other way around?

Chadori's avatar

Chadori

Member since 10 Oct, 2014

Twitter
Chadori has 49 followers

Trophy Case

  • 10-Year Club
  • Entrepreneur Sold something in the asset store
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • x2
    Coach One of your tutorials has over 1,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • RTFM Read the fabulous manual
  • x2
    Great Comment One of your comments gets 3 upvotes
  • Delicious Comment One of your comments gets 10 upvotes
  • Email Verified

Progress

24/44
How to earn trophies