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

TheBroodian

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

103 Neutral

About TheBroodian

  • Rank
    Newbie
  1. I've been writing a 2D platformer for some time now, and I'm getting to the point where I am preparing to add more objects to the world other than the player. This has led me to a position where I need to create some sort of collision system for dynamic world objects (NPC's/enemies, movable objects, floating platforms, etc). Up to this point the player has only utilized world-based collision detection, which works great, but world data is static, so I can't really use it to solve dynamic world object collisions. To start off with, I was just trying to form some sort of system so that the player could push, or be pushed by objects (be they enemies, or some other neutral type source) that would also sort of simulate a sort of weight between objects. It doesn't have to be perfect but I haven't been able to nail it down yet. Here is the code I've written so far to give an example about what in theory I'm trying to achieve: [source lang="csharp"]//Clears the anti-duplicate buffer collisionRecord.Clear(); //pick a thing foreach (GameObject entity in entities) { //pick another thing foreach (GameObject subject in entities) { //check to make sure both things aren't the same thing if (!ReferenceEquals(entity, subject)) { //check to see if thing2 is in semi-near proximity to thing1 if (entity.WideProximityArea.Intersects(subject.CollisionRectangle) || entity.WideProximityArea.Contains(subject.CollisionRectangle)) { //check to see if thing2 and thing1 are colliding. if (entity.CollisionRectangle.Intersects(subject.CollisionRectangle) || entity.CollisionRectangle.Contains(subject.CollisionRectangle) || subject.CollisionRectangle.Contains(entity.CollisionRectangle)) { //check if we've already resolved their collision or not. if (!collisionRecord.ContainsKey(entity.GetHashCode())) { //more duplicate resolution checking. if (!collisionRecord.ContainsKey(subject.GetHashCode())) { //if thing1 is traveling right... if (entity.Velocity.X > 0) { //if it isn't too far to the right... if (subject.CollisionRectangle.Contains(new Microsoft.Xna.Framework.Rectangle(entity.CollisionRectangle.Right, entity.CollisionRectangle.Y, 1, entity.CollisionRectangle.Height)) || subject.CollisionRectangle.Intersects(new Microsoft.Xna.Framework.Rectangle(entity.CollisionRectangle.Right, entity.CollisionRectangle.Y, 1, entity.CollisionRectangle.Height))) { //Find how deep thing1 is intersecting thing2's collision box; float offset = entity.CollisionRectangle.Right - subject.CollisionRectangle.Left; //Move both things in opposite directions half the length of the intersection, pushing thing1 to the left, and thing2 to the right. entity.Velocities.Add(new Vector2(-((offset * (float)gameTime.ElapsedGameTime.TotalMilliseconds)), 0)); subject.Velocities.Add(new Vector2(((offset * (float)gameTime.ElapsedGameTime.TotalMilliseconds)), 0)); } } //if thing1 is traveling left... if (entity.Velocity.X < 0) { //if thing1 isn't too far left... if (entity.CollisionRectangle.Contains(new Microsoft.Xna.Framework.Rectangle(subject.CollisionRectangle.Right, subject.CollisionRectangle.Y, 1, subject.CollisionRectangle.Height)) || entity.CollisionRectangle.Intersects(new Microsoft.Xna.Framework.Rectangle(subject.CollisionRectangle.Right, subject.CollisionRectangle.Y, 1, subject.CollisionRectangle.Height))) { //Find how deep thing1 is intersecting thing2's collision box; float offset = subject.CollisionRectangle.Right - entity.CollisionRectangle.Left; //Move both things in opposite directions half the length of the intersection, pushing thing1 to the right, and thing2 to the left. entity.Velocities.Add(new Vector2(((offset * (float)gameTime.ElapsedGameTime.TotalMilliseconds)), 0)); subject.Velocities.Add(new Vector2(-((offset * (float)gameTime.ElapsedGameTime.TotalMilliseconds)), 0)); } } //Make record that thing1 and thing2 have interacted and the collision has been solved, so that if thing2 is picked next in the foreach loop, it isn't checked against thing1 a second time before the next update. collisionRecord.Add(entity.GetHashCode(), subject.GetHashCode()); } } } } } } } }[/source] Unfortunately for me, this code doesn't exactly work. It... produces results, but not as intended. When an object pushes into another object, it's almost as though the object pushing has met a wall, which isn't entirely undesirable behavior in of itself, but then when the object stops pushing, both objects sort of rubberband in the opposite direction. Sorry if the code looks like a mess. Any thoughts are immensely appreciated.
  2. I'm currently developing a PC game with the assistance of XNA and I'm integrating keyboard and gamepad control support. Up until now I've only supported gamepad control, and finding an elegant way to allow the player to choose one or the other is posing a complicated task to resolve. I was thinking of creating a class that would sort of convert either input into a universal sort of data that the game could then use for the player's character and the rest of the game to interpret- but I don't exactly know what that might look like, and I don't know where to start? Then, I thought maybe it would be simpler to create a duplicate of my main character's class, except adjust it to respond to keyboard input instead of gamepad input. Can anybody offer any insight?
  3. Excuse me, how silly of me, I'm using XNA with a wrapper for direct input.
  4. Trying to work on some sort of a button assignment system to change key bindings for controllers and keyboards. I have some sort of foggy idea about how I would do this, but I reach a point where the idea escapes me a little bit. Both direct input and Xinput's buttons correspond to an int, so it would seem simple enough to be able to attach that int to a string to symbolize the function the button has in the game (as the player prefers). But I'm a little unsure of how I would set this up. In case I'm explaining this poorly, this is sort of how I would like it to work: A menu queries the player to press the button he wants to use to Jump. Player presses the button he wants to use for Jumping. That button returns its int value corresponding to that button, and the game stores that int somewhere and correlates it to the action/function. Anytime the button is pressed with that value, the game will relate it to the "Jump" button. And if at a later time the player would like to do so, he can reassign the button to another function, and use a different button for Jump.
  5. So, I've been developing a game in XNA and I've been trying to lay the foundation for my game before starting on the real meat and potatoes of the game itself and getting all of my game components in order. For the most part I think I'm almost ready to start with some actual gameplay, but I have one big unsightly brown spot in my game that I'd really like to be able to do something about, but cannot quite figure out how. I'd really like to implement direct input into my game being as I don't own an XBox controller myself, and I know that without it, I'm shooting myself in the foot because very few people do in general (at least as far as a PC game goes, obviously it isn't such a big deal if I produce an XBox version of my game, but at the moment I only have plans to release it as a PC game). I've read as much as I can about wrappers for XNA to access direct input, and have eyeballed a few wrappers for it, but cannot for the life of me find any worthwhile documentation on how it works, and as a result have sort of shelved the idea.In summary: has anybody worked at all with any wrappers like nuclex.input or soopah.xna.input or any other sort of direct input wrapper? Can anybody explain how they work or how I would go about making my own wrapper?