Video and Gif animation playback speed can be controlled with Math.
Trigger compare operator ‘value changed to’.
Simulation mode produces some text data for common inputs.
New Action: Load Recent Dash.
Data Multicasting is able to use CAN connections to share data.
Fixes:
Hold value action not resetting value if button press was canceled.
Invalid checksum on configuration for Waveshare and ‘Type 1’ CAN adapters.
Each gauge in container now has independent fade animation value.
Graph gauge mask image.
Global action target gauge name is not set to NONE if gauge is not found on current dash.
Android: Immersive mode restore on some Xiaomi devices.
Android: Crash on JNI handling.
Android: GPS not restarting if ‘Provider Disabled’ received from OS.
Linux: Video gauge looping playback.
OSX: Window resizing issues.
NOTES
Gif animation playback rate can be adjusted with ‘Look’n Feel->Special->Playback->Playback Rate Math’ option. It accepts same formulas than Gauge Math and should produce a factor for playback speed (1.0 normal speed, 2.0 double playback speed etc.). For example, try something like ID37/1000 to adjust playback speed per engine RPM. This same control is also available for Video Gauges, but result may vary as videos are hardware decoded and playback rate may not be accurate between devices.
Each gauge inside the container now has their own independent fade value. Previously, the fade value of the container was set ‘as-is’ to contained gauges. From this version onwards fade of the contained gauges is calculated as container fade * gauge fade. This allows more flexibility as gauges inside the container can have their own independent fade.
The ‘Triggers and Actions’ view has ability to filter the triggers and actions based on inputs they are using. For example, enter ‘dummy 03’ into the search box will include any Trigger/Action that is using Dummy 03 input, regardless of the trigger/action name. With Actions, you can also use attached gauges name for filtering. Hopefully this will help find/organize your Triggers and Actions.
Data Multicasting can now share data between RealDash instances that are connected to same CAN bus. All numeric and text values can be multicasted over CAN, including inputs. Currently album art and navigation instructions cannot be multicasted with CAN connection. Multicasting requires 2 free CAN ID:s, of which first one can be configured at Data Multicasting Screen, and another is previous +1.
Hello friends. I have identified some issues that need to be explained. And so: if the skin was created in an early version of the application and it has triggers with “hide” and “show” actions, then in the new version of the application all “show” actions are no longer performed. let me clarify that I am manipulating containers, as mentioned in the update description. I tried to reduce the degree of smoothing of the Sensor and container to 0, but it did not help.
Show/Hide Gauge uses Fade internally, latest version multiplies gauge fade with its container fade. Previous version set the fade of contained gauges to same value as their container. If old dashboard used container fade, it could lead to the situation where gauges inside container have fade as 0, and they do not appear. You may need to update the dashboards ‘re-set’ contained gauges fade to 1.
The Current Hidden Container inside layers won’t show, only the Visible Container work with Hide/Show Action. the hidden containers contained elements isn’t showing.
We have multiple layers within each hidden container, but each Show Action can only handle one input. Is there a way to reset or reveal all hidden gauges with a single action?
To be honest, I’m a little confused. because every person who updates the app will receive all the previous skins in non-working form. And I’m even afraid to imagine this Sisyphean work that would fix Every skin for every Person.
Each skin can have 10 or more triggers with the fade action. and there can be hundreds of Skins. I beg you with all the saints. let’s remove the multiplication by 0 . or cancel this feature altogether. because it has no practical application other than difficulties! please be understanding. a lot of work will go down the drain.
Even I re-set the hidden Gauges inside the hidden Container, when you restart the app / open Themes Gallery, the hidden gauges recently shown keep hidden again. I hope this issue resolve, I hope there a old version link downloadable for desktop
I’m sorry, I probably already annoyed you today, but there’s one more problem. If the skin was edited in 2.5.7. then it can no longer be opened in the older version 2.5.6. and lower. The app crashes immediately and gives an error!
We are building 2.5.7-2, on which Show Gauge action on container also sets the fade of child gauges to 1. That should fix the compatibility issue. Fix should be live soon.
Currently, do not save dashboards on version 2.5.7, as they will not be compatible with older version. This will be also fixed in 2.5.7-2, out as soon as possible.
2.5.7-2 has now been uploaded to Play- and Microsoft Store. Other versions will follow shortly. Fixes:
Saved dashboard files retain backwards compatibility for older RealDash versions
Show/Hide for container affects gauges inside the container.
Our sincere apology for everyone who was affected by these issues. This was pretty bad oversight from our part, and wish not to repeat it.
But in life, mistakes happen. And will also happen in the future. I personally appreciate that you are able to report issues with new version so quickly. Quick fix would not have been possible without your help.
Here is also a direct link to Android 2.5.7-2 Playstore APK, just in case Play store review takes longer than usual:
unfortunately, the problem is not the availability of the file system on some android devices. please consider delaying the start for 1 second, it seems to me that this will completely solve the problem.
