Chadori's Forum Posts

  • FabianB - There are so many possibilities. But I can link you to some documentations that the creators made to solve these kind of problems. These will provide you almost every basic knowledge you will need in optimizing your game.

    Performance Tips

    https://www.scirra.com/manual/134/performance-tips

    Optimisation: don't waste your time

    https://www.scirra.com/blog/83/optimisa ... -your-time

    Memory usage

    https://www.scirra.com/manual/183/memory-usage

    Remember not to waste your memory

    https://www.scirra.com/blog/112/remembe ... our-memory

    Best practices

    https://www.scirra.com/manual/34/best-practices

  • You do not have permission to view this post

  • Problem Description

    The Longer the Object the more inaccurate the mouse selection becomes. This is noticeable when an object reaches 10,000+ pixels of length. The Mouse Hitbox tends to become inaccurate unlike it's drawn canvas. And unable to keep up with the canvas.

    Tested Objects:

    Tiledbackground : Affected;

    Sprites : Affected;

    I only tested two plugins. But I'm sure it's the same for all drawn objects.

    Even though it's already noticable when an object reaches 10,000+ pixels of length, I still set the length to 111,000+ to enhance the effect.

    Construct 3 is not affected.

    Attach a Capx

    https://1drv.ms/u/s!AjcW2ueud6qp6nsJz1Nr91dXEfd8

    Steps to Reproduce Bug

    It's easy to reproduce the bug.

    Just try your best to select either the TiledBackground or the Sprite. Especially at the X-axis end point of the target object.

    You will find it difficult to select the 2 objects.

    Observed Result

    The objects can't be selected.

    Expected Result

    The objects should be selected.

    Operating System and Service Pack

    Windows 10 64-bit.

    Construct 2 Version ID

    Construct 2 r246 Beta Release

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • NN81

    I suggest posting this on C3's bug section too for immediate action. Scirra doesn't really prioritize Construct 2 bugs as much as Construct 3 bugs.

    Instructions are stated here by Ashley :

    You can also just redirect this bug report to your C3 bug report too so that Ashley can read this thread too.

    I also agree that this is a bug, but I still think the bounce effect shouldn't be removed. Just have a boolean to enable/disable this feature.

    This is very useful in high speed 8-direction movements. You'll get what I mean when you set the "Max Speed" to about 5000+ and "Acceleration" to about 2000+.

    Think about this as an additional feature. We don't want other old/in-production games that take advantage of this feature to get broken.

    I'm not sure if it's feasible but new conditions like "Is collision-bouncing" and "collision-bounce enabled/disabled" would be nice.

    And a "set collision-bounce enabled/disabled" action too.

  • Hi guys I would love to have an update page in my game where ajax pulls information from a webpage in to the game how do I do this? The webpage is here http://bedfordgamesupdate.bitballoon.com/

    Here is the tutorial in using the AJAX plugin.

    Although for the backend part of your website, you would need knowledge on PHP for that. Depending on the purpose, you could also use xmlhttprequest. And also a bit knowledge about javascript.

    But I assume you already know that since you are developing a website.

  • This is amazing. Thank You.

  • —

    Firebase series plugins are already in TODO list, and I also plan to remove api v2.x supporting (now is api v4.3).

    That's good news. Thanks rexrainbow

  • ThePhotons - Please also convert your Photon plugins to support C3.

  • rexrainbow - Please also convert your firebase plugins. It's the only stable backend we've got.

  • The feature suggestions platform is for things exactly like this, you should post it there so people can vote on it.

    Ohh Sorry. Did not know there was such a thing. It's been a while since I last logged in.

    I'll post it there now.

  • Amazing. A must buy with the preloader plugin!

    But — , since Construct 3/2 uses the spritesheet method in loading images. Won't it affect other textures inside a spritesheet when you unload a specific texture from the same spritesheet?

  • [Feature Request]Construct 3/2 : "Description" Property and "Tooltip" Property for all visual objects.

    Feature Request Voting Link: Construct 3 Ideas : Description and Tooltip Properties with Visual Tooltips!

    With my years of experience in Construct 2. I noticed that with many duplicated objects in a very big project with lots of instances and objects, it can be very tedious to differentiate behaviors of same imaged objects. Some of us Construct 3/2 users took advantage with the feature "Construct 3/2 can differentiate same imaged objects on export, therefore lessening memory usage. " to also optimize cpu usage by cloning objects with the same image but programmed with different behaviors. To avoid redundancy calls within the program.

    Without the tooltip or description visual properties, our development will take longer exponentially as our project becomes bigger.

    Though, we could slightly lessen the burden by adding instance variables providing the descriptions but it will only make another redundancy and that's something that we're trying to lessen in the first place. And it cannot compare to a visual tooltip that will solve both problems at the same time.

    Long story short:

    Adding the Visual Tooltip and Visual Description as an object is selected will help our development significantly.

    It will eliminate the burden of tedious differentiation of same imaged objects in finding their individual behaviors.

    With those features, we can help ourselves label each objects suited to our situational needs.

    Main Feature Requests:

    • Object New Property: "Description:". Should be below "Name" property. As much as possible should be near the top part of the properties bar. Seen in the image.
    • Object New Property: "Tooltip:". Should be below "Description" property. As much as possible should be near the top part of the properties bar.
    • Visual representation of the "Description" property and "Tooltip" property. Seen in the image.
    • Visual Property triggered/shown when the object / objects is/are selected.

    Sub Feature Requests:

    • By Default: Description Property would be the Object Name.
    • By Default: Tooltip Property would be the blank.
    • Visual Tooltips can be disabled at anytime.

    Visual Tooltip:

    New Properties:

    Thank You so much Scirra Team.

    Ashley

  • Hi Laura_D , I'm not sure if you are the one in charge of these type of things nor do I know if I'm in the position to talk about this. But sure would love to suggest an official Construct 2 / 3 sticker design and shipping.

    Found this though: https://www.stickermule.com/user/1069173086/stickers (C2)

  • So useful. Thanks...

  • Ashley has a point, investing to a young technology which has potential to improve in time. But currently, within this decade, I'm with digitalsoapbox on this one, HTML5 is too young, javascript so slow... Even making a small Flappy Bird game is far more stable making in Unity for an Android Jellybean phone from 2012 than making on C2.

    As far as I remember, my tests back then has a performance of 60fps stable no significant spike for the game made on Unity and 24fps unstable, frequent lag spikes and unplayable for the one made on Construct 2.

    Theoretical FPSs or hypothetical speeds between native and html5 doesn't matter anymore when real life benchmarks are so significantly bad.

    In conclusion: Ashley you're so wrong ...