• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
le_mec

Looking to test lag/packetloss/corruption

6 posts in this topic

I'd like to perform network tests on my game in the most realistic way possible. This means having to deal with players who are on crappy wireless connections, who might even be playing on cellphones.

 

Short of having a friend living in a far away country with a copy of the game and a cellphone testing platform, what's a good way to stress-test your networking gudgeons?

 

Are there virtual Ethernet adaptors that can be configured to drop a percentage of packets, corrupt them, delay them, send them out-of-order?

Maybe some sort of firmware that can be loaded onto an external router which would sit in between two testing machines?

 

And, is there any sort of standard for robustness that I should aim for, like supporting 300ms ping delays, 30% packet loss before things go wonky, dealing with timeouts, etc?

0

Share this post


Link to post
Share on other sites

Hmm. Looks like I might be able to set up my spare netbook with Ubuntu and turn it into a router and run Netem on it.

1

Share this post


Link to post
Share on other sites

One trick I have used is to write a thin layer over the socket API, and provide pluggable functionality to simulate packet loss/ordering at that level. Effectively, the sending side socket will elect to either discard or delay a configurable percentage of all packets, at random.

 

It seemed to do a pretty good job at the time. Of course, it only works for UDP, since TCP handles packet loss at a much lower level.

2

Share this post


Link to post
Share on other sites

Both options are good:

1) Run a Linux something-or-other, either as a gateway, or for the actual server, with an error injector.

2) Add a thin layer on top of your networking that supports fuzz testing in various ways. Even for TCP, this can be useful, as it can emulate high latency, slow throughput, etc.

 

In addition, if you're serious about this, I would suggest:

3) Rent a VPN connection in some other country, and test while connected through that. Because one kind of VPN user is Bittorrent users who have high bandwidth, those generally provide pretty terrible performance, so that's a great stress test!

1

Share this post


Link to post
Share on other sites

Why not just have the real thing? If you have a router, move it farther and farther away until the connection becomes highly unstable, which means you are at the very edge of its emission range (it fluctuates randomly). Voilà. This is as real as it gets and is how "players with crappy wireless networks" are actually going to use your software wink.png

0

Share this post


Link to post
Share on other sites

Just go to the local Starbucks at prime time.  Half of them still have decent performance but I find when there are 15+ people I often see packet loss spike from 0/1% to 5-15% and latency spike from 150 to 300-2000.

0

Share this post


Link to post
Share on other sites

Consider setting up a Linux box as your network router, and use netem (successor to NistNET) to cause network disruption.

 

The other alternative, if you are writing your own network code, is to put a debug only path in that lets you cause artificial failure conditions, limit bandwidth, and so on.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0