oosyrag's Recent Forum Activity

  • WebRTC is cross platform, so it technically should work across all devices. But, support for WebRTC itself isn't exactly universal... you'll have the best luck with the latest, updated browsers on their respective platforms.

  • AFAIK socket.io is a is library for websocket, similar to how the construct websocket plugin is for websocket. Their purpose is analogous, and there shouldn't be much difference that the node.js server cares about.

    I believe you can utilize socket.io with an add on or the scripting feature directly, but I'm not familiar with that.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It can be that your character animations have different collision polygons, causing strange behavior.

    Try using a square invisible helper sprite as a base for collisions.

  • Put your distance() expression inside a min() expression like so...

    min(distance(a,b),y) where y is the maximum you want. The min expression will take the smaller of the two numbers.

  • It's probably networking issues that can be resolved with a TURN server rather than any compatibility problem between pc and mobile.

  • construct.net/en/tutorials/supporting-multiple-screen-17/page-2

    See the section on keeping the ui in place and the anchor behavior.

  • cdn.discordapp.com/attachments/780147845151326229/790121973438480424/unknown.png

    Gamepad #1 is a Dualshock 4

    Gamepad #2 is a Dualshock 4 running through DS4Windows wrapper

    Mine also looks like #2, running a Dualshock 3 through SCP Server

    Not sure how to go about on android...

  • Perhaps if you upload a quick project that displays the returned value for detected controllers I can forward the link to a friend who has one and let you know what he sees.

    FWIW I'm using a dualshock 3 with an xinput wrapper, so the system sees it as an xbox controller. I think most games default to showing xbox style controls/tutorials. It would be nice to be able to choose manually in my case, sense autodetection would result in xbox style controls after all.

  • Even if you call it a real time game, as long as the players have no direct interaction with each other at any given time it is in effect no different than a turn based game. Which means syncing becomes a much lower priority, and you have tons of options to hide latency.

    Even if they do have to interact at some point though, it always helps to break down what information is most important to be consistent across players, and when is it necessary? Anything that has the potential to interrupt or change what is expected to happen from any players point of view needs consideration.

  • One option, given that player 2 doesn't actually know when player 1 hit the ball in real life, is to not send the shot information to player two until it's completed. Then you'd be able to send information about the complete trajectory and end location all at once for player 2 to replay, in a sense.

    Another option is to not sync the ball location at all. Let player two run his own simulation based on the input of player one, and then update the final location to the actual one upon (or right before) coming to rest, whenever that information is available. The difference should be mostly imperceptible if both users are running the same physics engine.

    Basically instead of syncing the ball location at all times, only sync it at key moments, wherever it would be most effective to hide latency (I imagine the final resting position is the only real value of importance here). You can even add an ease/lerp/tween upon syncing the final location, to hide any unnatural looking jumps that might occur.

  • If you want it to increment, you'll need set value at 0 to array at 0+x. You're setting it to array at 1+2, which never changes because you are not changing array at 1.

oosyrag's avatar

oosyrag

Member since 20 Feb, 2013

Twitter
oosyrag has 39 followers

Trophy Case

  • 12-Year Club
  • 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
  • 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
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

22/44
How to earn trophies