Troubleshooting

Need extra help with RS Dash? You've come to the right page.

Troubleshooting sections
Licensing
  • If you have a question about RS Dash licensing, please read our Licensing FAQ.

 
​​​
Network / Connection Troubleshooting Tips
  • Ensure that you have correctly followed the steps in our setup section for the game(s) you are linking to.

  • Verify that your device is connected to the same network (WiFi or cable) as your PC / XBox / Playstation. 
    IMPORTANT NOTE: The mobile device you run RS Dash on and your gaming device must be connected to the same internal network. You can tell if they are on the same internal network by checking that the first three numbers in the IP address are the same on both devices. For example, both devices have an IP of 192.168.100.xx where the xx is different on each device. Another example might be 10.0.0.xx where the xx is different on each device. If any of those first three numbers are different, then it means that the devices are on different networks and they will not be able to communicate. The most common cause for this is that one device is connected to your internal network and the other is connected to your guest wifi network, instead of your internal wifi network.

  •  Verify that your wireless devices are connected using the same Wifi frequency (2.4Ghz or 5Ghz) as your PC / XBox / Playstation if that is also connected wirelessly.

  • Playstation users should check their NAT configuration on the console. If it is not currently set to use NAT 2, please try changing to use NAT 2 to see if it resolves your issue.​

  • Telemetry lag can be caused by using a transmit rate that is too fast for some routers. If you are experiencing lag, try the following

    • For Project Cars 1/2 try use UDP 4 .

    • For F1 20xx try use 20Hz.

    • For RS Transmitter try a transmit rate of 32.

  • Telemetry lag can be caused by Ethernet over Power line devices. If you have one of these devices, try using a direct cable connection between your gaming device and your wifi router instead of connecting through an ethernet over power device.

​​

  • If you are connected to a network which you do not have control of, such as a university network it may be that you are unable to get the telemetry working due to network restrictions. One way around this if you have a laptop is to create your own hotspot and connect your devices to that instead. Tip from Spanias: I made a hotspot with my laptop and connected it with my ps4 so 100% i would be on the same network and it worked​

  • RS Dash (classic) - Enable the "Legacy NetCode" option in the app settings when linking to AutoMobilista 2 and the Project CARS games with the UDP protocol, and disable it for all other games.

  • Broadcast mode is not always properly supported by routers, so if you are having connectivity or lag issues and have broadcast mode enabled in your game or in RS Transmitter (if applicable), try disabling it and transmit your telemetry to a single device's IP address only to see if it solves your issue.

  • PC users - Do NOT have Jumbo Frames / Jumbo Packets enabled on your PC's network adapter as this may cause a loss of telemetry in Multiplayer sessions or single player sessions with a reasonable number of opponents. The symptoms for this would be that the app works flawlessly when playing single player with no AI, but you lose telemetry when playing single or multiplayer sessions with a reasonable number of opponents. If you are unsure whether or not Jumbo Frames have been enabled, an article such as this explains how to enable it so can therefore also be used as a basis for how to check and disable it if required. The reason why jumbo frames usually does not work is that the hardware between your PC and the tablet/phone device you are using does not support it. For example a number of Wifi routers / access points do not support this feature and will therefore cut off the transmission once Jumbo Frames are sent from the PC (which occurs once you have a certain number of human or AI opponents in game as the amount of telemetry data that needs to be transmitted increases).

  • VPN software may interfere with UDP telemetry.
    Thanks to Steve for this one (UDP telemetry from PC to mobile phone had stopped working for him)

"I’ve managed to get it working.

 I got a friend to help me setup port forwarding on my router settings however, this didn’t appear to have any effect, even after restarting the router. I’m have Nord VPN on my pc but wasn’t connected to it, although I had used it in-between the days of using RS-Rash and for some reason in my networks list NordLynx was listed as connected. I uninstalled NordVPN, restarted the machine and now it works. So I guess the VPN must have had an effect on the network settings somehow?"

  • BT SmartHub / Superhub Troubleshooting

A big thanks to Peter for providing this information for the BT/Virgin Media routers

"I finally managed to get RS Dash working with BT Smarthub 6.  The approach also work with Virgin Media’s Superhub 3.0.  It’s really simple and doesn’t require port forwarding. All you have to do is set the PS4 with a static IP address which requires a manual network setup and then put that IP address as a DMZ on the router. 

So for manual setup on PS4 you select your IP address within your routers IP range:

BT is 192.168.1.nnn

Virgin is 192.168.0.nnn

So select your IP address (making sure it’s not already assigned)

Eg 192.168.1.64

Subnet 255.255.255.0

Gateway and Primary DNS as per previous settings for BT both 192.168.1.254

On the BT router go to advanced settings >> Firewall >> Port Forwarding >> Configuration

Set DMZ to on and select the PS4 by IP address and save setting.

Similar menu options on Virginmedia. 

I’d restart the router and PS4 then you’re good to go.

" -- Peter

