[Applies to build 1130 and later] See here https://docs.studio-397.com/develop...neral-tracks/track-limits-track-configuration
Thank you so much! We need more guides like this. As I wrote on the news section: We need full documentation and details about new cuts system, how to properly set it up in our custom tracks and cars, every parameter and configuration needed. "Hey, you just choose default or strict" is not enough for league admins, please take a little time for that, like the perfect explanation we got in track dev forum about pit exit detection.
"In order for these connections to not be made automatically, add an invisible wall at AIW generation time along the white line, with a face only facing the pitlane." Do we need to temporally activate this invisible wall each time we do any edits to the AIW? Think this is where I'm going wrong. My pit exit branches are keep coming back when I save and reload track even if I'm not editing anything on the pitexit.
Had the same problem with the coming back branch connections. redapg gave me the hint to place the wall a bit going through the surface and then hit "find corridors". Voila, the branch connections are gone
And you did the "find Corridors" with an added Wall Mesh, that separates the Pit Out Waypoint Section along the white Line? And did you, to ensure that the Wall really separates the main from the Pit Out Path, stick the Wall a little bit through the Surface? If you do that and reload the Track and don't do "find Corridors" again, the Connections normally stay disconnected.
I just tested locally and they do seem to regenerate at least in some circumstances. I need to look into it
I opend a Track from the Workshop (Road Atlanta) to edit the cut corridors. Due to this I also edited the pit exit cut detection. I removed the branch connection and adjusted the corridors. The next time I load the track again all removed branches are back. I didn't hit find corridors. Because it's not my track I don't have any Temp Wall. Ofcourse I could do one but the only thing I would to point out is that they get reconnected. Maybe the problem is that I only edit the cut corridors and not also the collision corridors. Which I suppose are different when there is a temp barrier during the find corridors process.
The Wall is necessary, to completely separate the main from the Pit Waypoint Path, when you do the "find Corridors". Editing the Corridors by Hand is no good Idea in this Case, i guess. EDIT: And i would suggest to give the Wall a Thickness of maybe 20 cm.
That's not a viable solution in many cases. It will give penalties if you use the other side of the line on the race track, which is usually legal.
@Alex Sawczuk Is the pit exit cut detection also dependent on the values for cut detection in the gdb?
Thanks for the Clarification. The Problem with this, like with other Features too, is the Lack of precise Information that we Modders get. If we would exactly know how the Code handles it and how exactly it has to be done, Things would be much easier for us. In this Context, may i also ask here, what the following GDB Entries, that you did mention HERE, exactly do? It's CutNextLapThreshQualifying CutNextLapThreshPractice CutNextLapInvalidDist
I said I would explain correctly once I have time. At present I'm trying to fix more pressing issues, sorry.
So yes there is an issue it needs code. And there are still some things that need fixing before I share full details about how to customize things, because I don't want people customizing them one way, and then another way is required afterwards.