PDA

View Full Version : Possible glitch, not major and far from game-appbreaking



Ticondrius
20-07-2018, 13:21
Hi, I'm a first timer here and just wanted to say I've rapidly become addicted to your CrewChief app.

After updating to Version 4.9.4.2 my crewchief seem to have less knowledge about track limits in Project Cars 2, specially on the first outlap he tells me half way through the lap that I cut the track and my laptime will be invalidated (he does this regardless whether I do actually cut track or not :P )
It's in no way a game-appbreaking thing, but it's a bit annoying from time to time.

I wouldn't say this should be on the top of your to-do list, but if noone tells you, you wont be aware of the glitch/bug

Thanks again for this awesome app and your continued support for it, and best of luck in your coming updates and developments

mr_belowski
20-07-2018, 19:42
Interesting. This is a known issue for r3e (will fix it next week) but I've not heard this behaviour in pcars2. I'll investigate when I'm back from holiday

Ticondrius
21-07-2018, 17:22
Interesting. This is a known issue for r3e (will fix it next week) but I've not heard this behaviour in pcars2. I'll investigate when I'm back from holiday

Wow, that was a quick response!

thank you! hope I didn't mess too much with your vacation and that your having a good time :D

inthebagbud
27-07-2018, 20:11
I can confirm I have this also in Pcars 2 - I started driving a new track Oscherslaben B and just though it was an error with the track itself - it happens to me just before turn 4 hairpin

AUSSIEINVADER
01-10-2018, 03:59
Im getting to grips with crew chief for Automobilista, but find track limits to be off most tracks.
is there a way to teach where track limits is for crew chief?
i get " cmon rob thats track limits" but in game its not...?

mr_belowski
01-10-2018, 16:59
maybe Reiza has added more surface types or something. I've reversed the app logic so all wheels now have to be on grass or gravel for this off-track stuff to trigger. This will make it less likely to trigger, and if a new non-racing surface exists that the app doesn't know about it won't trigger the cut detection. Which isn't ideal but it's better than false-positives.

Will be in the next release