RS Transmitter for RS Dash Classic Troubleshooting Tips
  • Ensure that you have correctly followed the steps in our setup section for the game(s) you are linking to.

  • For PC games that require the RS Transmitter app, ensure it is installed on the same PC that the game is running on.

  • Perform the following steps to try and isolate where your issue may be

    • If you start the app on the device without the transmitter running, it should show the message "Waiting for Transmitter Signal"

    • If you then load the RS Transmitter on the PC and click "Start Transmitter", the app should change to say "Waiting for game to start.."

    • If you then start the game, the app should change to the vehicle page by the time you start driving. 

​If it stays at step 1 "Waiting for Transmitter" then it means that your WiFi connection between the PC and device is not working or you have specified the wrong IP Address. You could try tick the "Use broadcast mode" checkbox on the transmitter screen to see if this fixes your problem however a very small percentage of Android devices may have problems with broadcast mode resulting in the telemetry feed stopping between the PC and device.

General Troubleshooting Tips

  • Ensure that you have correctly followed the steps in our setup section for the game(s) you are linking to.

  • Additional game specific troubleshooting tips can be found in our support section under the setup instructions for that particular game.​

  • Power off the device completely (on Apple devices, hold the power button until it comes up with "Slide to Power Off", then use the slider to switch it off). Wait for 10 seconds or so, then power the device back up. Wait for it to completely load and then start the application.​

  • Some Samsung android device users may experience issues with the screen effectively getting blacked out after 3 minutes. This is due to Samsung's "Game Tools" app (thanks for Giovanni for figuring this one out). You can disable this function by doing the following

    • Load RS Dash

    • Drag the android notification panel down from the top of the screen

    • Click on the "Tap to show game tools" option

    • Click the "Advanced Game Features" option

    • Turn OFF the "Auto Screen Lock" option

  • RS Dash (classic) - Android device says "App license could not be verified with Google Play!" when starting the app. Check that your device is connected to the internet. Check that your date/time and time zone settings are accurate. If the time is different to the google play servers by too much then it will cause this error. It is recommended that you let the device synchronise its time from the Internet. If neither of the options above help, you may have an outdated version of Google Play Store and/or Google Play Services. See the troubleshooting tip below with regards to fixing these services.​

  • RS Dash (classic) - java.lang.SecurityException: Neither user <userid> nor current process has com.android.vending.CHECK_LICENSE. This error will occur if your device is stuck with an old version of Google Play Store. You can fix this by completely uninstalling Google Play Store and reinstalling it, alternatively go to Apps -> Play Store -> Clear data and then do the same for Google Play Services. After that launch Google Play Store, set it up and wait for update.

  • RS Dash (classic) for Windows users, if you are experiencing app crashes the likely cause is a bad audio or video driver in windows. A corrupted sound scheme has also been known to cause problems with windows applications (fixed by resetting the sound scheme to windows default in control panel -> sounds). Check your event viewer for hints as to the cause of the problem. The following is the solution to repeated crashing caused by a bad ASUS audio driver application as found by one of our users. "So… I was starting to notice that every crash was somehow connected to this “SS2DevProps.dll” in the Event Viewer. I’ve done some research and this is a library used by Sonic Studio II, an Asus software that is automatically installed when you install the audio drivers. A lot of people on the internet are complaining that this sonic studio 2 cause a lot of Windows app to crash. I don’t even use any of it’s features (it is incompatible with the optical out that i use as audio source) so i uninstalled it completely with all of its plugins. Now RS Dash seems to work properly, not a single crash in a 35 mins gameplay and all features are functioning as they should."​

  • RS Dash (classic) for Windows fails to start with errors like
    RSDash.exe - System Error : The code execution cannot proceed because MSVCP140.dll was not found. Reinstalling the program may fix this problem.
    RSDash.exe - System Error : The code execution cannot proceed because VCRUNTIME140.dll was not found. Reinstalling the program may fix this problem.
    RS Dash for Windows requires a specified version of the Microsoft VC runtimes. To install this, simply goto https://www.microsoft.com/en-us/download/details.aspx?id=53587 and click the [Download] button. Select the vc_redist.x86.exe version and install it.
     

  • Legacy Android devices (eg 4.4.2) are unable to login to the RS Dash.  This issue is caused by those devices having outdated root certificate authority lists which do not include Microsoft's newer certifying authorities. To resolve this issue you need to manually install the root certificates for Microsoft CA's on your device. The certificates can be downloaded from the official Microsoft repository here https://www.microsoft.com/pkiops/docs/repository.htm
    The certificate that needs to be installed is called "Microsoft Azure TLS Issuing CA 01", however it is recommended that all 4 of the "Microsoft Azure TLS Issuing CA" certificates are installed as the others may be used in the future.
    To install the certificates on your Android device, goto Settings -> Security -> Credential Storage section and click on "Install from SD card - Install certificates from an SD card". Navigate to the location of the certificates you downloaded from the link above on your device , select the certificate to install, give it a certificate name (enter the same name as the certificate), set credential use to "VPN and apps" and click OK. 
    You should now be able to login to RS Dash on this device.
    Note: There will likely still be a limit to how long these legacy devices will work for, as new security requirements that emerge for cloud services will eventually result in old legacy devices no longer being able to connect due to outdated/unsupported security protocols.