• 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
  • entries
    11
  • comments
    17
  • views
    22345

ComponentManager v ComponentMapper: Dawn of Components

Sign in to follow this  
Followers 0
TheChubu

1282 views

[font=verdana]Do you know in which results page dustArtemis appears if you search for "artemis framework" in Google? Absolutely in none of them! So we're going to celebrate by talking about the ComponentManager class.[/font]



[font=verdana]

dustArtemis

[/font]



[font=verdana]dustArtemis is a fork of Artemis Entity System, which is a BSD-licenced small Java framework for setting up Entities, Components and Systems.

(to be fair if you google "artemis fork" its there like in the eight result but I doubt anyone Googles for forks exclusively, spoons on the other hand...)

Components, components, components!



ComponentManager is what it sounds like, it manages components in a way that isn't very memory efficient, but its quite fast for adding, removing and retrieving components.

It holds a Bag for each Component type there is. That means that in a single vector(ish) collection you have all the components of that type.

This makes it rather fast and easy to access components IF you know their index, and it happens that their index into the Bag is exactly the ID number of the Entity owner of that Component, how convenient!

The protagonists



Artemis organizes it in two classes really:

ComponentMapper is what EntitySystems use to access components when iterating over entities. All that is needed is a simple get() to have your component ready to use.[/font]void process ( Entity e ) {SomeComponent cmp = someComponentMapper.get(e.id);doMagic(cmp);}
[font=verdana]There, direct index lookup, all the O(1) glory you can muster.

Now, ComponentMapper is just a thin veil over a particular bag of components that, as I described, originate from ComponentManager actually. Since ComponentMapper is used for access, ComponentManager's purpose is mainly adding and removal of components.[/font]protected void addComponent ( final Entity e, final Component component ) { final int cmpIndex = ClassIndexer.getIndexFor( component.getClass(), Component.class ); initIfAbsent( cmpIndex ).add( e.id, component ); e.componentBits.set( cmpIndex );}protected void removeComponent ( final Entity e, final Class type ) { final int cmpIndex = ClassIndexer.getIndexFor( type, Component.class ); final BitSet componentBits = e.componentBits; // if entity has such component if ( componentBits.get( cmpIndex ) ) { componentsByType.getUnsafe( cmpIndex ).removeUnsafe( e.id ); componentBits.clear( cmpIndex ); }}
[font=verdana]Adding and removing components is a tiny bit more complex since what you know at the moment is the component's class, not its index.

All the indices!



Here it comes my own addition, ClassIndexer. ClassIndexer just does one rather simple thing, given a superclass, it indexes incrementally the provided subclass. So each subclass of Component will have its own incremental index. Since those indices are the ones we use to find the corresponding Component Bag, they can't be any value, so they start from 0.

This process involves a hash lookup, and in case you use it for something else, ClassIndexer is prepared for multithreaded access (original idea was to be able to create Entity instances on different threads but that idea fell through once I started to see all the side effects I'd have to take care of).

It was the same cost for original Artemis (well, HashMap lookup instead of ConcurrentHashMap lookup) except Artemis had two separate ways of dealing with the indexing for EntitySystems and Components (specialized inner class and ComponentType respectively), I just removed that code and made a single point where both get their indices.

I can probably jiggle things a bit around and get rid of it for this particular case (off the top of my head, HashMap, Bag>) but there are a few more places where indices per Component type are used.

After that, its smooth sailing, access directly by index, clear or set the corresponding component type bit in the Entity for removal/addition respectively (so EntitySystems can know if they're still interested in the Entity), and you're good to go.[/font]

Pre-emptive initialization


[font=verdana]
There is also another small addition of mine here, while fixing a few null pointer exceptions in this class, I choose to eagerly initialize the bags in 'componentsByType' so not to do null checks every single time.[/font]private final BoundedBag initIfAbsent ( final int cmpIndex ) { final int prevCap = componentsByType.capacity(); // If type bag can't hold this component type. if ( cmpIndex >= prevCap ) { componentsByType.ensureCapacity( cmpIndex ); // Init all the missing bags. for ( int i = componentsByType.capacity(); i-- > prevCap; ) { componentsByType.setUnsafe( i, new BoundedBag<>( Component.class, 4 ) ); } } return componentsByType.getUnsafe( cmpIndex );}
[font=verdana]Those branches are taken very few times, HotSpot can "prune" them when JITting the methods.

The End... Or is it?



Well, thats it for now, next entry I'll discuss a bit the issues with the "index by Entity ID" approach that I've encountered. Cya![/font]

3
Sign in to follow this  
Followers 0


0 Comments


There are no comments to display.

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