Hi folks, I thought I fix a cutting-problem at a certain track. There is a chicane where you can fly through, without the game detecting any cut. And that where the cut lines are reaching until the dge of the curbs. Now I´ve shortend the cut detect-lines, but it does nothing! I´m now in the middle of the road already, but there is no difference! I simply can´t narrow this down! No matter how much I shortend the lines at the certain AIW-points. Any ideas? Thanks in advance, Pete
Check if there are Cut.... entries in the tracks gdb file. If yes, check their values. Especially the value of the line CutLeavingThresh= If that is too high it could be a possible reason for cuts not being detected by the game.
Unfortunately that still does nothing! I´ve put some extreme numbers in, for example 1.0 for CutLeavingThresh= but still nothin..... Here are the lines of the GDB as of now: CutLeavingThresh = 1 // Threshold for leaving track CutJoiningThresh = 0.75 // Threshold for re-joining track CutPassPenalty = 0.75 // Penalty for each driver we pass (this is an inaccurate indicator) CutTimeRatioMax = 0.96 // Start penalizing even if we lose 4% of time CutTimeRatioPenalty = 0.38 // Penalty for fraction of time savings CutSecondsSaved = 0.75 // Penalty for each second saved CutWorstYawPenalty = 1.5 // Penalty for staying under control CutDirectionalPenalty = 1.5 // Penalty (actually reward) for being in wrong direction CutWarningThresh = 1.70 // Threshold for warning (or disallowance of lap) CutStopGoThresh = 3.0 // Threshold for immediate stop/go penalty
Nope. When doing extreme manoevers it does a cut detection. As before any editing. But for that you have to fly far off.
sure: Salzburgring { Filter Properties = rFRS TMOD GTWEC RCC Historics NSCRS IndyCar RMT TCM F2_2012 Attrition = 30 TrackName = Salzburgring EventName = Salzburgring Grand Prix VenueName = Salzburgring VenueIcon = Salzburgring\SalzburgringIcon.dds Location = Plainfeld, Austria Length = 4.255 km TrackType = Permanent Road Course TerrainDataFile=SALZBURGRING.tdf HeadlightsRequired = true // whether headlights are required at night GarageDepth = 2.9 Max Vehicles = 30 NumStartingLights=6 PitlaneBoundary = 1 RacePitKPH = 60 NormalPitKPH = 60 FormationSpeedKPH = 100 TestDayStart = 10:00 RaceStart = 14:00 RaceLaps = 60 RaceTime = 120 Latitude = 47.82398 // degs from Equator (range: -90 to 90, positive is Northern Hemisphere) Longitude = 13.17368 // degs from GMT (-180 to 180, positive is East) Altitude = 685.0 // meters above sea level RaceDate = June 11, 2017 // default date for the race TimezoneRelativeGMT = 1.0 // hours compared to Greenwich Mean Time (should be negative to the West) DSTRange=(67.0, 305.0, 0, 9999) // (start day 1.0-367.0, end day 1.0-367.0, start year, end year); multiple lines allowed CutLeavingThresh = 1 // Threshold for leaving track CutJoiningThresh = 0.75 // Threshold for re-joining track CutPassPenalty = 0.75 // Penalty for each driver we pass (this is an inaccurate indicator) CutTimeRatioMax = 0.96 // Start penalizing even if we lose 4% of time CutTimeRatioPenalty = 0.38 // Penalty for fraction of time savings CutSecondsSaved = 0.75 // Penalty for each second saved CutWorstYawPenalty = 1.5 // Penalty for staying under control CutDirectionalPenalty = 1.5 // Penalty (actually reward) for being in wrong direction CutWarningThresh = 1.70 // Threshold for warning (or disallowance of lap) CutStopGoThresh = 3.0 // Threshold for immediate stop/go penalty SettingsFolder = Salzburgring SettingsCopy = Salzburgring.svm SettingsAI = Salzburgring.svm }
Hi. Everything seems to be correct. I'm not now at home and can't compare with our tracks. The only thing that i see, but i'm prety sure that it isn't the problem, is the format of the CutLeavingThresh. I always use the decimal format Instead of CutLeavingThresh = 1 // Threshold for leaving track I use CutLeavingThresh = 1.0 // Threshold for leaving track But this can't be so silly, no?
I tested it with several numbers of 1.5 or 1.25 for example. And after all I have experienced with .GDB, .AIW and other files this isn´t a thing. But thank you so far anyway! I hope we can find a solution, as this otherwise fine track is not useful for league racing as it is now.
Wild guess... (without seeing cut corridors etc. in devmode) Try zero out CutJoiningThresh value. CutJoiningThresh = 0.0
@peterchen How long is the distance that you are off track, when you cut that chicane? Is it this track? https://steamcommunity.com/sharedfiles/filedetails/?id=892454354 EDIT I have tested it with the above linked track and the cut detection worked at both chicanes. Can you upload a replay, where a cut wasn't detected, that i can see your driven line and maybe can try to reproduce it?
Hi! Jka: CutJoiningThresh = 0.0 seem to do nothing. Maybe a tiny bit better for the first part but hard to tell. Bernd: Yes it is the track from the workshop. I can´t make a video, but I could maybe send a replay file. In the left half of the chicane we can fly about 1,5 meters or more right through it. Right half its more or less the same. On the left half you become a detection after maybe 2,5 meters or so. Hard to tell... We try to held a race with 27 people few days ago and it was for all the same. So I wonder that it´s ok for you! Hard to believe.... Rules I´ve tested is full without DQ
I have tested it a few times only and with cuts that gave me the best advantage, so i maybe didn't meet the line where cuts are not detected. But i did it with the chicane before and the chicane after the start-finish line. Could you post a screenshot from a top view, where the line or area, where no cuts get detected, is marked?