Michael Kuhne Posted October 20, 2018 at 06:30 PM Posted October 20, 2018 at 06:30 PM Using the latest beta (2018-10-14 build version 3.2.1.18 (3.2a(r18))), I am experiencing from time to time an "Unspecified error" message, after some second a second one pops up. No impact as far as I can see, I can just click them away and everything continues to work fine. Link to comment Share on other sites More sharing options...
Jonas Kuster Posted October 20, 2018 at 06:42 PM Posted October 20, 2018 at 06:42 PM Observed the same. Including a short freeze while the message is displayed. Jonas Kuster Network Supervisor Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland GNG Support Team | gng.aero-nav.com ES Plugin Developer | CCAMS Link to comment Share on other sites More sharing options...
Jonas Kuster Posted October 20, 2018 at 07:08 PM Posted October 20, 2018 at 07:08 PM Actually found out during a session with another member using r18 as well that we get those errors exactly at the same time. We were also both observing the same area. Thus, it's very likely this issue is connected to some messages from the network which ES r18 cannot properly read. Jonas Kuster Network Supervisor Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland GNG Support Team | gng.aero-nav.com ES Plugin Developer | CCAMS Link to comment Share on other sites More sharing options...
Oliver Gruetzmann Posted November 21, 2018 at 05:48 PM Posted November 21, 2018 at 05:48 PM Might be related to METAR updates (have those as well). Link to comment Share on other sites More sharing options...
Nestor Perez Posted November 22, 2018 at 11:48 AM Posted November 22, 2018 at 11:48 AM Oh, so it's not only me! Thank God. I had no clue of what I could've broken this time in my setup Me. Link to comment Share on other sites More sharing options...
Claus Hemberg Joergensen Posted January 8, 2019 at 09:14 PM Posted January 8, 2019 at 09:14 PM Any updates on this? Is experiencing it too with 3.2a(r18) Claus Hemberg Joergensen Vatsim Membership Manager - Americas Link to comment Share on other sites More sharing options...
Oliver Gruetzmann Posted January 8, 2019 at 11:02 PM Posted January 8, 2019 at 11:02 PM Think I found something about it: Today, I had the error again on some occasions, later during my shift I experienced something I've seen recently several times as well: A flight without a flight plan, where others had one. I was trying to get the plan via .getfp -> Unspecified Error I asked fellow controllers to change something in the fp -> Unspecified error each time someone closed the flight plan with OK. I'll post my logs tomorrow, maybe someone can find out what happened, I didn't see anything wrong. Seems to be something in some flight plans. Link to comment Share on other sites More sharing options...
Oliver Gruetzmann Posted January 8, 2019 at 11:14 PM Posted January 8, 2019 at 11:14 PM This is the flight: https://stats.vatsim.net/callsign_details.php?id=1425126&callsign=SAS1678 It had a wrong departure airport at first, which was amended by some controller (need to check which version this guy uses), maybe this is something to look after. Can't see anything strange in the plan so far. Link to comment Share on other sites More sharing options...
Oliver Gruetzmann Posted January 9, 2019 at 05:50 PM Posted January 9, 2019 at 05:50 PM Found the error: [20:04:21 >>>> EDWW_B_CTR] $FPSAS1678:*A:I:MD88:430:EKDB:2090:2090:FL280:EKCH:0:51:2:11:EKOD:+VFPS+/V/ /XSQUACKBOX /NEWBIE:GERGA T239 PEROM T298 MONAK Look at the :2090:2090: part, which is Estimated Time of Departure and Actual Time of Departure. Changing this to 2030:2030 gets rid of the error. Not sure how this is possible. Check the Log: https://1drv.ms/t/s!AjT-PvbG_V3g1TfGJrQi0nGZmJHY You'll get 2 errors popping up right at the start, if you change the two lines, the error is gone. Link to comment Share on other sites More sharing options...
Oliver Gruetzmann Posted January 9, 2019 at 06:42 PM Posted January 9, 2019 at 06:42 PM And just had another pilot with this kind of typo, same error popping up, flightplan not visible to me: Link to comment Share on other sites More sharing options...
Joel Lagarrigue Posted January 11, 2019 at 10:33 PM Posted January 11, 2019 at 10:33 PM Hello, Oliver, you are absolutely right, same issue for me with 8000 as departure time. Changed it to 0800, no error popped. Link to comment Share on other sites More sharing options...
Harry Sugden Posted March 31, 2019 at 09:14 AM Posted March 31, 2019 at 09:14 AM This bug was rather excruciating when trying to control a busy CTP sector... kept popping up every 30 seconds at some points! ATC Examiner, VATSIM UK No nonsense controlling Twitch - HazControl ✈️ @HVatsim Link to comment Share on other sites More sharing options...
Andrew Gransden Posted May 6, 2019 at 12:20 PM Posted May 6, 2019 at 12:20 PM I have been experiencing this fault for sometime. Today it occurred to several UK controllers at the same time. After a period of multiple error messages it stopped and then restarted about 30 mins later for a short period. I am using v3.2 r19. Can we ask when it will be fixed? Link to comment Share on other sites More sharing options...
Alex Amorianos Posted May 6, 2019 at 02:57 PM Posted May 6, 2019 at 02:57 PM Same here. I was on LGAV_APP and had that error several times. Alex Link to comment Share on other sites More sharing options...
Magnus Meese Posted May 7, 2019 at 12:53 AM Posted May 7, 2019 at 12:53 AM Chiming in, a fix would be great. Link to comment Share on other sites More sharing options...
Nestor Perez Posted May 8, 2019 at 10:43 AM Posted May 8, 2019 at 10:43 AM Issue has now been found and fixed. A new version will hopefully be coming out soon. Regards, Me. Link to comment Share on other sites More sharing options...
Michael Kuhne Posted May 9, 2019 at 12:00 PM Author Posted May 9, 2019 at 12:00 PM Great, thanks! Link to comment Share on other sites More sharing options...
Nestor Perez Posted May 16, 2019 at 10:12 AM Posted May 16, 2019 at 10:12 AM Hi all! Find the link to the new beta here: viewtopic.php?f=71&t=78724#p532997 Regards, Me. Link to comment Share on other sites More sharing options...
Recommended Posts