I’m been doing a little bit of reading on this topic and I’m a bit intrigued.
Probably the best resource I’ve seen is here at Intel:
Smoke - Game Technology Demo
Here’s the article describing the system:
Just wanted to kick off some discussion about this, with Java in mind.
As it happens I’m currently building a highly concurrent framework in Erlang for my final year project at uni. It’s only for simple games and so doesn’t provide AI or Physics. It just concentrates on parrallalising updating the game state whilst pipelining it with the drawing code.
iD have quite a nice presentation on the parallization they’ve been doing in Rage: http://s09.idav.ucdavis.edu/talks/05-JP_id_Tech_5_Challenges.pdf
Job-based seems to be the way to go IMHO, as it scales much better (both in terms of dealing with varying number of cores/task and in terms of programming complexity). Having said that, it’s not something I’ve considered doing for my own games since they’re not usually CPU-intensive enough to warrant it. Usually I only move things off into threads to avoid blocking the main thread’s execution rather than trying to make maximally effective use of multiple cores.
My main reason for being interested in this topic is not because I need this for any particular game I’m working on, it’s just a technical curiosity. I’d like to be able to build a basic game engine using parallelism, just to open some doors in regards of knowledge and expertise.
It’d be fun to start an open-source java project to make something like this…
[quote=“appel,post:4,topic:34459”]
That’s something I’ve been interested in for a while, and would love to get involved in. But I’m waaaay too busy to commit to anything.
what a revolution… ??? heu… I did not kwnew that there is anoter way than this one to make multithread application, this is just the most logical way ? no ?
EDIT: sorry I had a bad day…
I wish you a better night.
Maybe you could contribute to an existing project, couldn’t you?
Depends on the project.