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

Inverness

Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

115 Neutral

About Inverness

  • Rank
    Newbie
  1. Actors that already exist on the client would be those that are added to a level in the editor, which both the server and client would have a copy of in Unreal games. I recommend using RakNet if possible because it can handle reliability issues for you. Unreal compresses its vectors send sends the full value over the Internet, not a delta from the last state. This way the packet can be ignored if it arrives late or not at all. Unreal handles player movement separately from the rest of its replication using RPC. See this section: http://udn.epicgames.com/Three/NetworkingOverview.html#Player Movement and Prediction   This is why you need to be conservative in determining which actors in a game need to be replicated and how often they need to be replicated. In Unreal, the score board would be send to the client in WorldInfo which is a special actor representing the game world. You could also simply not use replication for things like that. Right now I have 3 modes of communication in my game: Normal replication happens only between actors and 5 times per second. This is done reliably, but order is not guaranteed and older packets can be ignored by the client. Example:public override void Serialize(DeltaSerializer s, IReplicaClient destination) { base.Serialize(s, destination); s.Write(_collideTiles); s.Write(_collideActors); s.Write(_blockActors); s.Write(_layer); } public override void Deserialize(DeltaSerializer s, IReplicaClient source) { base.Deserialize(s, source); s.ReadBoolean(ref _collideTiles); s.ReadBoolean(ref _collideActors); s.ReadBoolean(ref _blockActors); s.ReadSByte(ref _layer); }   Event messages can be sent manually between actors, which is what I use for my complex things like player movement or updating the inventory of an actor. For movement, this is done for every game update, which means 30 times per second as opposed to 5 for normal replication.private void MoveAutonomous(Vector2 delta) { // Only call this on the client when it is autonomous Debug.Assert(Actor.Role == NetRole.Autonomous); Move(delta); Vector2 newPos = Actor.Position; // Save moves so we can replay them later if the server corrects us _savedMoves.AddLast(new SavedMove(delta, _time)); // Tell the server to do the same move and confirm or correct our own NetOutgoingMessage message = CreateEventMessage(EventServerMove); message.Write(delta); message.Write(newPos); message.Write(_time); message.Write((byte)_direction); SendEvent(message, NetDeliveryMethod.UnreliableSequenced); } Player messages can be sent through through the player objects that represent clients in a game. The client only has its own local player object that can send to the server, but the server has one for each player logged in the game to communicate with its local counterpart. For each combination of a client and an actor relevant to it Unreal stores the values previously sent to that client. Replication is done by comparing the current value in an actor to the last sent value for each connection. This happens during network ticks only.
  2.   I'm also using Unreal's networking model as inspiration for my own project, though I'm using C# for it.   Anyhow, a few points:   Actor checking: I suggest adding actors that could possibly be replicated (that aren't already provided by the level itself) to a separate list to be checked. You would further eliminate unnecessary checks by allowing actors to specify a replication rate so less important actors need not use as many resources.   And yes, if a client joins, the server would evaluate replication for that client and send it any actors that are relevant to it and they have not already been replicated to it.   As for reliability, I am using the Lidgren library for C# and used reliable sequenced delivery so packets always arrive but old packets are dropped in favor of newer ones.   As for Unreal networking attributes, bNetDirty is set whenever a property is set on an object in UnrealScript, it is a helper variable so you can skip replication if its false. bNetOwner is true when the client you're replicating to owns that actor, and bNetInitial is true when it is the first time you're replicating so you can send variables that only need to be sent once.   My current source code is available, it might be of some help or it might confuse you.  ReplicaManager handles replicating my actors through the IReplica interface. And you can look at my MovementBehavior component to see how player movement is handled. I just copied how Unreal did it in that case.
  3. Considering I'm already pretty proficient with C++, for learning networking, I looked at existing documentation and code for engines like Source, Doom 3, and UDK. They were really helpful in understanding how I would design my game architecture for networking and the different ways that are possible. UDK's documentation on its networking is extensive, and Valve has a developer wiki with information about how they handle networking.   Sending messages between servers is very easy depending on what kind of library you use, such as RakNet.   Unfortunately I can't really point you towards a specific book or tutorial since I never used one myself.
  4. Quote:Original post by tgashby There's got to be a way to package it without dealing with that Visual C++ Redistributable... Can I just compile it in the console or something and include the dlls?With Visual C++ 10, you can simply include the runtime DLLs in the same folder as your executable and it will run. In previous versions, a private assembly was the only way to do this, but that is no longer necessary.