2.7.3 released 14.10.2026
New:
Fixes:
The Dash Data values are saved to the hard drive only if I press F2, not immediately after “setvalue”. I am using the Realdash 2.6.9 version from the manufacturer (Falcon S.)
Yes, it is not feasible to save every time after value is set. It is too easy to make a trigger that will set those values hundreds of times per frame, that would kill the filesystem pretty quickly.
2.7.3 may have an issue with all network connections on devices/computers without local TLS certificate. We are currently building a 2.7.3-2 update to fix this issue. Should be available soon.
I turn off the car, and after the dashboard wakes up, the old values load. Then make a special ACTION TYPE to save them — what are they even for then, if you need to remember to reload the skin every time after changing them?
They are saved at the app exit. I’m just building 2.7.3-2, I will take a look if save can be made more frequent.
Yes, thank you in advance! I never exit the app — it’s like a launcher. If I immediately reboot the dashboard, they don’t save.
2.7.3-2 is now submitted to Microsoft Store and Google Play Store. They should be available pretty soon. APKs are updated in My RealDash downloads section.
Hi. I tried to download an animated WebP and I couldn’t do it. The system returned an error. I’ll add a simple picture here.
This is a 31-frame animation at 1920×1079. Its compressed size is only 1.43 MiB, but loader tries to cache about 245 MiB of decoded frames and rejects it as too memory consumption heavy. We’ll investigate if we can loosen that limit.
Just a note, both apng and webp are extremely memory consumption heavy. While animated gif can be decoded “on the fly” to save on memory consumption, its not feasible to do frame decompressing on apng or webp during the runtime of the animation.
I understand you. I know that WEBP requires a lot of computing power. This is described in the format specification. However, it works in browsers so that it’s an easy thing to do. It turns out that the one who has to save memory uses it more than a weighty GIF. This is understandable, because the machine needs to process only 256 colors in the case of Gif. In the case of WebP, there are millions of colors. But how damn beautiful it looks compared to a Gif)))