Cool. And would it in the future also be possible to enable and disable elements at the user side? So I can choose to have the complete dashboard or have the speedo or laptimes only? Would be lovely to have a MoTeC replica design, I would gladly create some design for ya.
Which device/browser? Are you able to clear the browser cache? Have a feeling the faulty script is still cached on your device.
Speedo and rpm aren't woking for me. Neither do the oil temp, oil pressure and water temp. Tire temps are extremely high (200-600°C). Tyre temps (inside, outside, middle) don't change. I'm using Windows 7/Newest Chrome version.
Did you clear the browser cache as there was a bug in my first release? Did you update the software to v 1.1? The temperatures on the side are disk brake temperatures not tire. Maybe they are not celcius need to check the api
I downloaded it one hour before my post for the first time. So it shouldn't be a cache issue and should be version 1.1, but i will try it tonight. I didn't realize that the other temperatures are brake temperatures - my fault
no worries...the brake image is not very big and clear anyway! if you get the same problem tonight....open it in Chrome...press F12...then click on Console as shown in image below and send a screen shot here so that we see if there is a script error. Thanks!
Nice. But I'm curious: how can I verify that information presented on the dashboard inside the simulator itself? (tire temps, delta team?) Only for anyone who uses a dashboard?
Post a screen shot like I described here pls https://forum.sector3studios.com/index.php?threads/r3e-web-dashboard-released.2317/page-2#post-23068 Without any logs/screen shot, it is impossible for me to know your problem. Cheers
Ok it seems like tyre temps are working today. But the speedo and rpm does not. In the chrome console i get thousands of errors:
From the error, the car velocity and rev counter values are coming through as empty and thus crashes when tries to draw a null value, Which car are you trying, maybe I can try to replicate the issue here.
Are you by any change in a country where the decimal point is "comma" or maybe your pc is set with "comma" decimal points? Example: 100, 20km/h as compared to 100.20km/h Note the "," and the "." used....
Not sure if that is the issue without testing, but if you can change it to decimal and it will work then I'd know whats the issue and can fix it! thanks