Sofa_King's Recent Forum Activity

  • Nah, doesn't answer any of my questions ;) Reading first before replying wouldn't be harmful ;)

    - You literally asked zero questions in your initial post.

    - newt has done a great job of explaining.

    - There are some hang ups, especially in relation to developing for iOS.

    - It is super fun to use.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • > That's a different question entirely and I guess the answer is you make one and upload it somewhere then use the URL in the properties. It isn't important for testing. You should also be using test mode ads on the plugin.

    Thank you I will look at the privacy policy.

    app-privacy-policy-generator.firebaseapp.com

  • Ashley,I can't open my project, which I've been creating for six months! Can you help me restore it?

    Do you have any backup copies?

    What were you doing before this issue?

    Have you tried opening it in a different browser?

  • Why not publish to web, or scirra arcade if you don't have somewhere to host it?

    To further Oosyrag's comment:

    - Export from C3 into 'Web HTML5' or 'Scirra Arcade' and upload it to the linked sites

    If you really want to export into EXE:

    - Pay the money lol

  • Thanks for all your help and advice oosyrag! Yeah, I can see what you're saying now, that I am using it incorrectly. I will have a play with it and see if I can find another way around the problem.

    On the topic of the peer not communicating with the host, it was definitely related to the beta. You are right about it not being that 'peer ready' trigger, but I have no idea what else it could be.

    I may just leave this one to the experts.

    Again thanks for the trouble shooting! 🌠

    EDIT:

    I found the issue; the peers were waiting for a message from the host, which only triggers once. So if the host somehow misses the original message, then the peer is waiting indefinitely.

    Just wanted to own up and say, this was not a construct error in the new beta, but my own silliness.

  • > Set up a trigger that happens whenever your player double jumps.

    > On your double jump trigger

    I Meant something like this:

    You can double jump for free, but if you jump again after a double jump, only then will currency start depleting, with infinite further jumps after double (as long as the player has jump gold)

    What calminthenight said works for that also. Just add an additional variable counting the number of times the player is jumping in the current jump 'set'. Then do a [if x>2 then subtract 1 gold]

  • Well, I just realized that I have been using the r248 release (beta). I must have updated without realizing. Anyways, I tried an older release and this issue goes away. So it must be something related to this beta release.

    The shitty thing is that it wont let me roll back my most current save, so i'm stuck working on r248 now.

    Is this something I should report to the Construct head honchos?

    EDIT:I was able to easily migrate all the recent progress into an older non-r428 save. So all is well with me now :)

  • Yeah, I realized that after posting the screenshot. Really the only important part is that it gets stuck at:

    If TP2_LO1_Progress = 10.11 and Is ready for input

    When I disable the 'Is ready for input' condition, the peer is able to progress onto and gets stuck at the next condition:

    If Peer message Send_... and TP2_LO1_Progress = 10.12

    This is the reason why I put the Is ready for input condition there in the first place, to make sure the host is ready to receive and transmit the data.

    What is the correct way to use this condition?

    Why is there a communication breakdown between the host and the peer?

    Everything was working perfectly until a couple days ago. It is super strange because all my older backups are hitting the same issue in the same place.

  • Some additional info on this;

    As far as I can tell, the host is able to see and seems willing to accept the peer into the room. It looks like nothing has changed on the hosts end. The peers alias, ID, etc is all getting picked up successfully by the host.

  • Hi all. I'm running into a weird error where the peers are indefinitely waiting for the 'ready for input' trigger from the host. At first I thought it might be that I deleted something important by accident, so I went to a really old back up and even this old copy hits the same problem.

    Has something recently changed in/on/with the signaling server?

    Here is a screenshot of the events where the peers are getting stuck. I can see that the peers are getting stuck at 'TP2_LO1_Progress = 10.11'. They are sitting there and waiting for the secondary 'Is ready for input' condition to trigger.

  • Just an additional note:

    This guy wrote about this a long time ago. He came to the same conclusion that I have; There should be another way, but making two rooms works pretty well also.

Sofa_King's avatar

Sofa_King

Member since 12 Sep, 2018

Twitter
Sofa_King has 4 followers

Trophy Case

  • 6-Year Club
  • Email Verified

Progress

7/44
How to earn trophies