It's broken, photo bucket is blocking remote hosting.machin wrote: ↑30 Jul 2017, 16:55Yes Matteo; it was very tight! Only a few small parameter changes in Virtual Stopwatch or Mantium WFlow would probably reverse the result... I guess this is not too far from reality; the impact of different weather conditions, track temperature, track adhesion (for example if the laid-down rubber gets washed away by rain) etc. could easily provide a +/- 0.05 second (or more) advantage to one car over another... I'm sure Vettel or Hamilton would take a 0.05 second advantage in qualifying gladly!
Andre sent me the completed lap time chart, but he is away today, so I expect the full results will be on the Challenge page sometime during the coming week.
http://i90.photobucket.com/albums/k248/ ... msbjyb.png
I'm doing my first run parallel in 1606+ and 4.1. Small changes to fix CDSavage remarks on my model. The one running on 1606+ went bonkers, Cd is 4.6xE16 already halfway the run. The exact same files seem to be behaving on 4.1.LVDH wrote: ↑26 Jul 2017, 17:06The fix is now up.
The changes between 2017.4 and 2017.5 are mostly a change in OF versions. The numbers will only slightly change, I have not tested extensively as I am running all of your cars for the race.
The differences will not be comparable to the jump to last year as there the major change was in the numerical schemes which affect the results a lot.
About 3 seconds at Monaco, depending on the other factors... you can test it for yourself by selecting between the two engines on the MVRC Virtual Stopwatch:-