• 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
TheComet

Floating point accuracy across computers?

7 posts in this topic

I read the 1500 Archers paper on AoE, which specifies a networking model for RTS games known as "lockstepping", where only the actions and mouse positions each player issues are sent over the network. Contrary to the server-client networking model, this requires all clients to be able to simulate the game the exact same way.

 

How viable is it to use floating point numbers for things like unit positions?

 

Do all computers (including different operating systems) compute floats the same way, so that every client gets the same floating point error after every operation? What are potential pitfalls to look out for if trying to synchronise floating point arithmetic over multiple computers?

 

Would it be wise to go down the floating point route, or do you think it would be safer to keep all critical variables as integers?

0

Share this post


Link to post
Share on other sites

Thanks for the great information thus far!

 

@ApochPiQ - If I ever knock on your PM front door with a wall of text on how gay floats are, you will know I have failed and can be safe to assume I was weeping in a fetal position in the dustiest corner of my room as I typed it.

 

@Frob - That "Real" class you talked about, is that publicly available?

 

From what I gather, the safest approach would be to use a fixed point implementation for all critical data. I would have done this with two integers representing a "value" and a "factor". I suppose converting to and from floating point values is determent so long as the floating point error is insignificant enough. Is something like the following a good approach?

#include <iostream>

template <class I, class F>
class Real
{
public:

    inline Real(const I factor) : m_Factor(factor)
    {
    }
    inline Real(const I factor, const F value) : m_Factor(factor), m_Value(static_cast<I>(factor*value))
    {
    }
    inline Real(const I factor, const I value) : m_Factor(factor), m_Value(factor*value)
    {
    }

    // assignment
    inline Real& operator=(const Real& other)
    {
        m_Value = other.m_Value;
        m_Factor = other.m_Factor;
        return *this;
    }
    inline Real& operator=(const F f)
    {
        m_Value = static_cast<I>(m_Factor * f);
        return *this;
    }
    inline Real& operator=(const I i)
    {
        m_Value = m_Factor*i;
        return *this;
    }
    inline F operator=(const Real& r) const
    {
        return static_cast<F>(r.m_Value) / r.m_Factor;
    }

    // binary arithmetic
    inline Real& operator+=(const Real& rhs)
    {
        m_Value += rhs.m_Value * m_Factor / rhs.m_Factor;
        return *this;
    }
    inline Real& operator+=(const F f)
    {
        m_Value += static_cast<I>(f * m_Factor);
        return *this;
    }
    inline Real& operator+=(const I i)
    {
        m_Value += m_Factor * i;
    }
    inline friend Real operator+(Real lhs, const Real& rhs)
    {
        lhs += rhs;
        return lhs;
    }
    inline friend Real operator+(Real lhs, const F rhs)
    {
        lhs += rhs;
        return lhs;
    }
    inline friend Real operator+(Real lhs, const I rhs)
    {
        lhs += rhs;
        return lhs;
    }

    // ... got lazy

    friend std::ostream& operator<<(std::ostream& os, const Real& r)
    {
        std::cout << "Real(" << r.operator=(r) << ")" << std::endl;
    }
private:

    I m_Value;
    const I m_Factor;
};

Example usage:

#include <fpp.hxx>

#define REAL Real<unsigned long, float>

int main()
{
    REAL test1(1024, 6.0f); // two numbers with different fixed-point factors
    REAL test2(2048, 6.5f);

    test1 += test2;  // test1 = 12.5
    test1 += 7.7f;    // test1 = 20.2

    std::cout << test1 << std::endl;
    return 0;
}

Lots of overloads for the operators, though...
 

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