Search the Community

Showing results for tags 'real-time'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • HTML5 Game Coding
    • News
    • Game Showcase
    • Facebook Instant Games
    • Web Gaming Platform
    • Coding and Game Design
  • Frameworks
    • Phaser 3
    • Phaser 2
    • Pixi.js
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Skype


Location


Interests

Found 9 results

  1. I'm trying to build a real-time MMO game. I'm using Phaser for FE and Node.js + socket.io for BE. I have read all the tutorials like http://www.gabrielgambetta.com/client-side-prediction-server-reconciliation.html and so on. Different players might have different FPS, this is how I update position on the client (phaser): const data = { down: this.cursors.down.isDown, timestamp: Date.now() }; var deltaTime = (data.timestamp - this.lastTimestamp) / 1000; if (data.down) { player.position.y += speed * deltaTime; socket.emit('input', data); } This ensures speed is FPS independent (every player is moving with the same speed). The server is running a tick() at 60 FPS. This method is processing saved inputs from players. How should the server correct player positions? It doesn't know their delta times. It also can't use server's delta time since it would be always around 0.016 and it doesn't reflect player's update interval. tick() { var now = Date.now(); var serverDelta = (now - this.prevTimestamp) / 1000; this.prevTimestamp = now; for (var player of players) { player.update(); } } player.update() { for (input in savedInputs) { player.y += input.down * speed; } }
  2. Hi everyone! I've been working on my own in the past months on a game, OWN. It is a competitive, multiplayer, real-time, free-to-play and browser-based game developped with Phaser of course. To quickly sum it up, it is kind of a mix between Super smash bros and League of Legends. In 1v1, 2v2 or 3v3 you face opponents in a quick deathmatch on a small map. Games are super fast (3-4 min max) so that you can easily choose how much time you want to spend playing. Here is a short video footage of the game (sorry for the poor quality, it's just raw sequences to get an idea) : Even though the game is not quite finished yet, I'd like to increase the number of testers to have more feedback and to test the architecture. So I really do hope some of you will be curious enough to give it a try. If you're interested, please PM me so I will provide you with some registration keys for you and a couple of friends. Hope you guys have a nice day!
  3. Greetings! I see quite often around these parts and in further fields, that there are constantly people who are just starting out asking how to add networked multiplayer functionality to their HTML5 games. I was one of them, and I hated the near absence of practical explanations that were written in concise, plain-English, yet still detailed, of how to get started. So, I made a simple game example/template using Socket.io and Phaser, and documented the hell out of it. Almost everything gets a few lines of comments to explain what is doing what, and I haven't assumed any prior knowledge, aside from core JavaScript and being able to set up NodeJS and how to view the game in a browser. The main focal point is using Socket.io, as the game framework can be easily interchanged to one of your preference. Hopefully this will save a few hours and headaches for people who don't have a clue what they are doing. https://github.com/Arcanorum/basic-networked-multiplayer-game
  4. Hello everyone, I want to develop a real time game using phaser. Searching on web I found this course that looks great. I want opinions about course. I will buy it tomorrow! https://store.bgr.com/sales/the-complete-real-time-web-and-game-development-course?rid=1589861
  5. Hi everybody, I'm back after more or less one year :D. I 've been very busy with a lots of universiy exams, but now I have some time, so I've decided to made this simple real-time multiplayer game. Here is the code : Real-time-multiplayer-game-with-BabylonJS-and-socket.io Wht do you think about that? In your opinion, the logic behind the creation of the meshes is correct? This not the best game ever , but it is just an experiment and a way to learn how socket.io and BabylonJs can work togheter. Thanks a lot for all the previous support. Cheers, DellaFree p.s. It's my first project on github, so feel free to correct and modify whatever you want
  6. Island of conflicts http://islandofconflicts.com This game is a 2D real time survival inspired by Rust. What is it about ? - Explore the map and look for necessary resources to make items. - Survive the hostile environment (animals and players). - Build your home and expand your property to protect yourself. - Make weapons and explosives in order to raid and rob other players. - Try to acquire a title by going into areas guarded by dangerous creatures. - Title owners receive the ability to tax other players when they're collecting resources. This game is currently in Beta and we'd like to get some feedbacks !
  7. I have not built Multi-Player 3D games for over 10 years. But I now have a project and I want to choose a WebGL engine I looked at: Babylon.js Three.js PlayCanvas Cesium And I am am strongly leaning towards Babylon. Does anyone see any caveats, show-stoppers, or things I should be careful about. Does anyone have any pointers to work done using babylon.js as a way of veiwing real-world data? We have a variety of real sensors are sending motion, location, and visual clues via WebSockets. We need to handle a 25 FPS update rate, and have this animate, move, change meshes, change materials of Babylon.js objects. Some idea of the upper-bound that we can handle on a top-end workstation browser (GTX980 GPU) would be good input. Features that are important include: Easy import of 3D models (scene construction) buildings, roads, signs, bikes, cars, pedestrians LOD (Level of Detail) WebSocket This is critical, since we will be getting live data streams to drive the objects location, orientation, and attributes This also means that the objects need to be script-able (loc, orientation, attributes (size, and color and texture would be nice) based on websocket data buildings, roads, signs, bikes, cars, pedestrians physics collision detect mensuration from the model (engineers want to measure distance, light, speed, acceleration, etc.) Timeline control (forward, back, single-step) Camera control (first person, 3rd person, follow-me) Fog and atmospheric effects (outdoor lighting). Only Linux and Windows support needed for right now Can use NVIDIA GeForce GTX 980 Development time is at a premium. so the easier to get started, and testing the better.
  8. Tenobaal

    Realtime Chart

    Hello there, this will be my first post and I want to excuse all of my beginners questions. I will work on it. At the moment I want to create a real-time chart and there a several questions about a good “way” to realize that. 1) My first try is really simple: Draw a line between the Points with the “graphics.lineTo” function. Then shift the graphics object position to the left. The Problem is, that the graphicsData will grow until there is no shift of the array of the data. If I use a CanvasRenderer I can shift the graphicsData but it do not work in the WebGlRenderer. Are there any method to shift the Data? http://jsfiddle.net/Tenobaal/7m6u9q2n/ 2) The second try is to redraw the lines. So I put everything in an array and draw the lines in a for-loop after I clear() the graphics object. But this method is really bad for the performance. http://jsfiddle.net/Tenobaal/wvtmg3ze/ 3) The third try is to use the polygon object. But later I want to use the bezier-function, so the polygon object might be not the best option. There is another problem with the triangulate of the lines if you have a fast switching graph. So not really a good choice at the moment. I will post later Version in jsfiddle. 4) The last try is to generate a texture from the graphics object and paste it in as sprite. So I clear the graphics object and begin to draw at the origin. The sprite will shift to the left, too. The texture looks different because of the anti-aliasing? Another problem is, that I need two graphics objects, because if I shift the position of graphics object the generate Texture will lose the data of the "shift". So the performance is not so good because of the two objects and the view is not the best. I will post later Version in jsfiddle, too. Maybe you can help me out with an idea, how I can realize a good looking and nice performing real-time chart. I would be happy to learn. Sorry for my english, it is not my first language. Many thanks tenobaal
  9. Hi all, I just wanted to post a topic here, because to put it simply I didn't know any other place where to state my concerns. For starters, I wan't to say that I am currently middle of process researching/writing my own first real-time multiplayer roleplaying game to browser environment using technologies such as node.js/socket.io and I have my doubts whether I finish it some day or not - so won't be showing any cool links, at least, not yet The thing which really concerns me is that I have stumbled upon an issue that TCP/IP (according to many resources and literature) is just not suited for real-time multiplayer games, it works for multiplayer games with slower pace where getting responses from server with varying even bigger milliseconds (or second(s)) doens't matter and don't affect the gameplay much. For instance, Heroes of Might and magic (turn-based) in a browser? possible. Games likes the type of Diablo (real-time), not possible. To be honest, this is sort of a broken dream for me.. articles (from ACM) and through internet worries me that I have jumped too early to a train of technology, which simply to put - is not there yet. I have tried my best to use techniques such as prediction, delta-packets vs full world snapshots and interpolation (which is sort of under dev atm.).. which makes my game use less bandwidth and be more latency tolerant. However, the real problem is in TCP/IP itself and how it works, because socket.io communicates over it, it is argued not to be not suited for real-time multiplayer games at all. The fact which concerns me most is packet loss and how TCP/IP behaves in front of it compared to UDP: "..whenever a packet is lost, everything has to stop and wait for that packet to be resent. On the client game objects stop receiving updates so they appear to be standing still, and on the server input stops getting through from the client, so the players cannot move or shoot. When the resent packet finally arrives, you receive this stale, out of date information that you don’t even care about! Plus, there are packets backed up in queue waiting for the resend which arrive at same time, so you have to process all of these packets in one frame. Everything is clumped up! Unfortunately, there is nothing you can do to fix this behavior with TCP, nor would you want to, it is just the fundamental nature of it!" As a reference where this text is taken, section: "Why you should never use TCP to network a multiplayer game", see: http://gafferongames.com/networking-for-game-programmers/udp-vs-tcp/ So to speak, TCP/IP is not suited because it will try to resend data every time again and again through the line when it detects packet loss (including all buffered data which happened to every client at that time), even more, because it tries to guarantee this delivery it is much more slower than UDP. And the problem within case of a multiplayer game is that every new user joined to a game is a big risk in terms of service quality. We all know that packet loss is way too common. In favor of TCP/IP I must say that I would really like to use it - I though that I could use it, but facts are really getting into me at this point. I have also seen resources like http://onedayitwillmake.com/blog/2011/08/creating-realtime-multiplayer-games-using-node-js/ which demonstrates that "hey this can be done". But lets be real, that is an example with few clients connected to a localhost? (At least, it looks like it) rather than running a remote server under real circumstances. The thing which I also noticed earlier is that in node.js you can send messages using "volatile" flag while emitting, to avoid resending when failure is detected, however as I traveled through google I began to understand that it was only some internal queue issue rather than somehow mystically getting rid of problems of TCP/IP ? Now, the question is - does someone have actual facts and proofs that TCP/IP is a winner in terms of real-time multiplayer games for browser environment or not? Can it be done? and how? I am sort of a in a dead end right now. If I need to abandon the idea of TCP/IP and just go for the UDP, within browser environment it is sort of "impossible" I found this reference: http://blog.alexmaccaw.com/chrome-tcp-udp but that's basically it, pretty limited. Thnx, hopefully posted to a right forum, i need answers from other multiplayer game developers