Excessive track limits - car width for draft purposes???

MileSeven

MileSeven

Registered
Weird.

We’ve been racing iterations of two cars I’ve been working on long term.

Tonight, we started getting excessive numbers of track limits - didn’t matter if the server was set to Default, Lenient or whatever. Most of the times, the track limits were automatically converted to drive-thrus - no award of points, just immediate drive-thrus…

We abandoned that track and tried another - same issue…

I did make minor tweaks to the drafting settings of one of the vehicles in between last weeks races and tonight - but nothing radical. I don’t recall changing the same settings on the other vehicle and it was having exactly the same issues.

Any ideas?
 
Sounds weird indeed.

Was anything else than the Drafting changed in the Car Mods?
Normally Things like that (Cut Detection and Penalty Points) doesn't change by itself.

And have there been visible Cuts or was it more the Problem that you e.g. could not Cut more than 1 Time, to get a drive through, like it's normally the Case (of course depending on the Settings)?

And were the same Tracks used before, without that Problem?
 
redapg said:
Sounds weird indeed.

Was anything else than the Drafting changed in the Car Mods?
Normally Things like that (Cut Detection and Penalty Points) doesn't change by itself.

And have there been visible Cuts or was it more the Problem that you e.g. could not Cut more than 1 Time, to get a drive through, like it's normally the Case (of course depending on the Settings)?

And were the same Tracks used before, without that Problem?
Click to expand...
We have used the tracks before without any obvious problem. We reverted to the Oulton Park 2015 track after initial problems at the non-Steam '60s Oulton Park' and had the same issues - the 2015 version of the track has not been updated on Steam since 2022 and we've used it many times with other vehicles.

I'll need to check what other drafting changes (if any) I made.

I'm doing some more work on the cars today and tomorrow and will check if the problem extends elsewhere and (hopefully) under what circumstances.
 
I don't know your Workflow, but do you maybe have a Backup of the Version from before the Draft Update?
Maybe a rfcmp of a former Version?
Or at least a Backup of the Files that you did modify?

If not, when you check the current Files (probably only the hdv File?) check it for "invalid" Letters or Numbers too and also for Commas and Dots at wrong Positions.

What still sounds strange, is, that a Entry in the HDV could be the Reason for strange Track Cut Behaviour...

And as it sounds too, the Tracks don't seem to be the Problem.

Good Luck for your Search. :)

EDIT I forgot to mention not closed Brackets for e.g. Setting Ranges, that also can lead to strange Things happening.
A quick Test is to count all opening and all closing Brackets.
 
Last edited:
redapg said:
I don't know your Workflow, but do you maybe have a Backup of the Version from before the Draft Update?
Maybe a rfcmp of a former Version?
Or at least a Backup of the Files that you did modify?

If not, when you check the current Files (probably only the hdv File?) check it for "invalid" Letters or Numbers too and also for Commas and Dots at wrong Positions.

What still sounds strange, is, that a Entry in the HDV could be the Reason for strange Track Cut Behaviour...

And as it sounds too, the Tracks don't seem to be the Problem.

Good Luck for your Search. :)

EDIT I forgot to mention not closed Brackets for e.g. Setting Ranges, that also can lead to strange Things happening.
A quick Test is to count all opening and all closing Brackets.
Click to expand...
Thanks.

Yes, I’ve got access to all of the recent iterations of the rfcmps and try to keep folders containing the individual MAS’s for each version until such time as we are happy to set a new baseline version.

One of our members will hopefully be able to load a server today with the same cars/track to rule out any problems with my server (the only change to which recently was altering the individual session start times in the JSON).

The odd thing is that I’m fairly sure the track limits issue was happening to one of the two vehicles despite us having run that version without issue in the previous week. It’s just possible that the issue was already present but the track limits of the track we ran a fortnight ago were pretty loose anyway and the issue with the car(s) was simply not a factor.

Anyway, I have time today to look into this rather more closely.
 
Quick update - not much help but for completeness...

For various reasons rooted in tyre development, I rolled back the two vehicles to slightly earlier versions and started again. We didn't have any problems racing them at a totally different track on Tuesday and although not much testing took place, no super-obvious issues at Oulton 2015 online.

So:
i) Hopefully the problem has gone away but
ii) I still don't know what was causing it.
 
gerald gandeboeuf said:
Is there a link to my app for tire modifications?
Click to expand...
Do you mean - has your app caused the issues?

It sounds unlikely but I don't think I changed anything else in the vehicles so it's possible (one of them in particular only had tyre changes from one week to the next).

I would need to try adapting tyres with your new tool again and see if the problem resurfaced.
 
You must log in or register to reply here.
Back
Top