• Advertisement

Axium Cog

  • Content count

  • Joined

  • Last visited

Community Reputation

110 Neutral

About Axium Cog

  • Rank
  1. Getting Started: First Person Shooter

    Thank you sir i believe i have enough to get started. You have been very helpful.
  2. Getting Started: First Person Shooter

    [quote name='BCullis' timestamp='1338157810' post='4943819'] A good server/client setup doesn't trust the client as far as it can throw them. Clients should send input and render visuals/audio. Server should be authoritative for everything else. [/quote] I see the value in this but doesnt that put alot of load on the server? [quote name='BCullis' timestamp='1338157810' post='4943819'] Basically, the client should tell the server "player clicked on this object while at its current location", and the server will be able to determine "that's standing in front of a control lever, so now they've opened the bay doors, which I will update the game state with and notify all my clients and AI/physics routines". [/quote] So 3d mesh collisions are handled server side? I can understand not being able to trust the client with saying what direction it was facing cause then you end up with CS snap shooting shenannigans, but this seems a little odd to be completely server side. Could you elaborate on the physics portion of this? As a side note once i get a firm understanding of all of this i plan to post a conceptual template of where each piece of behavior takes place and the general structure/routine of these engines.
  3. Getting Started: First Person Shooter

    [quote name='BCullis' timestamp='1338155640' post='4943811'] Graphics(shaders, cameras, animation (which can overlap with physic...) ) Physics Input Networking AI Content/resource management (level loading, scenegraphs, segment-culling or segment-pausing, etc) [/quote] This is more along the lines of what im looking for, thank you. [quote name='BCullis' timestamp='1338155640' post='4943811'] So what would you like more specific information on? [/quote] As far as multiplayer games are concerned, i know some of these functions are offloaded from the client and placed on the server. I know its a balancing act of just how much do you place on the server, but any guidelines would be helpful. This is what i know so far: Client Side- User Input, Graphics, Physics, Resource management, and of course some aspects of networking. Server side is a little more enigmatic, aside from managing connections, what does the server handle? I imagine AI, keeping track of locations, and informing clients of what they can see? Thank you both for your help thus far.
  4. Getting Started: First Person Shooter

    I am a computer science major, and very familiar with C#. The idea here is to create an engine from scratch. Im just not sure where to begin. I have XNA and OpenTK which are great to keep from reinventing the boilerplate but as far as how to structure an engine has proven a bit enigmatic. Thanks for your help so far.
  5. Ive been combing the forums and havnt found much generic help on the subject, mostly just highly specific topics, so here I am. I am beginning a Multiplayer First Person Shooter in C#. If anyone could give an outline of what the major parts of such an engine are, what aspects of functionality are handled by which part, and if possible a skeleton of such an engine would be greatly appreciated. Please keep replies as verbose as possible, post such as "just use XNA" are not inherently helpful. Please describe how to leverage XNA. This post will likely help others in the future. Thank you in advance for your help.
  • Advertisement