Jump to content

Peter S - 1249373

ATS Staff
 View Profile  See their activity

  • Posts

    812

  • Joined

  • Last visited

  • Days Won

    61

 Content Type 

Posts posted by Peter S - 1249373

    VATSpy and InfoServ 1903 Updates

    in Pilot Clients and Utilities

    Posted

    14 hours ago, Kirk Christie said:

    Can you upload the changes to here https://github.com/vatsimnetwork/vatspy-data-project?fbclid=IwAR3j2Qee1uSmykorS5s8LyHEUg4yoN3bXD3XsAhiZcXucZCIxILW6VQRx9g

    That way when I update with VATPAC updates, it doesn't wipe all the other updates I have done.

    Thanks for pointing out the new location for the VATSpy Github.

    To put your mind at ease, the recent VATPAC VATSpy update used the old Github VATSpy data as the base. I have downloaded the VATSPy data from the new Github and it is currently the same as the old Github data, so our update uses the latest data. I'll use the new Github site for future updates and have encouraged NZ to do the same for their recent updates (I will incorporate the NZ changes into the VATPAC VATSpy release whilst waiting for the master files to be updated)

    My preference is not to host our own copy of VATSpy data and to just link to the master files. I did find with the old site that my updates did take some time to be processed. If the response improves with the new Github site, I'll be recommending we just reference that.

    YPPH Perth Taxiway Changes

    in Airspace

    Posted · Edited by Peter Story

    9 hours ago, William Teale said:

    Genuinely curious - how do you decide what to model as far as that goes? The key example Im curious about is Brisbane - I understand there is scenery available which has the new runway and associated taxiways already.

    We aim to align the airport layouts in our sector files with what is published in the current AsA DAP. Having said that, the updates to airport layouts are a lower priority than the other information in the sector files (SID's STAR's airways etc). They can be an AIRAC behind. In the case of AIRAC 1911, it was a mid cycle release specifically for Audio For VATSIM. The only updates were the addition of enroute frequencies.

    AIRAC1912 will have the updates for YPPH.

    VATSpy and InfoServ 1903 Updates

    in Pilot Clients and Utilities

    Posted

    I have to say I'm pretty disappointed to see that the original VATSpy Github which I was contributing to was copied across to a new VATSIM Github six months ago and no notification to the contributors even though the same person organised both sites. Oh well I'll get over it and register with the new site for future updates.

    @Harrison Scott I have a specific AIS Github user name registered with the ais vatpac email so it is always available to the ais manager (whoever is in the position) . I'll send another email to Alex to register this with the new Github location.

    NOTAM: VATSPY and ServInfo AIRAC1911

    in News

    Posted · Edited by Peter Story
    Vatspy was also missing the SYD Director positions

    Unfortunately I made an error in both the VATSpy and ServInfo files (CVN was not part of DOS) published in the NOTAM above.

    This has been fixed and the files on the server and in the NOTAM links above have been replaced.

    If you downloaded the files since the publishing of the NOTAM above and before  0725Z 22 Oct 2019, please download them again.

    My apologies for any inconvenience.

    • Like 3

    Request for Beta Testers - Automatic Sector File Updates for VRC and Euroscope

    in Controller Clients

    Posted

    The VATPAC Controller Client Updater has been modified to support VRC clients and those Euroscope users who do not use the VATPAC Euroscope Package.

    Both clients will automatically receive AIRAC sector file updates as they are released. In the case of a standalone Euroscope (not the Euroscope package which is already supported), updated Voice file and Login profiles containing the latest controller positions and frequencies will be available if you wish to use them. The readme file explains how to do this.

    If you wish to help test this new version of the Controller Client Updater, please PM me and I will provide a link for the installer.

    What do I have to do as a beta tester?
    The testing is very straight forward

    • Run the installer, select the location where you have your sector files and for VRC the location and name of the .pof file you use
    • When prompted, accept the download of the 1911 sector files. This will happen the first time irrespective of what version of the sector files you have.
    • Leave the Controller Client installed - you will automatically receive the 1912 AIRAC when it is released.
    • Review the readme file (desktop shortcut and in Windows Start menu under VATPAC) and provide feedback on its effectiveness
    • Report any issues and provide feedback.

    Existing beta testers will automatically receive the new version of the Controller Client Updater with the readme file explaining the new features.

    The VATPAC Controller Client Updater runs once a day for about a second to check for updates. If there aren't any you will not be aware of the program.

    • Like 1

    One Controller, Multiple Frequencies - Explained

    in Audio For VATSIM

    Posted

    One way to see if a controller has extended to another sector (provided they remembered to cross couple the frequencies)  is to look at the VATSIM Viewer.

    The cross coupled frequencies will appear against the controller login in the left panel. You will also see the transceiver sites active on the map in the extended sectors.

    Of course you still need to know the frequency for the extended sector to call on as the controller icon on the map and the pilot client only shows the primary frequency. There is an update to VATSpy and ServInfo coming that helps to find the frequency to use in an extended sector.

    Jandakot YPJT RWY 12/30 Extension

    in Airspace

    Posted · Edited by Peter Story

    For those that have seen the media releases today advising of the runway 12/30 extension at YPJT, the new layout will be included in the 1912 AIRAC sector files.

    After the 7 Nov 2019 release of AIRAC 1912, controllers need to be aware that it may take some time for pilots to upgrade their airport scenery, assuming an updated version is available.

    The new runway layout is not in the 7Nov19 AsA documentation, but is covered in AIP SUP 129/19

     

    Screenshot 2019-10-08 17.21.57.png

    • Like 4

    Audio For VATSIM - Coming 14th October 2019

    in Audio For VATSIM

    Posted

    12 hours ago, Kirk Christie said:

    Much like they do on the ERC charts, we could write the freqnecys into the sector files for each area? 

    11 hours ago, Callum Strawbridge said:

    Definitely a good option David and Kirk. I think this is something we could look at for our next AIRAC Sector File update. :)

    Have added it to the list of sector file update tasks. Depending on workload, It may be possible to release an update for the 14 Oct AFV launch.

    This is also possible in VATSpy. Only TRT has been updated as a test. I've only shown the standard sector frequency so as not to create any confusion. I need to do some more testing to understand the impacts on VATSpy reporting and handling of upper sectors and discuss within Ops on the best way to implement.

     

    Screenshot 2019-10-03 11.06.15.png

    • Like 1

    Audio For VATSIM - Coming 14th October 2019

    in Audio For VATSIM

    Posted

    6 hours ago, Russell Diehl said:

    Does anyone know whether developer's of pilot clients intend to support transmissions on multiple frequencies? That is, allow pilots to transmit to CTAF and a monitoring CTR controller for IFR departure calls to receive a code and IFR traffic info.

    Hey Rusty, I don't know what the developers have planned, but in the real world, you can only transmit on one frequency at a time and I remember making a CTAF call, followed by a CTR call when departing IFR from a non-controlled airport. There is the ability to receive on two frequencies and it's just a matter of switching the TX from com1 to com2 to make the CTAF broadcast followed by contacting CTR for a code and to start the SARwatch.

    Provided the aircraft simulation supports two comm radios and the ability to switch the TX function between them I believe AFV will support it as well.

    My 2 cents worth :)

    • Like 2

    Euroscope Airways Routes

    in Website & IT

    Posted · Edited by Peter Story

    G'day Tyler, I think you will find the problem is you are using an old version of the Euroscope file AIRWAY.TXT where MUDGI is shown as MDG for H202. If you have a Navigraph subscription you can get the latest airway.txt by downloading the FS-Navigator FMS data.

    If you use the VATPAC Euroscope Package, the instructions for doing this are in MyDocuments\Euroscope\VATPAC\Readme.pdf file

    Extension to ASP

    in Airspace

    Posted · Edited by Peter Story

    On 9/22/2019 at 5:33 PM, Kirk Christie said:

    Noticed that when I set sector ownership to EXTENDED-ASP, the following sectors are light up.
    YWAR
    YASP
    YFOR
    YAUG
    YTBD

    Kirk, now I'm back from holidays, I had a look at the .ese sector definitions for EXTEND_ASP and they are correct. I can't explain why you had AUG and TBD light up as I couldn't reproduce it when I tried

     

    Screenshot 2019-09-28 16.54.36.png

    • Like 1

    Sydney Director

    in Airspace

    Posted · Edited by Peter Story

    14 hours ago, Tristan Garratt said:

    So on MRM, When Director logged in, with runway 25 selected. The runway 16 airspace was cut out rather than the 25 airspace.

    The Euroscope TMA rules for YSSY airspace are quite complex. For me to try and reproduce the problem I'll need to know the following

    • The callsign you were logged in as (eg was it SY_DEP or SY-S_DEP
    • The active runway you have selected (I assume rwy 25)
    • What other App/Dep controllers were present eg SY_APP before SY-D_APP (Director) logged in.

    What you see as highlighted airspace is only dependent on the position you  are logged in as, the active runway you have selected and what other TMA positions are active. It doesn't matter what the other controllers have selected as the active runway as your Euroscope can't see this.

    If you can provide this information I can reproduce the scenario using the builtin Euroscope simulator which allows me to simulate other positions being active whilst I'm logged into a position.

    • Like 2

    Sydney Director

    in Airspace

    Posted

    Thanks for the advice Tristan. I just tested it and it highlights for me for Rwy 25. 

    What I did notice when testing was that Euroscope sometimes takes a little longer before the active airports for the position you are logged in as are set in the runway selection. You can tell when the active airports have been set by euroscope by looking for the METAR summary which appears in the menu bar or by opening the active airport/runaway runway selector dialog.

    Without YSSY being set as an active airport and runway 25 selected as the active runway the airspace owned by the position for that runway won't be highlighted

    Request for Beta Testers - Automatic Update of Euroscope Package

    in Controller Clients

    Posted

    1 hour ago, Matt Kelly said:

    I've found the biggest hassle of updating AIRACs is having to set up all of my F1+# shortcuts again afterwards.

    Thanks for the feedback Matt and a great question. I assume you are creating short cuts in addition to those provided in the package. The current version of the ES Package Installer was designed as an installer and it overwrites all existing files, so yes if you add extra shortcuts you will loose them next time you run the installer. Whilst it could be redesigned to do updates only, the work has been put into the Controller Client Updater instead. The aim is for a new user to run the ES Package installer once and then use the Controller Client Updater for updates.

     The Controller Client Updater has been designed as an updater rather than an initial installer and preserves any changes you make to the profiles and TAAATS.txt. There are some settings that are "controlled" and will be updated if they have changed. At present these are  limited to the LastSession ATIS and airway lines in the .prf and the VoiceAtisBuilderUrl and SModeTransponders lines in the TAAATS.txt file. In addition to preserving user changes, files are only updated if they have changed since the last update.

    A potential future enhancement being considered is the ability to configure the voice hardware settings for one profile and then have them copied to all profiles. Whilst these are not updated by the Client Updater, they are required in each profile, so are tedious to set up at present.

    • Like 2
×
×
  • Create New...