Jump to content

Search the Community

Showing results for tags 'vatsys'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • VATSIM Information
    • Announcements & Important Notices
  • Discussion
    • General Discussion
    • Pilot Talk
    • Controller Talk
    • Charts, Navigation and Flightplanning Help
  • Community
    • Virtual Airlines
    • Special Operations Administration
    • Groups
    • Events
    • Come fly with me...
  • Support
    • General
    • Pilot Software
    • ATC Software
    • Other Software
    • Audio for VATSIM Support
  • Regions & Divisions
    • Americas Region
    • Asia Pacific Region
    • Europe, Middle East, and Africa Region
    • Partnerships
  • VATSIM Services
    • General
    • Audio for VATSIM
    • VATSIM Webmasters
    • VATSIM Vacancies

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 3 results

  1. Hi, When I log on to VatSys and listen in on ATC (just observing for now), I notice that the transmitting (when pilots and controllers talk) is very choppy. I have tried to see which server has the best ping, I tried downloading the standalone AFV, but that just seemed to worsen things. Does anybody have any suggestions on what I should do? Or does anybody know what the issue is? Thanks, Pepijn Colenbrander
  2. G'day, I have been wondering if there is a way to get vStrips working for VATSYS other than having Euroscope Open and running VATSYS in Local Host Mode. Any replies would be appreciated! Thanks, Flynn Wright (1502406) 🙂
  3. Myself and other members are reporting on both the VATPAC and VATNZ Discord that vatSys would crash to desktop (CTD) when attempting to connect to the VATSIM network regardless of what vatSys profile is used on version 0.1.7719.33834. Here is the crash report from Event Viewer on Windows: Faulting application name: vatSys.exe, version: 0.1.7719.33834, time stamp: 0x602e1ba7 Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e61bb Exception code: 0xc00000fd Fault offset: 0x00017e33 Faulting process ID: 0xdc8 Faulting application start time: 0x01d705d17741f582 Faulting application path: D:\vatSys\bin\vatSys.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report ID: 8d721745-aa62-4730-8f91-7e7e5fc88429 Faulting package full name: Faulting package-relative application ID: By the looks of it this could be something to do with vatSys and the .NET Framework. Any possible fixes or ideas to come soon? Thanks.
  • Create New...