A funny but unfortunately accurate summary of your race. a Richard said, you will come back in Pikes Peak.
I am happy with the results: the official data perfectly match my local simulations.LVDH wrote: ↑04 Feb 2019, 12:21A funny but unfortunately accurate summary of your race. a Richard said, you will come back in Pikes Peak.
I released the results:
https://mantiumchallenge.com/results-mvrc-daytona-2018/
There was an issue with convergence on some of the cars. This forced me to run some of the cars with different mesh settings. I did it in a way that the results did not get too distorted in the overall lap times. The gaps between some cars are a bit inaccurate now though. The main two cars affected were JJR and Variante. They were driving in their own league, though. I think the issues are because of their designs which forces very fast air through relative small gaps in the floor to the ground area. Today I will look a bit deeper into this. Probably I will have to release an updated version of MantiumFlow tomorrow, which will then be the standard for the last race. If you guys like, I can delay the last race for one week.
Congratulations, you improved your downforce also if compared to last year rules
Yes, his car is possibly now the new benchmark. I think it is easier for him to fix the cooling thing than for Variante to improve his downforce as much as he needs now. But this would only be true if we would have a normal last race. We will obviously see very different cars in Pikes Peak. So who knows, maybe the old and beaten CAEdevice car will like the new wings most, or somebody else entirely will climb to the very top (fastest). One way or the other, the championship is very open now, which is cool considering how it started.
It is too late, I should have sold them after the first race
Ok, tomorrow I will repeat one of the simulations done for Daytona, so I can compare the results.
Yes, Virtual Stopwatch is now updated for the new CoG, link; VIRTUAL STOPWATCH