Page 1 of 1

shadowdash questions

Posted: Fri Jul 14, 2017 1:47 pm
by nzgrub
have been working on some dashboards to go onto my nexus 7 android tablet using shadowdash. I have a couple of questions...
1/ first dash is like the green led one that comes as standard with shadowdash, on tunerstudio I set max rpm to 6500, have checked the .dash file once uploaded to tablet and looks set to 6500, when dash loads max rpm is at 100rpm, the needle spins wildly all over the place, I can change it in shadowdash to 6500 and it works fine until I restart shadowdash and it reverts to 100. How do i fix this?
2/ second dash I have designed and uploaded as shadowdash_2_landscape.dash but in shadowdash the old dash still shows. Is there a way in shadowdash to see what file it is actually reading for the dashboard.

Re: shadowdash questions

Posted: Sat Jul 15, 2017 4:58 am
by LT401Vette
What version Shadow Dash?

It sounds like you may be using a TS 3.0 dash with Shadow Dash 1.3x?

Re: shadowdash questions

Posted: Sat Jul 15, 2017 11:36 pm
by nzgrub
version 1.001
there does not seem to be an option to update,
If I uninstall and reinstall will I need to have my registration details again? Was a long time ago will have to see if I can find them.

Re: shadowdash questions

Posted: Sun Jul 16, 2017 1:01 am
by nzgrub
Did the update to the latest version.
The first dash is loading correctly now.
My new dash design still does not show up, I have tried it as /Shadow Dash MS/MS2_Extra/dashboard/dashboard_1_landscape.dash and dashboard_2_landscape.dash but it still makes no difference to what shows in shadowdash.

the .dash file is 1317kb is that a problem, if so how do I make it smaller?
was going to upload it here but is to big for this site so heres a link.
https://drive.google.com/file/d/0B0Y480 ... sp=sharing

Re: shadowdash questions

Posted: Mon Jul 31, 2017 2:07 pm
by Brian H EFI
I just tried loading the dashboard using Shadow Dash version 1.5.02 and I am getting an error in the debug log when Shadow Dash tries to load the file. We will have to look into what is causing the issue however our head developer is currently out of town right now. When he returns I will bring this up to him and see what we can find.