Updating game objects...

Hello, there. I'll start off with letting you all know that I'm new to C++, although I have prior experience with other languages (Delphi, BASIC, Pascal, and some scripting langauges). I've always been a game developer at heart, and now I've decided to dwell into the realm of C++ programming. I could go on, but this thread has been created for a purpose other than stating my dull programming history.

In my planned game, it will (of course) feature objects of sorts that will be displayed on the map. This is true of pretty much any game.

I'm probably over simplifying this, so I'll get to the point: What is the most efficient way to store/access object data that can be read and updated with the most ease possible? The two options I was considering were arrays or linked lists. My experience in the latter is significantly lower. Basically, all I need to do is be able to efficiently run through every object in the game and update it accordingly.

Thanks in advance.

There is no one best way. It depends on the situation...

>all I need to do is be able to efficiently run through every object in the game and update it accordingly.

With that purpose in mind I would suggest an array. It is easier to run through them than it would be to cycle through a linked list.

However, if you plan on adding elements to the array/linked list DURING game play....its up for grabs....

Linked Lists can add fast because all you do is switch pointers...the problem is finding WHERE to add it to in the list...

Arrays are a bit more cumbersome, because if you exceed your length, you must make a new array of a larger size to add elements to, however the search time is probably much less in an array than in a linked list.

So, like confuted said before me, it all depends on the situation...

You've both made a valid point: I was rather vague as to what I'll be doing with these objects.

Let's say the objects were projectiles, such as bullets or laser beams or holographic cheese wheels. I would need to be constantly updating their movement and collisions, as well as be able to add new projectiles whenever the player arbitrarly whacks the spacebar.

I have the most experience with arrays, although if linked lists would work faster, than I'm more than willing to give it a shot.

As long as there are an (practically) unlimited number of bullets which will be (potentially) displayed, use a linked list. Especially since it doesn't matter if you have to update each bullet in a certain order.

what confuted said is very true....and also, it really helps if you keep a pointer to the end of your linked list so you dont have to cycle through it every single time you want to add something...

What if there are multiple object types (classes) that need to be constantly updated?

I know that I could make a dozen different linked lists, but is there an easier way to contain everything into one linked list?

I'm not really experienced on the matter, so I'm assuming that I sound reasonably logical. :P

You could use a linked list with void pointers.

I'm currently developing a game engine too, I chose to use linked lists to store game object data, however, instead of using void pointers, all of my game objects inherit from one class called Object, which has member functions like draw and update...
and each linked list node has a pointer to Object.
This works great for me.

I suggest not having all objects in the same list. What if you only want to traverse the bullets (and not the enemies)? If you have everything in the same list, you spend unneccessary time traversing objects you don't need to.

I go through the list once every frame to update all the objects, Idon't need to do it more than once, this maybe different for your engine though.

Maybe I didn't read hard enough, but why hasn't anyone mentioned the use of vectors?

vectors are essentially the same as arrays with extra little nice features

Quote:

---

Originally posted by glUser3f
I go through the list once every frame to update all the objects, Idon't need to do it more than once, this maybe different for your engine though.

---

In my version, I test all the objects vs each others (like if they overlap each other). This would require n^2 checks if all objects are in the same list. If you split the list into several, you can dramatically lower that number. For example, you have no need of testing if two bullets overlap each other. At least not in my game ^^.

It sounds like you don't test the objects vs each oteher. In thta case, you can as well go with 1 list.