While in beta, many aspects of Stim are manual and not yet automated. When you see the “Framerate dropped to 0” error, it typically means that the streamer was able to connect but your device was unable to decode the first batch of frames sent to it.
Here are a few steps that you can take to troubleshoot this issue:
- Try refreshing the webpage. Refreshing will cause the stream to try a different port and resend the initial frames which could have been corrupt. It also gives your device a chance to warm up and come out of power save mode.
- If that does not work, the stream may be sending too many frames to your device too quickly and flooding it before it's GPU has a chance to warm up and come out of power save mode.
- Visit https://stim.io/settings/quality and select the lowest quality and FPS (you can increase it later once connected while in-stream).
- Visit https://stim.io/settings/quality and select the lowest quality and FPS (you can increase it later once connected while in-stream).
- Now try connecting to your Cloud PC again by visiting https://stim.io/apps/direct/create
- If you are still unable to connect, try restarting your Cloud PC. Go back to https://stim.io/apps/direct/create and click the red stop icon under your Cloud PC to shut it down. Once stopped you can start it again and try to connect.
- If that does not work, please visit https://stim.io/apps/direct/create and create a new Cloud PC. You may be asked to first stop your old Cloud PC.
- If none of the above work, please try the following tips: https://stimsocial.zendesk.com/hc/en-us/articles/25922870394131--How-To-Improve-the-Experience-if-You-Have-Lag-Latency-and-or-Stuttering
Please contact support@stim.io to let us know if you are still having issues or if any of these troubleshooting steps worked for you so that we can better automate these steps to help others.