Jump to content

Greg Barber

Members
  • Content Count

    141
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Hi, Sorry for the delay in checking back here. An update to XPilot had firstly cleared the Path to CSLs in the options and when I re-set it up there were some changes to how the path was read. I had originally used \'s in the path and never had an issue with a previous version, but the latest update seemed to want /'s. Also the path no longer accepts spaces (if you enter them in they are removed when you load the CSLs. This was never a problem before either and required me to rename the folder I had the CSLs in. I have now rolled back to 1.2.1 beta as I am not using vulkan yet.
  2. Yes. The users would have had time to digest and test both thier systems and the new client. Perhaps a more measured approach would have been to have the pilot client report the problem without the disconnect for a while to make users aware that they cannot continue to operate this way. Sure the message may not have reached everyone as not everyone is involved with the community as much as others. But such time may have given the oppotunity for the news to propogate through the varius supporting communities. As it was, the announcement was made and 24 hours later, users were being disconnected at 40FPS. Again, can you point me to these multiple complaints. The responses within this thread and others on the subject are, while not the first I've heard of the issue, are the first indication that the issue is widespread. The increase in X-Plane usage directly correlates to an increase in overall VATSIM usage which has to be a good thing and somewhat misrepresented in the communications to date. And in the process, many of those users have simply logged off. Well done on the bandaid analogy. For what it's worth, it would seem the initial bugs in the system have now been ironed out and the client(s) are working for the most part as expected. Now is the time to educate the user on how it works and how to live with it.
  3. Hi Norman and all, My "under the carpet" remark was a little tongue in cheek I admit. I want to point out to everyone commenting on the change that was made that I am not against the frame rate limit. I am actually all for it, if it is applied in a measured and considered way. I think that its current implementation (and this has improved greatly over the past few days), gives rise to more problems than it solves with pilots leaving and rejoining the mix very regularly. Personally this change hasn't affected me. I have the means to keep my equipment updated and have been able to conduct online flights on VATSIM in X-Plane without being disconnected. My original post was more about how he change was that upon the community. In any case, this is not my original post and was more about where my original post went than the issue at hand. Norman, feel free to lock this one as it's kind of merging with the other one a bit now.
  4. Yeah I was a little disappointed that the main point of the post was apparently missed. Alas it's been conveniently moved to the hidden, inaccessible forum now (aka swept under the carpet).
  5. Ah right, I did try looking there. I kept getting redirected back to the index whenever I tried to enter that forum. Obviously very broken.
  6. Where did my forum post go? If it was removed can I please have an explanation of why?
  7. Hi Evan, Thanks for sharing your experience. I don't doubt that it causes problems. My beef is not so much with the change but the way it's come about. There has been little to no community involvement until after the fact and the response to the feedback has been somewhat disappointing. One issue that's been raised by a fellow controller is the number of aircraft that are now disappearing and reappearing within the traffic picture because of this change. This isn't always slow traffic but people who are in no way interfering with the sequence at all Suddenly not being there for a few minutes only to reconnect a random number of seconds/minutes later. One such issue occured where an aircraft disconnected and reconnected several times during approach. Each time the tag has to be re-tracked, CFL readjusted and the sequence checked to accommodate. Then with the aircraft on 5mile final he disappears again. With 6 waiting for departure at the holding point, do we take advantage of the new gap in the arrivals sequence and clear a takeoff only to have them reconnect again? Or wait, wait, wait and have the aircraft reconnect at the gate and miss the opportunity? Consider this, "UAL123, give way to the B738 p[Mod - Happy Thoughts]ing right to left, continue..... Oh wait, he disappeared. When will he reconnect I wonder????" Not saying there are not answers to these questions but why were they not asked before? Why wasn't a full risk analysis undertaken to consider exactly how this change may affect ALL users? VATSIM should undo this change until they have a solution to the questions. By fixing one problem, they have created 2 new ones.
  8. OPEN LETTER TO VATSIM Allow me to introduce myself. My name is Greg Barber and I have been a VATSIM user since 2004 having helped administer this network up to Divisional Director level. The statements below are my own feelings about have VATSIM have approached a recent change and in no way reflect the views of any organisational level that I represent. What I write below is not intended to single anyone out, but to hopefully generate a team effort fix the unintended issue that have arisen. If you share or disagree with these views, feel free to join the conversation below. Recently VATSIM mandated a change to the way certain pilot clients maintain their connection to the network. I won't go into the technical nature of this as I believe it has already been well covered. I fear this is a case where VATSIM has shot themselves in the foot (for those unfamiliar with the expressions please exuse it). They made this change to prevent the guy with the slow PC from "ruining everyone elses experience". Honestly I have heard of one instance where the x-plane method of slowing the sim rate has caused a problem for a controller. If you search these forums you'll be lucky to find any either. So they made this decision, so what, that's their choice. Here's why it's been poorly implemented... VATSIM has in recent months seen a vast increase in it's user base due largely to the voice codec but in part due to the improved accessibility of X-Plane to the network. I know of severl long time x-plane users who are just finding themselves joining VATSIM for the first time. With this came very few reported users having issues with sim rate (actually I can't find any evidence of them but I know a few are out there through other channels). So VATSIM implement a function that disconnects users when their AVERAGE frame-rate (or is it sim-rate that it looks at?) drops below a certain level. Unfortunately it appears that function is now disconnecting users who have average frame rates much higher than the published threshold. Unfortunately in true VATSIM fashion, the notice period for this change gave users no chance to investigate whether they'd be affected or make anything more than minor changes to compensate. The update dropped within one day of the changes being posted on social media. Additionally the tech support offered in the pilot client forum below is badly lacking and reduced to a few high up VATSIM representatives telling their users they are wrong and that VATSIM is right. All I can do is to plead with VATSIM to listen to it's users, or risk losing them again. Work WITH this cohort of YOUR users to reach a solution that works for everyone and works as it's intended. As far as I can tell right now, this change is not working as intended and VATSIM's leaders need to show some leadership. I would like to close by saying that I have not yet flown on the network with the new version of the pilot client so I do not post this in response to my own experience but in response to the interactions I have witnessed both here on these forums and in other media. This is an effort to get those people who can sort this problem out, together for the good of this network and it's user base. Thanks
  9. I heard someone say that X-Plane must be the window in focus for the PTT to work which is an undocomeented change I suspect.
  10. Hi, Ok next time I see it, I'll be sure and save the log.txt. It happens in the cruise. I generally get around 80FPS then. I know the other guy who saw it had a beefy PC and gets at least these FPS in cruise.
  11. Hi All, Having just completed almost all of Worldflight using XPilot, the software held up pretty well. One issue I saw a couple of times (and I am not aware of it being reported before) on my system and on another persons system via a stream is the occasionaly freeze of all traffic. This manifest itself during the cruise with all the traffic ahead of you appearing in more or less one place, at their respective levels. You slowly close up on them and then p[Mod - Happy Thoughts] all the traffic at once. Disconnecting from VATSIM and reconnecting seems to fix the problem but it's like something out of the twilight zone or bermuda triangle there for a few minutes until you figure out what's going on. Anyway, just thought I'd post it here in case it's not been reported or shown up at some other time.
  12. The Q2 VATOCE ATO report reported that there was a 91% increase in pilot ratings given compared to Q1. How is this a steady decline?
  13. NOTAM: Worldflight 2018 - Arrival 1 INTRODUCTION Worldflight 2018 will return to VATPAC airspace on the morning of 10th November (local time) and travel through VATPAC airspace via Darwin, Port Moresby, Cairns and Brisbane to arrive back in Sydney that evening. VATPAC will provide ATC services for the arrival legs using controllers from home in conjunction with controllers who have nominated to visit and control from Worldflight Headquarters (WFHQ) in Sydney. This NOTAM contains details of controller positions reserved for use during the event and procedures developed and implemented to manage traffic levels throughout the day. This content is relevant to both ATC and pilots participating in Worldflight legs. 2 NOTAM Download Link https://drive.google.com/file/d/1fb6HMeI8NbSbGNGG0gmFxS9MIhI3vmP_/view?usp=sharing 3 AUTHORITY Director, Operations – [email protected] 4 CANCELLATION This NOTAM self cancels at 1300UTC 10 NOV 18.
×
×
  • Create New...