dop2000's Forum Posts

  • .c3p files are actually zip archives. Rename it to zip, extract to a folder, open yourproject.c3proj file in Notepad. You will see the version it was saved with, for example:

    "savedWithRelease": 18204

  • How big is your game? (in megabytes)

    Try disabling/removing things, until you find which one of them is causing the delay. For example - remove GooglePlay plugin, test.

  • I don't fully understand the issue, but I think you need to use Line of Sight behavior with ray casting, instead of the obj_PlayerDestinyFinder object. Cast a ray, use Player.LineOfSight.ReflectionAngle expression, maybe that will be what you are looking for.

    See these two templates:

    https://editor.construct.net/#open=instant-hit-laser

    https://editor.construct.net/#open=raycast-reflections

  • You need to have at least one copy (instance) of the object on any layout. Create a blank layout, name it "Storage" or something similar, put your Particles object there and configure all its properties. After that you will be able to spawn it.

  • Use Touch instead of the Mouse. You will still be able to control it with the mouse, but Touch plugin also has SpeedAt() and AngleAt() expressions.

    You can use them to apply an impulse at angle, for example:

    On Touch End -> Sprite apply impulse min(100, Touch.SpeedAt(0)) at angle Touch.AngleAt(0)

    But of course you will need to experiment with values.

    Instead of physics you can use Bullet or some other behavior.

  • If you have lots and lots of frames with size like 600x650, then it's understandable why the editor is lagging. You will also get poor performance and extremely high memory usage when you run the game!

    Run the project in Debug Mode and check memory usage by images, with and without this sprite, you will see for yourself.

    From what I can see, the image is very simple, you need to reduce its size and the number of frames significantly.

  • Check out "Blend modes" template in Construct 2.

    Both objects need to be on the same layer and this layer should have "Force own textures=Yes"

  • Add NWJS object to the project. On start of the layout run "NWJS Set window not resizable" action.

  • Add Drag&Drop behavior, set Axes=Horizontal Only in properties.

  • First of all, remove rex's Container plugin from your project, and WebStorage too. These are very old, long deprecated plugins.

    The problem is not with the containers, but with wrong usage of "Else" in event 39. "Else" doesn't mean "all other instances". It means that if previous event didn't pick any instances, only then the "else" block will be triggered.

    You need to remove "Else" and change the event to this:

    Hitbox is NOT B -> Shield set invisible

    (add "Hitbox is B" and then invert it)

  • Op probably means that moving pathfinding objects are colliding with each other. This question is asked about once a week on this forum..

    makevideogamesnow123 I have two examples you can try. Also, search the forum, you may find many other solutions.

  • Doesn't look like an infinite loop to me. Is there another loop in the parent event?

    What happens when you run it? Does it work if you disable "Repeat choose(0,1,2)" line?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Any touch/click means a new "On touch end" event is triggered, and that's why animation frame is changed again. You can add a condition "objThumbsUp is NOT visible" to the event. Or, better yet, instead of "On touch end" use "txtCorrect On Drop"

  • Your code is very wrong..

    "On start of layout" can not be nested in a sub-event and after a "Wait". Move it to make it a top level event. "On collision" sub-events also can not be there, they will never work.

    Also, your first event "NivActuel=5.75" runs on every tick. And inside of this event you have "Wait 3.5 seconds". This creates hundreds of wait-threads, which can cause all kinds of problems and bugs. Try to never use Wait inside of events which run on every tick!

    .

    I found your older post where Sam Dimanche have already pointed exactly the same issues. Did you even read his comment?