Not really.
But an animate based AI (ie intelligent that reacts to its environment instead of using an automate or scripts) needs a large amount of data analysis and decision making.
In my case: RTS which is squad based. The squad leader (a higher rank unit) does decisions on his own if there is no input from the player. But to do so, he / she analyzes the informations you have as player as well, which affect his surrounding.
In the same time, all the squad members are animate units as well which analyze their environment. but to a far lower degree than the squad leader, as they are led by player / squad leader.
It is sadly not possible to do this analyze approach usefull as the user input sadly suffers heavily.
You are right, so far it is not fully optimized yet. But even with optimation, it won't make a difference that is high enough to make the whole thing even nearly playable in realtime on a non-monster system.
So far, it has only been possible to come around that doing virtual multithreading. But running 2 apps using UDP for "communication" isn't something I plan to use as "final idea".
Surely, a different way would be virtual multithreading.
But I'm sorry. Its 2006, even Windows is multithreading capable since Windows 98 and today, all new CPU are multi core. So why would I want fake something that is much more efficiently implemented into the system and hardware today, especially as the workload for me to fake it is far higher. (the other 2 supported OS know of multithreading for many more years you know. Can't remember right now, when Unix got it exactly, but long before MS implemented it in Windows)
And create it in another language with threading and statically import it sadly not possible as many tests done by others earliers showed (RakNet Wrapper as the "most current" one).
But ok, why discuss over it if even a very experience programmer does not see the reason for multithreading although the terrains in Blitz3D already showed WHY it would be usefull and the language would heavily benefit of it.
If this is the last word on threading, thats a sad thing, as it is the feature that will be most needed in future.
PS: I'm not looking for a high featured super end thing as in java or C#, as even tests in PureBasic with its mutex showed that that is already more than enough to get around the problems.
But an animate based AI (ie intelligent that reacts to its environment instead of using an automate or scripts) needs a large amount of data analysis and decision making.
In my case: RTS which is squad based. The squad leader (a higher rank unit) does decisions on his own if there is no input from the player. But to do so, he / she analyzes the informations you have as player as well, which affect his surrounding.
In the same time, all the squad members are animate units as well which analyze their environment. but to a far lower degree than the squad leader, as they are led by player / squad leader.
It is sadly not possible to do this analyze approach usefull as the user input sadly suffers heavily.
You are right, so far it is not fully optimized yet. But even with optimation, it won't make a difference that is high enough to make the whole thing even nearly playable in realtime on a non-monster system.
So far, it has only been possible to come around that doing virtual multithreading. But running 2 apps using UDP for "communication" isn't something I plan to use as "final idea".
Surely, a different way would be virtual multithreading.
But I'm sorry. Its 2006, even Windows is multithreading capable since Windows 98 and today, all new CPU are multi core. So why would I want fake something that is much more efficiently implemented into the system and hardware today, especially as the workload for me to fake it is far higher. (the other 2 supported OS know of multithreading for many more years you know. Can't remember right now, when Unix got it exactly, but long before MS implemented it in Windows)
And create it in another language with threading and statically import it sadly not possible as many tests done by others earliers showed (RakNet Wrapper as the "most current" one).
But ok, why discuss over it if even a very experience programmer does not see the reason for multithreading although the terrains in Blitz3D already showed WHY it would be usefull and the language would heavily benefit of it.
If this is the last word on threading, thats a sad thing, as it is the feature that will be most needed in future.
PS: I'm not looking for a high featured super end thing as in java or C#, as even tests in PureBasic with its mutex showed that that is already more than enough to get around the problems.