Feature Request RaycastCommand.ScheduleBatch with List<RaycastCommand>

It happens to me that I don't know the amount of raycasts upfront when scheduling the job. The raycasts are built by different job, which is not finished yet.

I'm left with two options:

1. Synchronize on the main thread, read output of the previous job and Schedule raycast job
2. Do conservative estimate of amount of raycasts needed and schedule raycast with preallocated array
   (which will be filled by job)

Both approaches are bad, in the first case it introduces extra sync point, I need to find a good place in the PlayerLoop where I should wait for the job and schedule raycasts.

In the second approach I might submit a LOT of empty raycasts, which get skipped by physics (zero length). I haven't tested the performance implications of that yet. The problem here is the worst case. In average cases, I might need 10 raycasts, but in extreme case when there are a lot of enemies nearby player, it can go to thousands. Doing 990 "empty" raycasts every frame just because I might need 1000 sometimes seems bad.

Proposed solution
Allow us to schedule Raycasts with RaycastCommands in List, so the actual number of raycasts can be determined when starting the job.

Alternative might be to still use arrays, but supply the count parameter as NativeReference<int> for example, instead of Array.Length.

Another alternative would be to allow scheduling the raycasts job from other job. (I think scheduling job from job is not allowed for good reasons now).

Same applies for SpherecastCommand and possibly others.

 

Oh, actually allowing to schedule raycast job from other job might be ideal case.
Consider this use case.

Code (CSharp):

1.     [BurstCompile]
2.     public struct RaycastJob : IJob
3.     {
4.         [ReadOnly] public int MinCommandsInBatch;
5.         [ReadOnly] public NativeReference<int> CommandCount;
6.         [ReadOnly] public NativeArray<RaycastCommand> Commands;
7.         [WriteOnly] public NativeArray<RaycastHit> Results;
8.  
9.         public void Execute()
10.         {
11.             RaycastCommand.ScheduleBatch(Commands.GetSubArray(0, CommandCount.Value), Results, MinCommandsInBatch).Complete();
12.         }
13.     }
14.  

There are no issues with dependencies, because job is scheduled and waited immediately.
I've read in the recent blog post, that Job system internally allows scheduling jobs from other jobs.

Current result
UnityException: ScheduleRaycastBatch can only be called from the main thread.