Distances - what to believe : onboard computer or debugRoadLenght ?

Hi there,

I was putting marshall towers along my tracks, 1 each Km helped with the onboard computer. And I realized that according to it ("total distance", which I reset at each new marshall tower), the Nordschleife on my map is 20,45Km. Real life is 20.83 Km.

And then I draw 1 decalroad on top of the existing ones, remaking the entire lap with it. And there, debugDecalRoad tells me that my track is 20,76 Km. That obviously fits me better than 20,45...

I checked on the gridmap : I draw a 1 Km straight decalroad and drove on it. On board computer gave me values ranging from 980 to 990m.

Which one do I believe ? debugRoadLenght on on-board computer ?
Thanks !

 

Decal road.

Onboard computer calculates distance from revolutions of the wheel and that can be off for numerous reasons, even air pressure of tires can affect that.

 

Thanks fufsgfen,

What an intricate way to calculate it. I knew I saw some weird reading once a wheel was damaged
It arouse my curiosity : why not just calculating it from X-Y-Z position of a node ?

 

Devs like being realistic, almost every UI app and game function is forced to be "realistic" by reading sensor data from the car rather than cheating and using values from the game engine. Obviously if you need to be precise use debug.

 

Game vs simulator, approach is different, for simulation to work like reality, methods of reality must be used as much as possible.

But funny thing, pretty much every game that has Simulator in their name, are not really good simulators at all, but very simplified games, odd things of life.

 

Nice,

I thank you all for the little lesson !