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


  • Content count

  • Joined

  • Last visited

Community Reputation

104 Neutral

About Qaia

  • Rank
  1. [quote name='gekko' timestamp='1348639496' post='4983901'] What is the problem you are trying to solve with garbage collection? Are you trying to deal with cross-object references and lifetime management? Even if you go with garbage collection, you should still avoid run-time allocations and explicitly run the garbage collector at load-time or whenever you can hide the massive frame spike you will get. [/quote] My main interest in GC is related to RTS-type games. I'm experimenting with different ways to reach a good balance between game performance and resource management. The suggestion of smart pointers is definitely interesting and I'm probing that scenario. In the RTS genre, you constantly have dynamic objects being created and destroyed. The main thing I'm trying to work out is this: Would a single sweep to collect a large amount of destroyed units be more efficient than interrupting the gameflow in order to destroy each individual unit as it is no longer in the game? Think of multiplayer RTS battles like Supreme Commander or Total Annihilation where you can literally have 100+ units being destroyed within the span of "seconds" (vs "minutes"). Interrupt game logic to destroy each unit individually as it becomes unreferenced or sweep occasionally to destroy several unreferenced units?
  2. Is it adviseable to implement a custom garbage collector for a game engine written in C++, or just delete objects immediately as soon as they become unreferenced? If a GC should be implemented, what criteria / guidelines should be adhered to (in terms of when the GC should be called)?
  3. What's the preferred method to select units with the mouse, i.e., you have a unit on screen that you want to either control or see its stats and you hover your mouse over the unit and click to select it? I was thinking of reading the (x,y) screen coordinates (not the world coordinates) of the unit and comparing that with the (x,y) mouse coordinates. But I'm not sure if this approach is commonly used or efficient. I was also thinking if it would be possible to associate a hitbox with the mouse and project that into the world. Are there other approaches commonly used?
  4. Perfect! Skybox is exactly what I was looking for. Thanks! About the collision detection, I'm guessing I'll have to create a new content pipeline processor specifically for skyboxes, since my current implementation processes all 3D models with their corresponding hitboxes.
  5. What is the most efficient and preferred way to implement static backgrounds involving full 3D camera rotation? For example, space and aquatic sims environments. The background is exactly that, just a backdrop to create the overall encapsulating environment allowing the character to explore the 3D universe unhindered. I was thinking there are two general approaches: 1) Use a 3D model that encapsulates the universe (like a box) with the inside of the model textured; or 2) Use a 2D sprite sheet that maps coordinates on the sheet to the camera position. The downside to 1) is that because it is a 3D model (needless) collision calculations would constantly be performed. The downside to 2) is that the engine has to constantly perform the mapping calculations and reload the sprite sheet accordingly. Which of these two approaches is preferred? Are there any other approaches used?