Funnily enough, from my limited testing of BRMin/Max I too ended up with 500 BRMax for one or two cars and sometimes one car up to 1250 (when I really didn't like a certain driver's ability and wanted to make him a laughing stock
). I never liked really BRMin at all though and rarely if ever used it as it always seemed the more artificial looking of the two behaviours.
What stopped me using it eventually was the still noticeable effect it had on CC results over time, because back then (and still now) I was working hard on an enhanced Performance Calculator spreadsheet to automatically generate driver-specific PFs for each race of each season and I didn't want to have to accurately feed the effect of the additional variable into my already cumbersome grip calculation formulae to compensate. Basically, even at low levels such as 500 I felt BRMax tended to skew the accuracy of my PFs when considered over several seasons and then one day when I left it out altogether I realized it was actually pretty hard to tell the difference on the track anyway. And then ErrorChance came along, offering another layer of complexity...
I'll probably come back to ErrorChance soon but for now I don't use either. Not sure that makes any difference to anyone else but that was my story.
Good luck finding that sweet-spot. It's probably out there somewhere!
ParisHL Wrote:
-------------------------------------------------------
> ErrorChance is similar (some drivers are more
> prone to mistakes than others) but really affects
> the amount of "offs" the driver may have during a
> session. I think if BRMax is set too high, then
> drivers will obviously brake too late for certain
> corners and run wide or crash out which isn't
> because of ErrorChance but more because the BRMax
> was set too high. By tweaking BRMin/Max too be
> much smaller, it'll still encourage overtaking and
> inconsistent lap times with the occasional lock-up
> without making it super obvious. That way we can
> differentiate between a driver being inconsistent
> and being error prone.
>
> So from the bit of testing I've done, BRMin/Max
> works well for overtaking moves and over one lap
> such as qualifying where an inconsistent driver is
> less likely to have a lap time that's
> representative of their skill level.
>
> We are still trying to tweak the numbers to a
> realistic level where the number of lock-ups and
> mistakes is similar to real F1, but I definitely
> wouldn't be putting those ratings over 500 for
> now.