imagine the shock all my friends would have the moment they see this LMAOOO they never saw this coming

thats the thing, i wanted to parallelize mainly the raycasts involved to increase performance where collisions are involved but that didnt end up happening

this causes certain issues for me where i cannot utilize it properly in renderstep ops such as playermodule, which is the exact thing i wanted out of something like this

what i meant by on-demand is doing all of the work going parallel to serial to parallel without messing up the order on the resumption point. parallel work is done on the rpws job which skips past the initial resumption point and threads that are deferred on that point

please work

im killing librewolf for this what is this :sob:;:;:

i disagree, parallel code is more of a defer after a defer with parallelization benefits. i used a single actor in this example which is not rly representative of the entire system but im showing this to make it clear that parallelization is not happening on the spot

its not really at the exact same resumption point like heartbeat or postsimulation. it skips ahead to after deferred threads which is part of why im reluctant on going with parallelization

i smell exaggeration i need evidence stat 😡😡😡😡😡😡😡😡

i thought parallel context was reserved for a special resumption point whaaaat

finally IT CAN ACT AS BOTH AN EASILY MOVABLE CONTAINER AND A CAMERA YEAHHHHHHHHHHHHHHHH HHAHAHAHA IM SO HYPED

WHAT IS THIS?????????