Liam

 Validated. Green is src, red is dest. LanesBackward relates to dest > src lanes.

 Example of bidirectional road with a `width` set (gap in the middle)

>  > > Validated. Green is src, red is dest. LanesBackward relates to dest > src lanes. I had the fuckers mixed up. Validated it's wrong lmao

 Fixed and validated src and dest nodes order. Blue is the node I'm passing to `GET_CLOSEST_ROAD` Green is src Red is dest

The purple line is the node heading though which is a bit weird, so maybe it's returning links connecting to the node in the opposite direction? Will check CW

 Can confirm. src and dest were fine before. The node you're testing against is sometimes the src, sometimes the dest

Unsure that `n` should be considered as such. It's only ever 1 in the rockstar scripts. In GTA IV it was 1 or 2 depending on the location of `pos`

> I don't have much of `CPathFind` documented, so these are my _rough_ notes on this batch of natives. Unsure how valuable they will be to continue your research: >...

> 0x132F52BBA570FE92: p3 looks like a node radius and is used to supplement n, likely leading to your "A bit broken as it returns a random edge after n" comment....

@gottfriedleibniz here are some examples of enumeraing "`n`" until the response is `0` (`p3 = 0.0f`). To me it looks like it gives relating nodes, like upcoming junctions/joins etc. What...