• 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.
Sign in to follow this  
Followers 0
Zouflain

Scalability and Memory Management for Many Dynamic Objects in Large Space

1 post in this topic

In short, I have a very, very large world space to fill with objects. I was debating on how I should go about memory management for these objects, and I was very curious to hear what others had to say and where better methods might be employed.

Here's a description of the system as I envision it: The C++ engine will serve as a means of communication between Lua/OpenGL and Lua/SQLite in addition to other less relevant things like file loading. Game objects (that is, things that can be interacted with directly) will be handled Lua-side, communicating with each other through a messaging and event system routed through C++. For its part, C++ has absolutely no idea what an object is or does, it just blindly passes messages. These Lua-side instances will be divded (by space) into an active group - those objects that are on the screen - and an inactive group. When an object moves from active to inactive, it is removed from Lua (and thus RAM) and ported to SQL. Every 2~7 seconds, these objects are pulled back into Lua, updated, then sent back to SQL. Objects in the active group are rendered, undergo physics simulations, ect. To the player, the whole world is doing this, but in actuality it's just approximating what might have happened (basic snap-to pathfinding on an extremely simplified navmesh, for instance). Quitting and saving is merely a process of storing all remaining active objects in SQL. Loading just requires a query to locate objects in the same or neighboring spacial partition as the player/viewpoint.

The reason I ask about this is because one, I suspect I'll be dealing with hundreds of thousands of objects spread out over hundreds of kilometers of space. They're also quite data heavy, and I suspect processing each object will take quite a few ms to complete (a lot of object lookups/queries, a lot of unfortunately redundant checks). I can also see a bottleneck arising. The C++ engine is only aware of Lua-side objects. If an object is SQL-side, when C++ attempts to send it a message, Lua will have to check if the object exists, find that it doesn't, pull the object from SQL, process the message, and then port the object back to SQL. For every message. Something tells me this is too slow for interactive frame rates, but I have yet to test the system. Ideally, I only want to use SQL as a save state and to cut it out of the play-process entirely. I chose SQL because it's fast, SQLite is, well, lightweight, SQL works well for random access lookups, and I'm familiar with it. This is why I phrased this as memory management, since I can't see thousands of lua objects being friendly to my 4GB total RAM budget.

I'm targeting systems with 1GB VRAM, 4GB RAM, and 4 processor cores. As such, I also want to take advantage of multi-threading to make use of those cores. Typically, I avoid multithreading like the plague, or only allow each thread to operate on completely different sets of data. For this game, I wanted to implement a task system, where the main thread can create tasks for a pool of 3 identical subordinate threads to process (I suppose a configuration file would let the user select more or less to match their core count, but the goal is 4 well utilized threads). Thus, individual updates of offscreen and therefore insiginificant objects can happen on a separate thread (right along with LOD file management), so all the main thread needs to concern itself with is physics and rendering. When the game is loading, for instance, the subordinate threads are doing the heavy lifting while the main thread renders the now loading video/progress bar/ect.

My questions ultimately boil down to these: is there anything fundamentally wrong with this approach? Is there a more optimal approach, or a simpler approach that will fully make use of the target system? Can you see potential hazards in this approach that can be avoided through careful design?
0

Share this post


Link to post
Share on other sites
if you have large amounts of data, you could go with streaming. especialy if you are talking about threading your game.

and to minimize streaming and stuff, divide your world into segments which cointans a set of objects. (quad tree) that would probably speed up things alot. Edited by Tordin
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0