07-06-2021, 07:34 AM
Hi,
This is fine, but only works if you have Burst, Jobs, and other dependencies installed. Code outside of a specific backend should compile and run with no external dependencies of any kind (as you can't assume which backend the engine is using).
I've been working on moving the entire render/mesh updating pipeline to backends. In most cases this allows to merge data from different actors into the same array, then schedule a single job per solver and work in parallel over multiple actors at once. This is similar to what constraint batches already do, results in better performance in all cases and works for any backend. This is a quite large change though and currently R&D, so it won't be available until Obi 7.0.
This is fine, but only works if you have Burst, Jobs, and other dependencies installed. Code outside of a specific backend should compile and run with no external dependencies of any kind (as you can't assume which backend the engine is using).
I've been working on moving the entire render/mesh updating pipeline to backends. In most cases this allows to merge data from different actors into the same array, then schedule a single job per solver and work in parallel over multiple actors at once. This is similar to what constraint batches already do, results in better performance in all cases and works for any backend. This is a quite large change though and currently R&D, so it won't be available until Obi 7.0.