Here's a tiny example of implementing threads in you lite-c application.

download example (2.2MB)

But be warned!
Multithreading is not that easy to use and the syncronisation may be a challenge sometimes...

mercuryus

so CreateThread just... works? that's interesting, i haven't thought that lite-c was that much compatible to native c code.

The problems may accour in detail.
The cube-demo (multithread_crashes.c) works on my single-core system but crashes at the dualcore system. dunno why?

add a

while(key_t) wait(1);

after

if(key_t && gv_cubes<MAX_THREADS){

change in speed is magnificant, but idk if it reaaly worths it? (at least from my programmin skill level.)

there are things which should be calculated in their own threads, such as ai or network movement prediction.

Maybe it's possible to handle all particle effects in an separate thread or animations not need to be synchronised with gameplay (maschines/clocks/cloudes/fog/light/create dynamic content...).

But an extra thread is not "extra (so far unused) power" - a busy/overloaded thread can effect the main programm!

you can NOT use engine functions in other threads (especially every ent_, effect and _create function will probably lead to an crash). They'll crash randomly, probably because of sync issues

So I would restrict the use of a second or third thread on complex caculations like AI-Pathfinding.

Yes, things like pathfinding are a good thing to do threaded.

Hey TechMuc, what do you think about the safety of using the threads for
directx vertex manipulations and entity texture changes(ent_setskin)?

mercuryus thank you for this contribution.
Is multithreading integrated in Lite-c,I do not understand can I use multithreading in every system and any processor? Or multithreading may crash in some systems.