I am using a AStar Project, that relies on multithreading.
I am now finding I pretty much am going to need to get into multithreading. … or jobs.
Can I run multithreading on AStar and jobs on everything else, or is it globally one or the other for the project?
Unity Jobs and System.Threading (multithreading) are two different technologies with a somehow similar output: allowing to run code in parallel.
The difference is that Unity Jobs uses the same thread pool that Unity uses for its own tasks, rather than a separated one, this reduces context switch between threads. Also, Unity Jobs includes a dependency system to avoid any kind of deadlock.
You can use both approaches in the same project, preferring one over the other in different parts of the project. Nothing forces you to choose one globally over the other.