Asynchronous raycasting and pathfinding

Hi,
I've just downloaded the new Unity (beta) 2018.1b version and I'm wondering how to use all the new fancyness introduced, like the two things mentioned in the topic. Can I just put pathfinding and raycasting code into IJob.Execute method definition and it will just work, or are there some more specialized structs I need to extend in order for those two to work (like IJobParallelForTransform)?

 

I guess you mean next beta release? (I'm already using 2018.1 beta)

And as for the raycasting part - roadmap mentions it as a part of 2018.1 release, so by saying "future versions of Unity" do you mean some next beta, or, say, Unity 2019.1?

 

This is a bit disappointing, as the roadmap showed everything on track :/

 

This is great news

 

any example?

 

Thanks~,and how about pathfinding.

 

Has anyone figured out how to do pathfinding with the new NavMeshQuery? I god to the point where you get the path result ( NativeSlice of PolygonIds ) and have no idea how to proceed further.

Spoiler: Code

Code (CSharp):

1.  
2. var start = query.MapLocation( currentPos, Vector3.one * 3f, 0 );
3. var end = query.MapLocation( targetPos, Vector3.one * 3f, 0 );
4.  
5. var status = PathQueryStatus.Failure;
6. status = query.BeginFindPath( start, end );
7.  
8. if (status != PathQueryStatus.InProgress)
9.     return;
10.  
11. int performedIterations = 0;
12. int maxIterations = 1024;
13.  
14.  do
15.  {
16.      int iterations;
17.      status = query.UpdateFindPath( 32, out iterations );
18.      performedIterations += iterations;
19.  
20.     if (status == PathQueryStatus.Failure || status == PathQueryStatus.OutOfNodes)
21.         return;
22.  
23. } while (status != PathQueryStatus.Success && performedIterations < maxIterations);
24.  
25. int pathSize;
26. status = query.EndFindPath( out pathSize );
27. if (status == PathQueryStatus.Failure)
28.     return;
29.  
30. var array = new NativeArray<PolygonId>( pathSize, Allocator.Temp);
31. var path = new NativeSlice<PolygonId>( array );
32. var nodeCount = query.GetPathResult( path );

 

There is quite a bit of work to do for that api to be usable. This post illustrates what the portals represent and then an algorithm for creating a straight path using them.

http://digestingduck.blogspot.com/2010/03/simple-stupid-funnel-algorithm.html