libgdx中的线程和移动精灵的一般问题

Question

I am reassembling my game i wrote for android. It was written with simple canvas to learn the basics. To get it to a higher level i am going to write it with the help of libgdx . To do so i thought about a stage where i add my Actors (Monsters, skills if they are active, character and maybe particle) to. I read that this is a good way to assamble a 2D Game.

Some more informations about it. It's a 2D RPG based on an square system. Every step is one move to the next square.(maybe tile based lateron. At the moment the background is a single picture)

In the old version i used threads for every Monster so they can handle and react as they "wish". Is this also possible in libgdx or do i need to handle it in a different way?

If i want to move the Character from one to the next square i had a calculated time where i moved the sprite from one square to the next by changing it's pixelposition. In libgdx i am going to have a camera with the squares as init. So (40f,30f) for example. Does it work to move the character within an thread as i did in the old game? So i knew that it does take 500ms from one square to the next so every 50ms the ppuX need to be +0.1f. I also updated the sprite depending on that. So if it moves faster the sprite gets faster changed.

I also programmed the skills in that way. For example a fireball is a picture that gets moved by a thread till it hit something.

See the picture of the "prototype".

Answer 1

It's probably possible, but assigning a thread per entity is a very bad idea - so bad, in fact, that it has a corresponding TheDailyWTF entry:

http://thedailywtf.com/Articles/Sprite_Threading.aspx

Not only are you consuming resources unnecessarily in this approach, you're also endangering your sanity in the long run. I believe the linked entry, along with the comments, exhaustively elaborates on why that is the case.

Generally, libgdx supports the "main-loop" model, via the ApplicationListener class (specifically the render() method). There is a number of tutorials to get you started, including one for Android .

I know the approach may seem more limiting at first, but it allows for much more reliable code.

Answer 2

In LibGdx, the Game class's render() method will be called continuously. In this method you can do 4 things.

1) Process Input
2) Update sprites/actors
3) Check collision
4) render the world

You don't need to create a separate thread for moving game objects.