Skin Freeze Issue (Solved)

**ldl72** · 07-05-2012, 05:41 PM

Hi All,

Hope someone can help. When my screen switches to the backup camera and return to RR the current skin freezes and the labels seem to stack on top of each other. RR continues to play music and accept commands. I have to reload the skin or RR to correct this problem. This happens with any skin that I try.

Does anyone else have this problem or know how to fix? Is there a way to reload the skin on this type of screen change and stay on the current skin.

Any help would be appreciated.

Edit... For any newbie that comes along. The solution for me was to use the PC (VGA) connection for the lilliput screen instead of the HDMI. I Did not try the DVI cable so I do not know if that would have worked also. Finally glad to have gotten past this hurdle.

**ldl72** · 07-11-2012, 05:44 AM

Is there anyone using a backup camera with RideRunner as the frontend and a lilliput 669 monitor that have this problem? All I am looking for is to get my rig running as seemlessly as possible.
If anyone would like to simulate this problem, Just start RR then minimize, Go to the graphics properties of your display and change resolutions, do not hit okay to accept the resolution change, go back to RR and switch to any screen, wait for the resolution to change back to what it was before and the try to adjust volume or any other control. You will notice that the new volume number changes on top of the previous.
Also, how do I get DashCommand to start or running in the background when RideRunner starts. I currently have to swith to the DashCommand skin each time I start my car. Thanks.

**sargeants** · 07-25-2012, 11:25 AM

Originally Posted by ldl72

Also, how do I get DashCommand to start or running in the background when RideRunner starts. I currently have to swith to the DashCommand skin each time I start my car. Thanks.

I get a similar thing with the freezing, but not really... can't do any input after going from audio/rrmedia back to gps - sometimes... so no help for you there.

As for the DashCommand, have you tried putting a shortcut to it in the StartUp folder in the Start Menu? Or possibly use the ONSKINSTART command in the ExecTBL.ini?

**ldl72** · 07-27-2012, 07:01 PM

Thanks for your response. I am really suprised that no one else has had this problem or maybe I am asking the wrong question. I did do some more reading and was able to get dashcommand to startup with RR. Wish I could get the other issue solved. It just makes RR feel incomplete. Thanks again.

**drewbp** · 07-28-2012, 12:40 AM

Originally Posted by ldl72

Thanks for your response. I am really suprised that no one else has had this problem or maybe I am asking the wrong question. I did do some more reading and was able to get dashcommand to startup with RR. Wish I could get the other issue solved. It just makes RR feel incomplete. Thanks again.

What did you do to start dashcommand with RR? Please explain.

**ldl72** · 07-28-2012, 10:42 AM

I initially read the thread below.

The embbed program cannot start

I am currently using UConnect but I adopted the concept from Elite2/DFX5 which I use also.

In UConnect ExecTBL I use - "DASHCOMMAND","LOAD;DashCommand.skin"

In UConnect SKIN I use - dashcommandpath=C:\Program Files\DashCommand\dashcommand.exe|-nosplash -nosplashvideo -startindashboards -title:"DashCommand™";DashCommand™

In RR Config Page2 I use - LOAD;DASHCOMMAND.SKIN||RUNQ;$DASHCOMMANDPATH$||CANCEL

Hope this help. With the above configuration DashCommand closes properly with RR and does not freeze up when changing between skins. I am now in the process of trying to get IGO8 to load at startup also.