Asmodean's Forum Posts

  • I think after the collision the top object is in 'sleep mode' and disable the collision isn't changing this state.

    Try: 

    + Mouse: On Left button Clicked on TopObject
-> TopObject: Disable Physics collisions with BottomObject
-> TopObject: Set Physics Immovable
-> TopObject: Set Physics Movable

    Or you could disable and enable the physic-behavior of the top object. That should reset the state.

  • That is called jamming https://en.wikipedia.org/wiki/Rollover_(key)#Ghosting.

    Try another key instead of space like shift or control.

  • Try this:

    drive.google.com/file/d/1ts2b1xrHfNFUwfAhmLcfvuYFexrAPTtt/view

    Don't know if this exactly what you want.

  • May be I understand this all wrong, but would it not be easier to use pixel per tick instead? 

    + System: ProgressBar.Width ≤ 208
+ Mouse: Left button is down
-> ProgressBar: Set width to Self.Width+(208÷3)×dt

+ Mouse: On Left button released
-> ProgressBar: Set width to 0

    With 208 the width and 3 the 3 seconds and if you have 60 FPS it would add (208/3) * (1/60) = 1.1556 pixel per tick to the width.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It seems that is a zipped project Folder. You only have to unpack it (you can also attach the suffix .zip, so it will be recognized as zip) and open the folder with Menu -> Project -> Open local project Folder.

  • Sorry my fault, answering before understanding the question completely.

    I think that is more a picking problem. In the second version the overlap (128,0) is already in (128,-128) covered. So it picked only the (128,-128), I guess. I also think that the for each is a problem. In this sub event it has only one choice, because the for each picked one raildetector.

    If you have an and event with two conditions it can only be one picked. If you want that all raildetectors with overlap (128,0) and (128,-128) are picked you need and 'or' event.

    I hope that makes sense. I'm not sure myself, without an example is only guessing.

  • The first one is an 'or' the second one is an 'and'. Make it an 'or' and it will work.

  • I think the easiest way is to use the Browser-Plugin: 

    | Global string myString‎ = 3*(4+3)+(4+2)/6
| Global number myResult‎ = 0
+ System: On start of layout
 -> System: Set myResult to Browser.ExecJS(myString)

  • My guess, the moving animation is now triggered the whole time you press a moving key (left,right). So the the animation for firing will never be played completely and the the end of animation event will never be triggered.

    It also looks like the running animation is only the first frame, because it starts over and over again.

    You could differentiate between only running and running and fire together.

    It's hard to say what is the best without seeing the wohle game code.

  • That is because you are using a triggered event (with the green arrow). Try to use 'Key is down' instead.

  • Have you disabled the "Default Controls" in the Behavior?

  • ashley say "H.264" and not "MPEG-4 AVC".

    H.264 and MPEG-4 AVC is the same. If you use that for video and AAC for Audio it should work.

  • - .mp4 with AAC codec (audio play but not video > black screen).

    What video codec do you use? It should be "MPEG-4 AVC"

  • The orientation is wrong of your sprites. 0° is to the right, so you have rotate them 90° to the right in the Sprite-Editor.

    And then this should work:

    System: For each aim -> aim: Set angle toward (aim(LoopIndex+1).X, aim(LoopIndex+1).Y)

  • It should be arrow(IID).angle

    With IID (Instance ID). So arrow(0).angle for the first instance , arrow(1).angle second ect.

    Give it a try.