gistfile1.txt

<Jarcode> mazeto: I'm referring to the kind of computation that occurrs in most simulation games as not parrellelizable
* pilne has quit (Quit: Quitting!)
<Jarcode> mazeto: for example, collision detection gets gnarly with multiple threads and you end up having to aggressively group bodies together that might collide with each other and then perform the actual computations in the same thread
<Jarcode> mazeto: and then the same with the other groups
* rmbeer has quit (Remote host closed the connection)
* Aruseus has quit (Quit: Leaving)
* Aruseus (~Aruseus@pD9526E42.dip0.t-ipconnect.de) has joined
<Jarcode> mazeto: but then if there's something difficult to predict (ie. very high velocity object that could travel across the entire game world), suddenly you're finding yourself yielding other threads and creating a massive mess
* rmbeer (~rmbeer@unaffiliated/rmbeer) has joined
<beaky> just use a neural network to implement the simulation stuff
* nyexpress (~textual@unaffiliated/nyexpress) has joined
<Jarcode> mazeto: sure, there are cases where it might have a realistic solution with multiple threads (ie. traffic simulation), since you can gaurantee these groups to always interact with each other, but that's probably a best-case scenario