@runevision@mastodon.gamedev.place
Post #3169272
2026-05-07 13:44 UTC
@aras@mastodon.gamedev.place For one because I'm extensively starting threads from other threads while Unity's can only start threads from the main thread. Having to wait for the main thread queue for each new chunk task would be a significant overhead in both performance and code complexity.
For another because in my experience, Unity's job system is not geared towards long-running background tasks AT ALL. The manual directly says "Avoid using long running jobs".
Replies (1)
-
@slembcke@mastodon.gamedev.place 2026-05-07 14:18
@runevision@mastodon.gamedev.place @aras@mastodon.gamedev.place Yeah, that’s what I’ve run into every time too. It’s meant for little bits of task threading, but every time I’ve reached for it it can’t actually do what I need. No sub tasks, no object refs, etc.