You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was reading this article these days and thinking if Flixel Community could benefit from multi-core processors.
The idea is to identify workloads that can be performed in parallel using Workers, such as physics and path planning. It would be awesome if Flixel could check for Workers availability and, if that's the case, take advantage of it, transparently.
A physics plugin based on Workers, for instance, would be a hell of a feature to justify the implementation of some sort of Workers API.
The text was updated successfully, but these errors were encountered:
I was reading this article these days and thinking if Flixel Community could benefit from multi-core processors.
The idea is to identify workloads that can be performed in parallel using Workers, such as physics and path planning. It would be awesome if Flixel could check for Workers availability and, if that's the case, take advantage of it, transparently.
A physics plugin based on Workers, for instance, would be a hell of a feature to justify the implementation of some sort of Workers API.
The text was updated successfully, but these errors were encountered: