After updating to v3.0.16 today, it looks like some gauges visibly show some placement constraints.
Maybe some debug code still in there?
My dashboard gauge looks like this:
v3.0.16 Problem with Dashboard
Moderator: LT401Vette
-
- Super MS/Extra'er
- Posts: 12733
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: v3.0.16 Problem with Dashboard
3.0.16 did contain a fix where gauges pointing at an invalid OutputChannel were not displayed as such, now they are again...
So it looks like you have a gauge that is pointing at an OutptuChannel that doesn't exist.
Go into designer mode, select the crossed out gauge and set it to a valid OutputChannel.
So it looks like you have a gauge that is pointing at an OutptuChannel that doesn't exist.
Go into designer mode, select the crossed out gauge and set it to a valid OutputChannel.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Re: v3.0.16 Problem with Dashboard
yup -
the component was just used for showing the digits on the dial and didn't specify an input - after selecting engine speed it cleared the framework.
Thanks.
the component was just used for showing the digits on the dial and didn't specify an input - after selecting engine speed it cleared the framework.
Thanks.