StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow do I make my component entity system thread safe?
primarykey
Id
3324244
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-24T07:31:05.743
FavoriteCount
5
LastActivityDate
2010-07-24T22:48:16.207
LastEditDate
2010-07-24T21:46:03.927
LastEditorUserId
400901
OwnerUserId
400901
ParentId
0
PostTypeId
1
Score
6
ViewCount
1913
LastEditorDisplayName
text
Body
I am currently integrating an entity component system, as seen <a href="http://www.gamedev.net/community/forums/topic.asp?topic_id=463508" rel="nofollow noreferrer">here</a>, with a physics engine and a graphics engine. This was all fine until recently deciding that the physics should be running in its own thread. (Thanks Glenn Fiedler!) As it is now I am simply locking a mutex shared by all subsystems when accessing components. Snippet from the physics loop: <pre><code>lock_guard<mutex> lock( m_EntMutex ); entitymap::iterator it; for ( it = m_Ents.begin(); it != m_Ents.end(); ++it ) { // Get physics component from entity // This is guaranteed to work ( component must exist for it to present in the map ) shared_ptr<comp_phys> phys( static_cast<comp_phys*>( it->second->getComponent( COMP_PHYS ).lock().get() ) ); // Get resulting Box2D vector b2Vec2 vec = phys->getBody()->GetPosition(); // Get position component from entity // Same as above, but this is the component shared with the graphics subsystem shared_ptr<comp_pos> pos( static_cast<comp_pos*>( it->second->getComponent( COMP_POS ).lock().get() ) ); // Update position component from Box2D vector pos->setPosition( vec.x, vec.y, 0 ); } </code></pre> Snippet from graphics loop: <pre><code>lock_guard<mutex> lock( m_EntMutex ); entitymap::iterator it; for ( it = m_Ents.begin(); it != m_Ents.end(); ++it ) { // Get position component from entity // This is shared with the physics subsystem shared_ptr<comp_pos> pos( static_cast<comp_pos*>( it->second->getComponent( COMP_POS ).lock().get() ) ); // Get position from position component doubleVec3 vec = p->getPosition(); // Get graphics component from entity shared_ptr<comp_gfx> gfx( static_cast<comp_gfx*>( it->second->getComponent( COMP_GFX ).lock().get() ) ); // Update graphics component from position component gfx->getObject()->getParentSceneNode()->setPosition( float(vec.x), float(vec.y), float(vec.z) ); } </code></pre> This is obviously a very naïve implementation, so I tried making the individual components have their own mutexes. It seemed the logical performance choice, but then the physics results (as queried through the position component) wouldn't always be consistent and reliable. What would be the most efficient manner of accomplishing a smooth updating process? Should I let it update the entire world in one go or do something more incremental? Edit: It has come to my attention that the pointer acquisition scheme is flawed, but let us assume that the pointers are valid.
Tags
<c++><entity-framework><boost><multithreading><components>
Title
How do I make my component entity system thread safe?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USnilekurt
UserOwnerUserId
1. USnilekurt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow do I make my component entity system thread safe?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow do I make my component entity system thread safe?
 UserUserId
 USennuikiller
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POHow do I make my component entity system thread safe?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.