Good catch. Will update OP as always. đź‘Ť
Also stumbled on more YouTube dash view videos so will put stuff here and there too.
BMW Z4 GT3 race car rev counter in car reads approx 2000 RPM too low - reads 7000 when doing 9000; 6000 at 8000, etc.
I did notice that before, but I'll let you know when I might take some more research about real life spec like Chevrolet Volt use gas engine as generator for expand range after battery is deplete. BTW, I notice when I stop for gas engine; however, gas engine didn't recharge battery unlike the Prius, CR-Z, and Insight did. And there one more for you to know, there is plug for the Karma, but when I enter pit stop show only fuel refill not with battery for recharge.
Hmm... I think I did found another car like Honda/Acura NSX 2013 concept has fuel gauge won't work plus odometer and battery meter are missing in game while last year's trailer show odometer and battery meter appear between 1:36 to 1:40, here is link:
Would also like to add that the BMW M5 now has a HUD speedometer, but displays speed wrongly (something to do with the first digit I think). Will check exactly how its messed up later.
Having just tested that out, here's everything that's wrong with it:
1.) When you're stationary, the HUD shows NN1 km/h
2.) When you're doing 10 kph, it shows N21 km/h.
3.) At 89 kph, it's going to reset from N99 km/h to N90 km/h.
4.) At 90 kph, it resets from N90 km/h to N00 km/h (not NN0 or NN1!).
5.) It's going to go up to N09 km/h (98 kph).
6.) At 99 kph it shows N00 km/h again.
7.) At 100 kph it shows 211 km/h.
8.) At 288 kph it shows 399 km/h.
9.) At 289 kph it resets to 390 km/h.
10.) At 290 kph it resets yet again, to 300 km/h.
11.) At 298 kph it shows 311 km/h.
11.) At 399 kph it resets to 300 km/h again
12.) At 300 kph it shows 411 km/h.
13.) At 308 kph it shows 419 km/h.
14.) At 309 kph it resets to 410 km/h.
15.) At 310 kph it shows 421 km/h.
16.) At 318 kph it shows 429 km/h.
17.) At 319 kph it resets to 420 km/h.
18.) At 320 kph it shows 431 km/h.
...
871.) At 388 kph it shows 499 km/h.
872.) At 389 kph it resets to 490 km/h.
873.) At 390 kph it resets to 400 km/h.
874.) At 398 kph it shows 409 km/h.
875.) At 399 kph it goes back to 400 km/h again.
876.) At 400 kph it shows 511 km/h.
There is something interesting about this one:Go home speedometer, you're drunk.
That's just... wow. How can that even be so wrong? What's more, the speed is displayed fine in the dial, and in the game's HUD as well! How hard can it be to make one appear in the windscreen, and how did no-one on the development team notice it's so heavily broken?
There is something interesting about this one:
Look at my post again. The HUD is obviously broken beyond belief, but there is a somewhat/clearly a ('a somewhat' if what I write below this point is false, 'clearly a' if true) regular pattern at what it displays.
The car's HUD is pretty 'sensitive', as in, it's far easier to make these tests at high speed as it changes slower. It's likely that what I found at over 300 kph repeats all the way from 100 to 300 as well but I may not have realized that as I wanted to see how it behaves at higher speeds. Also I wanted to see how it behaves transitioning between hundreds.
If my pattern 'theory' is correct, it must be a matter of simple programming. If PD can get other cars' HUDs (like the one in ZR1 C6) to display speeds properly, it's just an issue someone must have forgotten to fix.
(The post above)
If I find any more, I'll be sure to contribute.Good find. đź‘Ť
Now I wonder if it's a flaw specific to the car or a game engine limitation/oversight.
(Edit: Wow, almost a year since the last post. My OP has always been updated semi-regularly if anyone's curious. Seasonals are great for building car collections for reference.)
Go home speedometer, you're drunk.
That's just... wow. How can that even be so wrong? What's more, the speed is displayed fine in the dial, and in the game's HUD as well! How hard can it be to make one appear in the windscreen, and how did no-one on the development team notice it's so heavily broken?
def hud(speed):
speed = str(speed)
digit_list = ["1", "2", "3", "4", "5", "6", "7", "8", "9", "0"]
digit0 = "N"
digit1 = "N"
digit2 = "N"
if len(speed) > 2:
digit0i = int(speed[-3])
digit0 = digit_list[digit0i]
if len(speed) > 1:
digit1i = int(speed[-2])
digit1 = digit_list[digit1i]
digit2i = int(speed[-1])
digit2 = digit_list[digit2i]
print("%s%s%s" %(digit0, digit1, digit2))
So it's basically every digit being one higher than it should be? Proof that you always should proofread your work*snippity snip!*
(The post above)
Will check each car with a functioning clock later.Any clock in particular? Checked a few and still wonky.
Thanks for the fuel gauge tip.