Quadraxas did you know is jcl testing multithreading on Lite-C?

But how about ditectx functions(d3d9.h), can I use this functions?

i just did quoted techMuc. you can read the rest of his message. he was talking about engines current state

Quadraxas on this forum easily confused

multithreading is a technique of the operating system (windows, unix, ...)
I can't speak for all types of systems/processors but every Intel(r) compatible prozessor (Intel/AMD) and all Windows(r) operating systems from Windows 98 support multithreading.

Since 3DGS only supports Windows(r) multithreading will run on every clients target plattform (with different performance).

But there is a difference between multithreading-support of the engine and lite-c!
The engine actually DON'T use multithreading but you're able to create multithreading applications with lite-c (see the example) yourself.

The main challenge of multithreading applications is the synchronisation of the results of the different threads but once your concept works well the benefit could be extensive (especially with the new generation of multi-core processor systems!)

I discovered that I/O-handling (file/video/sound) in more than one thread ends in a crash (and more!*) especial in multi-core-systems.


mercuryus


*) backup your system before playing with multithreading programming!

You can take a peek in windows.h in your gamestudio folder and see what other hidden miracles are available .

Multithreading is a must for calling a database realtime, if you don't want any stuttering. I think Lite-C simply ports it from your windows.h, together with alot of other useful functions.

Great contribution Mercuryus!

Regards,
Joozey

so with using lite-c functions for database in parallel, would I want to set up a global flag for data_locked, while the 2nd, nth threads are working, then get them to set it to unlocked when the database data is placed back into variables?

Is this the simplest sort of setup so that I can avoid crashes / mishmashed data?

(I'd think I would want multiple threads for database access, AI, network chat (reliable checks) and the like.)

Don
have a great day

You can only have a maximum of X many threads on windows systems. The default virtual space a thread consumes is 1Meg, and if you're not careful, your pc could end up being very busy for a long time. I suggest you create as few threads as possible, only use them when there's no way around, such as a database query. But even so you only need one extra thread for an unlimited amount of database connection. Pending queries may be stacked. I'm not sure what you mean with "data_locked", AFAIK you don't need to lock anything.

I guess I was thinking that when a 2nd thread was running an update query, I wouldn't want my main thread to be trying to read any of that data. I doubt I'll be using it in the very near future though, or without a bit more research. Thanks for the response

To gain the data in the main thread, you need to pass a pointer to the second thread to store the data in, then keep checking the pointer in the main thread for valid data.