I think lite-C is a pretty cool guy, eh makes games run and doesn’t afraid of anything.

I think lite-c is fucked up beyond use thats what i think about half measures when it comes to coding languages but like you have an oppinion i have my own i think the only usefullnes it has as a language for actual game dev (for ease) is its vector functions (sometimes)

edit: by the way show me the games it makes run and dont come to me with its limited by the users ability as this is suppose to be a beginner engine and then you have pro versions and stuff show me wheres the pros using it and actually producing anything beyond "hey i make little thingy move and then then then .." its a piece of junk even in the hands of a good coder period ..besides this is off topic

Yeah. Sure. https://www.youtube.com/watch?v=fakKvlErGJE
That doesn't help Kartoffel a bit. He is asking how to reduce cpu usage. Splitting computation to threads does not minimize the load. The load is exactly the same and even a bit more for the thread management part. Using different threads only offers benefits when you want to speed things up in terms of the duration of the computation.

Actual lite-c or c++ ? Wont hold my breath for any further more proof of "lite-c" being worth anything but paperweight , seriously you dont want to argue that lite-c is anything but half measures ?

No , if he is running that computation during the time he plays the music , doung it on another thread will help taking the extreme load off the cpu because windows will split up the time every task occupies taking the load off of his main application period , do a couple of heavy algorithms in your main app and the cpu will have to dedicate time to your app and take alot of load while splitted up into seperate threads/tasks the cpus load will be split up by the time it gives to process every task and the processing load will be taken off the main app period thats why we have multicores these things are linked and designed for a reason , you want to argue that threads were actually invented for anything less ?

Well youre right that the time it takes to do all these tasks is shorten, but to get the cpu usage you have to add the usage of all (mostly 8) cores together and it will result in the same usage.
Its just a gain in terms of speed.

No, that is not the case. Using multiple threads does not magically take work away. The work to be done stays exactly the same, regardless of the number of cores or cpus being used. Multiple cores only help in terms of speed (assuming a given problem can be effectively split into separately calculable problems).

If you want to empty 20 bottles of beer and ask a friend for help you can split the "work" among you. This will half the execution time but that won't reduce the overall number of bottles to drink. If you're unlucky and you only have one 10 liter bottle instead of 20 .5 liter bottles the work cannot be split and the time required cannot be reduced.

What Kartoffel is asking for is how to reduce the overall number of beer bottles to drink. He's not keen on drinking the beer faster, he wants to drink less...

There is not really "8" cores mostly 4 with hyperthreading wich i am not going to elaborate on further ..

But like i have said dont know whats happening in the app therefore my advice could be ignored..

Only possible advice that could be given is to find whatever eats away at your cpu usage and try to do less of that ..

This could be hard because it very well may just be as "less" as it could be i wouldnt know but do know that cpu load is not actually a bad thing though videos music and media as such typicaly are cpu intensive

thank you all for your replies!

Although it seems like I can't change anything at the (background-) tasks done by acknex itself, I'll ask in the dev's forum, maybe there's something I can do.

On a side note: What system have you got? Running acknex without default.c included but nothing else utilizes about 50% of one of my cores @ 60 fps. At 30 fps it utilizes about one quarter of one core. I got an AMD FX 8350 processor.

I have to bring this up again but to humble
agree that yes you were correct with threads
excuse me for the little rant there , but
one thing i wouod not back down from
is lite-c suck imo i wil never like it unless
it were actual full blown c++ ..just my prefered language

yes supercan is cool agreed ..

Hope you guys have a nice day/night

cheers