When I change the test mode to “Run” then press F5, it instead launches a play solo test in a broken state where the stop and pause buttons are greyed out and clicking the still-enabled play button does nothing. Switching from the client view to the server view re-enables the stop button.
Expected behavior
Pressing F5 should start a test according to the selected testing mode, and the stop button should always be available during a test regardless of context.
same thing happens to me, its so annoying. i tried reinstalling and same thing still happens
Hello! F5 starts a Test session (Play Solo). If you want to start any other testing session with F5, you’ll need to remove the shortcut from Test and add the F5 shortcut to the Play button instead. This will allow you to start any playtesting session based on what’s represented in your dropdown (ex: Run).
As for the greyed out buttons, feel free to send over some logs and images/videos to help us debug further as this is something we were unable to reproduce on our end. Thanks!
its been a month, when is this getting fixed?
Hi! for the greyed out buttons, feel free to send over some logs and images/videos to help us debug further as this is something we were unable to reproduce on our end, so it’s difficult to figure out a fix and what the issue is. Also please note, F5 starts a Test session (Play Solo). If you want to start any other testing session with F5, you’ll need to remove the shortcut from Test and add the F5 shortcut to the Play button instead. This will allow you to start any playtesting session based on what’s represented in your dropdown (ex: Run).
hello! a fix has been pushed and it should be out within the next 2 releases 
thanks for the report!