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

Silgen

Members
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

178 Neutral

About Silgen

  • Rank
    Member
  1. Ultramailman - the white path overwrites the orange path, and the open list just outlines the orange block.
  2. Ah I understand what you are saying - my mistake. I disabled that type of movement to prevent it going through walls that are only one block thick - guess I'll need to revise that then.
  3. Surely it would have had to make the diagonal movement just before reaching the point though?
  4. I've finished implementing what I believe to be an A* algorithm in some rather heinous code. I hope to try out binary heaps when I revisit this. These are some images showing it in action. Blue representes an obstacle tile, orange a closed list square (explored) and the white line is the final path. Does this look correct? It moves towards the obstacle, then fills in back toward the starting point, until it can get around the obstacle, then resumes. [img]http://i.imgur.com/UvDhv.jpg[/img]
  5. My code is pretty dirty at the moment - unsorted lists for open/closed, and a 2d array for the map. The path is just a singly linked list of nodes.
  6. Working on my A* implementation - Mostly working fine, but I'm having difficulties in updating the g values of nodes. When I look at the neighbours of a given node - in order to check whether or not the g value is an improvement on the current node's g value, I have to search both lists, comparing the x/y coordinates of the current node, with each node in the lists. This seems over complicated. What is a good way of keeping track of the neighbours of a given node?
  7. Okay - then perhaps my question should have been - which representation of the search space will make running the A* algorithm on it easiest? What method is most commonly used?
  8. I have been reading about the A* algorithm recently, and I want to implement it myself to make sure that I fully understand it. What is the best way of representing the map that will be searched? Array? A tree of some kind?
  9. Thankyou for all of your replies. I've tried to take into consideration the points raised in the responses, and I've written a simple program to test this out. I was hoping you guys could give me some feedback - or some general pointers etc. [u]Extract from cState.h[/u] [source lang="cpp"]class cState { private: static cState* currentState; static bool isRunning; public: virtual void enter() = 0; virtual void update() = 0; virtual void leave() = 0; void setCurrentState(cState*); void updateCurrentState(); void exit(); }; class cStateA : public cState { public: cStateA(cState*); ~cStateA(); void enter(); void update(); void leave(); };[/source] [u]Extract from cState.cpp[/u] [source lang="cpp"]#include "cState.h" //--- cState* cState::currentState; bool cState::isRunning = true; void cState::setCurrentState(cState* target) { currentState = target; } void cState::updateCurrentState() { while(isRunning) { currentState->update(); } } void cState::exit() { isRunning = false; } //--- cStateA::cStateA(cState* caller) { //Clean up after the caller state and initialise the current one if(caller) caller->leave(); setCurrentState(this); enter(); } cStateA::~cStateA() { std::cout << ">> Destructor called for A" << std::endl; } void cStateA::enter() { std::cout << ">> Entering State A" << std::endl; } void cStateA::update() { std::cout << "Enter desired state: "; if(getch() == 'b') { setCurrentState(new cStateB(this)); } } void cStateA::leave() { std::cout << std::endl << ">> Leaving State A" << std::endl; delete this; }[/source]
  10. Going back to basics and writing really simple games (tic-tac-toe, currently) but trying to use a good, clean OO structure. All states are derived from a base class cState: [source lang="cpp"]class cState { public: virtual void enter() = 0; virtual void update() = 0; virtual void leave() = 0; };[/source] The code below is for the state manager [source lang="cpp"]void cGame::changeState(cState* targetState) { currentState->leave(); currentState = targetState; currentState->enter(); }[/source] I was thinking of putting each state in its own file, but this means I will need to pass a pointer to the state manager (so that the state manager knows when to switch states) and also an inclusion for all of the header files for the states that it can transition to. This sounds messy. Is there a better way of doing it?
  11. I don't have anywhere near as much experience with game development as I would like to, and I have an ever increasing amount of school work to be completing, leaving me less time to work on my projects. Apart from feeling that the platformer I was working on is far more complicated than it should be, I'm just not getting anywhere with it. Due to my entity management system, I'm struggling to fix bugs with the collision detection and movement without breaking something else. I feel like I've either bitten off more than I can chew at this point, or am simply over complicating things. I feel that I've hit a dead end with this current project, and my motivation has plummeted, ushering in a lot of self doubt about my own ability, which may or may not be accurate. This won't be the first time I've bailed on something like this, and honestly it just feels like complete failure. I'm not really sure what to do - should I just go back and work on something simpler, or what?
  12. I have recently returned to my platformer, and am having more collision woes. I am moving the player by its velocity, iterating through intersected solid objects looking for the minimum penetration axis, and reversing the movement. However when in mid air, and pushing against a wall - it gets stuck and vibrates. Has anyone had similar problems?
  13. Are you working on a platformer? Or maybe a 2D RPG type of game? If you are working on a platformer, do you not need states for jumping and being on the ground? Or could you just represent them using a boolean variable? I like the idea of using a state machine for the animations - what I was actually going to do was just set the animations in the walk state, or in the run state etc. - but this seems like a better solution.
  14. Lots of great information there. Personally I like to see things clearly mapped out. Perhaps you could map out the path you took from beginner to where you are now, or perhaps a suggested path that goes from knowing nothing about game programming to making something a bit more interesting. Like - learn python -> learn pygame -> make a pong clone -> make tetris etc. After all - learning to program games is accomplished by programming games.
  15. I have got my platformer working in a very basic fashion: entity/tile management system, collision, movement, collectible/dangerous items, camera etc. I have a long list of things that I would like to start adding/improving - and I think a state system for the entities would be a good place to start. My thinking was that this would simplify handling different kinds of behaviour - but also that I could link animations in with states. However I am unsure of exactly how to structure this. I was considering states like grounded, jumping, underwater, dead - and then having nested states (moving left, moving right, stationary.) How have you guys handled this in the past/would you handle this?