Comments on: XNA Framework GameEngine Development. (Part 8, Multi-Threading GameComponents)

By: Tal

Tal — Thu, 11 Jun 2009 16:20:18 +0000

I agree whit numer 9, but I got better idia.
Many games are used in load game screen, becouse it takes time until the game start. You should use in multi-threading for load all together(for multi core).
And my offer is to use in a multi BackgroudWorkers for the loading percentages, and whit simple calculation know the sum of loading percentages.

By: META_Cog

META_Cog — Mon, 09 Feb 2009 16:59:20 +0000

You have to be careful to make sure not to draw a texture before it’s loaded with this, because if something adds a texture to the texture manager and tries to draw it too soon, the texture will not be loaded yet and you’ll get an error. (This happens when using the menu from section 7) I don’t think it’s too big of a problem though.

By: UH COSC Interactive Game Development » XNA Game Engine Development

UH COSC Interactive Game Development » XNA Game Engine Development — Wed, 21 May 2008 16:52:58 +0000

[...] Part 8, Multi-Threading GameComponents [...]

By: Getting up with XNA GS 2.0 [UPDATED] - Kartones Blog

Getting up with XNA GS 2.0 [UPDATED] - Kartones Blog — Tue, 19 Feb 2008 20:54:39 +0000

[...] GameComponent Part VI: Input GameComponent Part VII: ScreenManager GameComponent (game state + GUI) Part VIII: Adding multithreading to GameComponentsPart IX: SceneGraphManager GameComponentPart X: CameraManager GameComponentPart XI: Static [...]

By: roecode

roecode — Tue, 05 Feb 2008 13:39:29 +0000

Not certain if using the ThreadPool could offer better results. If you like the implementation of ThreadPool or BackgroundWorker better, I am sure it would not be difficult to accomplish the changes.

It has always been my understanding that under the covers, asynchronous threading is all handled the same way. Granted, I am not doing any thread safety here, but since I have the ShadersLoaded and Initialized properties I essentially have a safety net.

By: adriano

adriano — Tue, 05 Feb 2008 02:30:43 +0000

Hi, you are doing a greate job. I saw your implementation of a multi-thread loading, this not would be betther use an async pattern with ThreadPool?

keep with the good job.

thanks

By: roecode

roecode — Mon, 04 Feb 2008 13:57:33 +0000

KaBaL,
Thank you, I am very happy this series has sparked interest.

By: roecode

roecode — Mon, 04 Feb 2008 13:56:37 +0000

Jaff,
I always appreciate your comments. I understand your desire for a thread manager class. Multi-threading is no easy task to debug, but not so difficult that it requires specific managment classes just for threads. About the only thing I could gain would be to put the ThreadStarter and delgate into its own static method, definitely something to consider.

By: KaBaL

KaBaL — Mon, 04 Feb 2008 07:55:27 +0000

Keep up the great work, can’t wait till the engine is complete, so to see how everything comes together, and finally be able to put “2+2″ together (figuratively speaking)

By: jaff

jaff — Sun, 03 Feb 2008 14:27:55 +0000

Cool, works great for me. Wouldn’t you prefer to create a ThreadManager class as a single point for thread creation though? I haven’t done loads of multi-threading so I’m cautious about making debugging any more difficult than it needs to be.
I guess it’s not really the point just yet… it would be easy to get bogged down in the details of a thread management system.
What I’m getting out of this most is an understanding idea of how engine components need to fit together.