Johan Grauers Posted September 5, 2015 at 06:36 PM Posted September 5, 2015 at 06:36 PM I have just had a conversation with another mentor, we were both signed on to sweatbox running two different files at two different airports. When I paused my session, it would also pause his, and the other way around. Feature or bug? If this is the intention can it be changed somehow? It makes running sweatbox a bit difficult as one would be explaining something to a student when the other person tried to run their session as they were mid session, and all pausing needs you to check with the other mentor first which isn't always what you need when a session is going in the wrong way. Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Matthew Moy 1288933 Posted September 5, 2015 at 09:02 PM Posted September 5, 2015 at 09:02 PM I think it is to do with the range the mentor have in Sweatbox. You can control all the aircrafts you have in your range if I'm correct. Link to comment Share on other sites More sharing options...
Johan Grauers Posted September 5, 2015 at 10:02 PM Author Posted September 5, 2015 at 10:02 PM I think it is to do with the range the mentor have in Sweatbox. You can control all the aircrafts you have in your range if I'm correct. But in the past (3.1d) if I paused only "my" aircfraft paused. Now we were pausing not only our own but also the other mentors aircraft, despite us running two different files in two different places. This has not been how it used to work in the past. Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Sam White 1214219 Posted September 5, 2015 at 10:54 PM Posted September 5, 2015 at 10:54 PM This is a known bug - I think it may have been corrected in the latest public beta? EDIT: Yep - bug fix 538: http://www.euroscope.hu/mantis/view.php?id=538 The beta is available here: http://euroscope.hu/installbeta/changes.html VATSIM UK S2 Rated (Essex RTS) Link to comment Share on other sites More sharing options...
Michael Pike Posted October 3, 2015 at 06:44 PM Posted October 3, 2015 at 06:44 PM I'm still seeing this happen. And it doesn't depend on range - I think it will affect everyone on the server at the time! Can we somehow spread the message that everyone using 3.2 on sweatbox needs to patch their ES to 3.2a. Mike Pike VATSIM-UK Link to comment Share on other sites More sharing options...
Recommended Posts