@Nellix82 Hmm interesting, I guess they could still be using rasterization to determine asphalt temperatures. It wouldn't be 100% true to life accurate but it would certainly be a step up from what we have in F1 series. Sorry, I jumped to a conclusion on that one, I'll have to look into that one more and see what tech they've got going on behind the scenes.
For the race distances, scaling Tyre deg to a certain distance shouldn't be an issue, it's just a matter of if they want to code the AI to understand the potential tyre strategies based on that distance. In this case it was just much easier to slip 35 in because there's very little difference between 25 and 35. Been a while since I've a run 35%er but if I recall most cars basically just go an extra 1 or 2 laps on soft and then like 3ish more laps on the medium/hard. 75% would probably bring 2-stoppers in to play which is why they avoid trying to tackle it.
Didn't have a lot of spare time today so could only spare a quick search but it doesn't seem as sophisticated as either of us might have thought. Track temp appears tied to time of day, which might work of endurance racing, but would be hard to apply to 1 1/2-hour F1 races. I know the pit pox telemetry will show temperature changes but that's usually just a sign of rain coming or going.
I'm not an expert coder by any means, but the best way to implement something semi-realistic without blowing out everyone's GPU would be to divide the track up into say 10 parts and then basically created a rasterized version of raytracing to determine how much light(heat) each section of the track was getting which would generate a tyre wear multiplier for that segment of track. driving smoothly over a high multiplier segment of the track would obviously result in lower wear than driving recklessly over that same segment.
Obviously this isn't completely "dynamic", but I also don't think it's unreasonable given today's hardware capabilities.
Community Manager
