Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Kyle Sanders

Pages: [1] 2 3
1
General Discussion / Is Frequency Spacing limitations still a thing?
« on: January 22, 2022, 04:46:51 PM »
I was told a while back that if the RW frequency we (ATC) are using has a .xx5 at the end, just make it .xx0. So we did.

Our normal CTR combine frequency is 120.275 but we prime as 120.270.
I get a good amount of pilots responding via PM from the ContactMe that they can't tune to that but when they tune to the RW 120.275, it is fine.

I know that AFV handles this "forwarding" but I am curious if we can just start priming as the RW frequencies now or not?

2
The Control Room Floor / Pilot Expectations, cont...
« on: July 06, 2021, 11:17:11 AM »
I am creating this thread because as Mani (USA1) stated in another topic thread, he does not wish to shut down this discussion, but it was a bit outside the scope of the topic it was posted under.
Reference: https://forums.vatusa.net/index.php?topic=10178.msg45876#msg45876




The following is the partial post from Dylan Lundberg on 05JUL2021 that triggered a following of those that agree that VATUSA Management should be advocating to VATSIM HQ for more accountability and reasonable knowledge checks for pilots prior to pilots being allowed to connect and fly.

Quote
2) What is the UNDERLYING cause of controllers not wanting to control? P I L O T S. I'll be damned if I'm going to staff more than I'm required, when us controllers are held to a crazy high standard, yet the 13 year old that gets MFSF2020 can connect without actually being checked for competency to comply with basic ATC instructions. Obviously this issue goes higher than VATUSA, but VATUSA isn't doing anyone any favors by telling facilities towards the bottom of the list "You should be online more." What VATUSA COULD be doing to help improve and motivate controllers to do more than what it required, is to be up at the front door of the BOG, knocking until they actually start taking pilot competency seriously. IT IS NOT FUN when we get online, and have to hand hold 50% of the pilots on our frequency. That alone is a big reason why most facilities don't have an higher uptime. Then you need to account for environmental factors like, I don't know, actually having a life outside the hobby, LOAs, etc. Controllers are BURNTOUT from dealing with the pilots that do not know what they're doing. We can preach to them that they should read the Pilot Learning documents, but currently that is merely a recommendation.

3) Last year (IIRC), VATUSA was more worried about having exit interviews with S1s (who cares?) when we should have been focusing on our C1+'s that got fully certified, worked some hours, and went away. Who cares why the S1 who did minimal training to work a DEL/GND position left? You'd have much more meaningful feedback if we focused on the fully certified C1+s that left after certification. If we did that, I'm willing to bet that you'd be hearing the same thing about pilots over, and over, and over again...if you had that feedback last year, maybe we could have made meaningful impact network wide regarding pilot competency, and eliminating that as a factor for Burnout.

4) You don't motivate leaders/members of a volunteer organization by comparing them to the guy next door. You're treating this as a company-type measurable metric, as if the pilots are our customers. No. Don't. PLEASE DON'T. By reaching out to some ARTCC leaders and telling them "We think your facility should be on more" again, is ignoring the underlying issues at hand. We need to first address the WHY, fix those issues, THEN we can begin to make headway in uptime.

My personal note:

I am a huge advocate for constructive feedback for management. Compared to years past, this particular group of individuals at the VATUSA HQ seem to be much more concerned with getting things done that have needed to be done for years and for the most part, approach these projects and tasks with a sense of logic and reason.

I would very much like this discussion to not be so much of a pilot and management-bashing thread but rather a constructive means to relay to our HQ department the reasons we are tired of controlling on the network with pilots that directly kill the “Realism” and therefore, “fun” of the simulation for us.

Yes, pilots have choices for the networks they can join (if any) to fly their sims and an argument could be made that ATC need Pilots, but not the other way around... sure, but if your activity hours for ATC start to dwindle, along with the quality in which we provide services, then that is an issue too. We might have found another hobby that doesn't annoy us so much. I am in favor of making this network just as attractive for ATC as it is for pilots.

For every pilot that is “one of those”, it seems that there is another pilot that takes the constructive criticism and resources we send via PM very well and appreciates the time we took to give them this information.

Why isn't this information provided to them in a more constructive way from the beginning? Even though I like the pilots that take the information well, it still takes away from me separating traffic and doing my job, and ultimately takes away from the simulation.

The Pilot Learning Center is fairly well done, but it does not seem to filter out “THOSE” pilots that have no intentions on making this a fun and educational environment, and it seems that the pilots that would benefit from that information and appreciate it still don't know it's there until we take the time to PM them.

Can we start the discussion on what can be done at the VATSIM level to correct this and hopefully propose it to the higher-ups?

3
The Control Room Floor / ORD 6 Departure CVS vs MAINTAIN
« on: December 24, 2020, 02:04:31 PM »
The following discussion was inspired by an incident on the network that I was not part of and I am not here to speak about that incident but rather the specifics for interpreting the .65 in a very specific situation.

I would like to know why KORD (even real world) issues Climb Via SID for the O'Hare 6 departure and hopefully learn something.

https://aeronav.faa.gov/d-tpp/2013/00166OHARE.PDF

https://aeronav.faa.gov/d-tpp/2013/00166OHARE_C.PDF.


7110.65 4-3-2.e.4:

Use one of the following when the SID contains published crossing restrictions:
A) Instruct aircraft to “Climb via SID.”"
B) Instruct the aircraft to “Climb via SID except maintain (altitude)” when a top altitude is not published or when it is necessary to issue an interim altitude.


The ORD 6 does have published crossing restrictions, so “Climb Via SID” is used at this moment.
However, if we go down to 7110.65 4-3-2.e.5 right after it:


“When a SID does not contain published crossing restrictions and/or is a SID with a Radar Vector segment or a Radar Vector SID; or a SID is constructed with a Radar Vector segment and contains published crossing restrictions after the vector segment, instruct aircraft to “MAINTAIN (altitude).”

Or simply put:
If "Y' to any of the following, issue: "MAINTAIN"
1) When a SID does not contain published crossing restrictions
2) SID with a Radar Vector segment
3) Radar Vector SID
4) SID is constructed with a Radar Vector segment and contains published crossing restrictions after the vector segment
      

Considering the answer is yes to #'s 2 and 3, I would now think that “Maintain” is now required.

So the way I see it is:

1) Since we came to an answer before getting to paragraph 5, we stop there an use that... so “Climb Via SID”, or...
2) KORD has special authorization to use Climb Via SID, or...
3) I am misunderstanding something.




I am pretty sure that scenario #1 isn't right because that would make the KSLC ARCHZ departure a “Climb VIA SID” yet it is “Maintain” in real world along with the fact that it perfectly fits into the last condition of paragraph 5.

Scenario 2 would be understandable.

Scenario 3 would be likely.

4
The Control Room Floor / All DPs and STARs Facility Files
« on: December 19, 2020, 03:50:52 PM »
https://www.dropbox.com/sh/8yganz4g9q5lipb/AACOps2znlLWWr9hpf41mSSza?dl=0

This includes SCT2 and GEOMAP diagrams for all STARS and DPs (including graphical ODPs) that aren't considered "RADAR VECTORED".

There may be a few errors here and there but this will get everyone a base map if you aren't already up to date.

5
The Control Room Floor / NASR FIX SCT Generator
« on: October 27, 2020, 09:33:19 PM »
This Batch File will create a FIX list in Sector File Format (.SCT2) for the user to easily copy/paste into their own custom Sector File.

Feedback welcome.

https://github.com/KSanders7070/NASR_FIX_SCT_Generator

6
The Control Room Floor / NASR APT ISR Generator
« on: October 27, 2020, 05:17:51 AM »
Feedback Welcome

THIS BATCH FILE WILL CREATE AN IN-SCOPE REFERENCE (ISR) for all Airports from the FAA NASR 28 DAY SUBSCRIPTION DATA for any Virtual Radar Software that utilizes this format of alias commands. (i.e. VRC by METACRAFT)

It will also create an Airport list in Sector File Format (.SCT2) for the user to easily copy/paste into their own custom Sector File.

SCT2: If the airport has an ICAO ID, the ICAO will be used for the airport ID.

ALIAS: If the airport has an ICAO ID, the ICAO will be used for the alias syntax.

https://github.com/KSanders7070/NASR_APT_ISR_Generator

7
The Control Room Floor / NASR NAVAID ISR Generator
« on: October 25, 2020, 11:53:55 PM »
Feedback Welcome

THIS BATCH FILE WILL CREATE AN IN-SCOPE REFERENCE (ISR) for all NAVAIDs from the FAA NASR 28 DAY SUBSCRIPTION DATA for any Virtual Radar Software that ustilizes this format of alias commands. (i.e. VRC by METACRAFT)

https://github.com/KSanders7070/NAVAID_ISR_Generator

8
The Flight Deck / KSLC SKEES Arrival Shortcuts
« on: August 13, 2020, 09:36:58 AM »
Pilots: We (at KSLC) have had a significant amount of aircraft this year cut HINKY out of their routing and go straight to IRRON after BOOOT. (image attached)

We use to think that pilots just willingly being negligent but given the amount of times this has happened, I wonder if it is problem with NAVDATA in some sims.

Could I get some pilots here to test FSX, P3D, X-plane 11, and then NAVIGRAPH to make sure HINKY is programmed into the route and then furthermore, could you fly the SKEES arrival and see if the FMS decides to treat HINKY as a Fly-By waypoint?

A normal clearance from ATC would happen when you are around BEARR and it would be “Descend via the SKEES5 arrival. At IRRON, cleared ILS RWY 16L Approach”.

Please send an email to [email protected] with your results.


If this ends up not being a sim issue or NAVDATA issue, this this a big problem in this area that I would hope that VAs that fly in/out of KSLC would bring light to this situation... we NEED you to fly to HINKY unless we give you a shortcut for many reason and one of them being separation... so like... the one thing we are responsible for haha!

9
News / ZLC Hired New EC!
« on: May 30, 2020, 10:29:13 AM »
I am very happy to announce Joshua Rogers as our new Events Coordinator!

Josh has been with ZLC since June of 2018 and has dedicated himself to pushing his training forward but not at the expense of thoroughly understanding the fundamental topics and this shows in his skills as a controller.

When reviewing our need and options for the EC position, the ATM and I could not think of anyone more suited for the task.

Everyone please congratulate him on this new accomplishment.

Josh- I can't wait to see what you do with this department. Good luck and have fun!

10
News / ZLC Hired a New FE!
« on: May 20, 2020, 10:53:44 PM »
I am very pleased to announce Nikolas Boling as our new Facility Engineer!

Nik has displayed a great deal of dedication, motivation and initiative in his training here at ZLC along with his passion to help in every department he can.

Initially due to his coding skills, he helped out mostly with the Webmaster side of things and then found a passion for the Facility Files. He has already written a great deal of programs for ARTCC FE's to use in order to make their jobs be a lot easier and is continuing to work on more advanced programs.

Nik and I have already discussed a general 2 year plan to completely revamp the Facilities Department of ZLC and bring more advanced resources to our members.

It is surprising to see a member with no prior experience in any aviation field come into this organization and learn as much as he has already. Thank you Nik and I am very excited to be working with you.

11
News / ZLC Seeks Events Coordinator
« on: May 05, 2020, 09:48:57 AM »
ZLC ARTCC wishes to thank Michael Romashov for his dedicated service to the Events Coordinator position. Michael has chosen to dedicate his time now the ZHU Webmaster position. We wish him well and good luck!

With that said, ZLC ARTCC is looking to hire a new Events Coordinator (EC).


EC DUTIES:
  • Report to the Deputy Air Traffic Manager
  • Plan, schedule, and coordinate all events involving the ZLC ARTCC controllers.
  • Maintain the ARTCC’s social media outlets
  • Acts as liaison for pilots and pilot organization to ZLC ARTCC

CANDIDATE REQUIREMENTS:
  • Active member of the network, in good standing.
  • VATSIM S2 rating.
  • Demonstrates knowledge or willingness to learn all available ZLC ARTCC resources such as Directives, CBT content, pilot resources, and facility file setups.
  • Demonstrates appropriate knowledge of all levels of ATC positions, responsibilities, limitations, and human factors.
  • Ability to work in a team environment.
  • Excellent time and project management skills
  • File and information management skills
  • Ability to examine and predict facility staffing levels needed to handle expected traffic levels.
  • Possesses the ability to present themselves with common professional etiquette (written and spoken correspondence)li]
  • Ability to dedicate a minimum of 15min a day checking/responding to emails and VATUSA staff forum posts.
  • Proficient basic user skills with the following programs/software or is willing to learn quickly: Photoshop (or like-program), Google services such as Docs, Slides, Sheets, and Forms.
  • Possess a high degree of energy and commit appropriate to the requirements of the position.
  • Familiar with managing common social media page platforms such as Facebook, Twitter, Instagram, Twitch, etc… (or willing to learn)
  • Demonstrate qualities of understanding, patience, and maturity.
  • Willing to first work as an assistant EC to demostrate abilities prior to being awarded the Department-Head position.


TO APPLY:
Send email to [email protected]:
  • SUBJECT LINE: EC App (your CID)
  • ATTACH: A single paged, professionally formatted resume in PDF format.
  • BODY: Your current ARTCC assignment and any additional info you wish to share.

NOTES:
  • Failure to send a satisfactory resume, may disqualify the applicant.
  • After submitting the resume, pay special attention for a response with a proposed interview time.
  • Interviews will take place in the ZLC ARTCC Discord. Instructions for connecting will be sent to the candidate at a later time.
  • In the event a candidate presents with less than the listed Core Requirements but is likely to soon posses said requirements, that candidate will be offered a Tentative role of EC until all Core Requirements have been demonstrated to the satisfaction of the DATM.

12
The Flight Deck / X-Plane Auto Startup BATCH File
« on: April 08, 2020, 04:48:22 AM »
This BATCH File will automatically start your X-Plane 11 along with opening many popular websites to help prepare for your flight.

The websites that it opens by default are listed below but is easily editable by the user:

*A google search for your departure and arrival airport x-plane scenery

*A FlightAware analysis for your route

*Skyvector zoomed out to the CONUS and direct routing between your DEP and ARR airports

*AIRNAV pages for your DEP and ARR airports

*Avaition Wx .gov

*Flight plan pre-file pages for both VATSIM and PilotEdge



Download the new file here:
https://www.dropbox.com/sh/5ocusc5tin3fb33/AABb9zlzEf-XhIvTsJzVSDI4a?dl=0




(note- I am sure there are more efficient methods of doing this but I am just now dipping my toes into coding. Starting with Batch and then moving on from there)

13
The Control Room Floor / Workstation Auto-Setup BATCH File
« on: March 08, 2020, 10:53:25 PM »
EDIT:
UPDATED 15MAY2020 (Added a version check to make sure you always have the most up to date BATCH File release)

---

Ever got online, primed up and realized you forgot to review something, pull up a website, launch a certain program, etc...

Or... just tired of pulling up all the information and launching all the programs you need to control?


Check this out:
https://docs.google.com/presentation/d/e/2PACX-1vTTbx5Szs5I8oveHofFnDDkJxYIWHcb7GqfyQYNXE-JtG2BX6_R0BTyj3DwOqFIRNoco1x8_XwgSc0Z/embed



Obviously this BAT file is designed for use by ZLC ARTCC but anyone that knows how to use google could figure out how to edit this for their own use.

I welcome feedback (I am not a serious coder so take it easy) and suggestions for updates!



BATCH File (contact me via PM if link doesn't work):
https://github.com/KSanders7070/Virtual_RADAR_Client_Workstation_Setup/releases

14
The Control Room Floor / v7340.2 ISR
« on: February 11, 2020, 08:21:17 PM »
UPDATE 08MAR2020:
Here is the File. I won't have it here forever.


https://www.dropbox.com/s/090rawcbw5zelda/3LD%20TELEPHONY%20v7340_2.zip?dl=0


:::::::::::::::::::::::::::::::::::::::::::::



Hello All,

I am in need of the collective knowledge here.

At ZLC, we have a command that opens your browser to a webpage that tells you the aircrafts telephony. It is not the most efficient method for finding this information so we wish to upgrade it to what we coined as an "In-Scope Reference (ISR)" message.

This ISR would return both the 3 Letter Identifier (3LD) and Telephony of an air-carrier within the scopes frequency text box so that nobody other than the user can see this information. (for those that are familiar, it is simply an override message to yourself)

The command will be just .id. Then without a space, the user would type out either the 3LD of the carrier in question or the name they heard the pilot refer to themselves as.

Example:

.idBAW (enter)

or

.idSPEEDBIRD (enter)

would return in the scope:

“3LD: BAW ____ Telephony: SPEEDBIRD”


The data will be based off of the FAA JO Order 7340.2 but I wish to include common fake airlines and various uses of these 3LDs.

Please use this form to submit any of the following. The more the better.
https://forms.gle/t1MA1VX5MBBn2juh9


1) A virtual airline that uses a real world Telephony but not the real world 3LD. Example: One of the major Delta Virtual Airlines goes by “Delta” Telephony but uses DVA as their 3LD instead of the real world DAL.


2) A virtual airline that uses a real world 3LD but uses a different Telephony on VATSIM. Example: Canadian Express Virtual Airlines uses the 3LD of CXA which is “XIAMEN AIR” in real world.


3)  A virtual airline that uses a fictitious 3LD and airline name. Example: 3LD: VVX, Telephony: Example Air


When I am done with the alias file, I will share it here as an edit to this OP and as a reply to this thread.
Example of the ISR attached

15
The Control Room Floor / AFV Client Support
« on: January 25, 2020, 06:12:34 PM »
Tried posting in the support forums on VATSIM.NET but it won't let me make a new topic.

The client crashes when I deselect my RX button and then select it again sometime after.


Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at NAudio.Utils.CircularBuffer..ctor(Int32 size)
   at NAudio.Wave.BufferedWaveProvider.AddSamples(Byte[] buffer, Int32 offset, Int32 count)
   at GeoVR.Client.CallsignSampleProvider.AddSilentSamples(IAudioDto audioDto)
   at GeoVR.Client.ReceiverSampleProvider.AddSilentSamples(IAudioDto audioDto, UInt32 frequency, Single distanceRatio)
   at GeoVR.Client.SoundcardSampleProvider.AddOpusSamples(IAudioDto audioDto, List`1 rxTransceivers)
   at GeoVR.Client.UserClient.TaskAudioPlayback(Logger logger, CancellationToken cancelToken, BlockingCollection`1 queue)
   at GeoVR.Client.UserClient.<Start>b__35_0()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4075.0 built by: NET48REL1LAST
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AudioForVATSIM
    Assembly Version: 1.6.32.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Ninject
    Assembly Version: 3.3.4.0
    Win32 Version: 3.3.4.0
    CodeBase: file:///C:/AudioForVATSIM/Ninject.DLL
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Ninject.Extensions.Factory
    Assembly Version: 3.3.2.0
    Win32 Version: 3.3.2.0
    CodeBase: file:///C:/AudioForVATSIM/Ninject.Extensions.Factory.DLL
----------------------------------------
Castle.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///C:/AudioForVATSIM/Castle.Core.DLL
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
GeoVR.Client
    Assembly Version: 1.0.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.DLL
----------------------------------------
DynamicProxyGenAssembly2
    Assembly Version: 0.0.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///C:/AudioForVATSIM/Castle.Core.dll
----------------------------------------
DynamicProxyGenAssembly2
    Assembly Version: 0.0.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///C:/AudioForVATSIM/Castle.Core.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
    Assembly Version: 0.0.0.0
    Win32 Version: 4.8.4075.0 built by: NET48REL1LAST
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
MetroFramework
    Assembly Version: 1.2.0.3
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
GeoVR.Shared
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Shared.DLL
----------------------------------------
netstandard
    Assembly Version: 2.0.0.0
    Win32 Version: 4.8.3752.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/netstandard/v4.0_2.0.0.0__cc7b13ffcd2ddd51/netstandard.dll
----------------------------------------
SharpDX.DirectInput
    Assembly Version: 4.2.0.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
SharpDX
    Assembly Version: 4.2.0.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
NAudio
    Assembly Version: 1.9.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
GeoVR.Connection
    Assembly Version: 1.0.0.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
FSUIPCClient
    Assembly Version: 3.1.11.313
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
NLog
    Assembly Version: 4.0.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.ServiceModel
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3825.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3825.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
Concentus
    Assembly Version: 1.1.6.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.Runtime
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.dll
----------------------------------------
System.Runtime.Extensions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Extensions/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Extensions.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 12.0.0.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
AutoUpdater.NET
    Assembly Version: 1.4.11.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
MetroFramework.Fonts
    Assembly Version: 1.2.0.3
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
RestSharp
    Assembly Version: 106.6.10.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.IdentityModel.Tokens.Jwt
    Assembly Version: 5.5.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
Microsoft.IdentityModel.Tokens
    Assembly Version: 5.5.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4075.0 built by: NET48REL1LAST
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Microsoft.IdentityModel.Logging
    Assembly Version: 5.5.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
Microsoft.IdentityModel.JsonWebTokens
    Assembly Version: 5.5.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
MessagePack.CryptoDto
    Assembly Version: 1.0.0.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
MessagePack
    Assembly Version: 1.7.3.7
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.Runtime.InteropServices.RuntimeInformation
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.InteropServices.RuntimeInformation/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.InteropServices.RuntimeInformation.dll
----------------------------------------
System.Memory
    Assembly Version: 4.0.1.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
System.Memory
    Assembly Version: 4.0.1.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
System.Runtime.CompilerServices.Unsafe
    Assembly Version: 4.0.4.1
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
NaCl.Core
    Assembly Version: 1.2.0.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
MessagePack.Resolvers.DynamicEnumResolver
    Assembly Version: 0.0.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
MessagePack.Resolvers.DynamicUnionResolver
    Assembly Version: 0.0.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
MessagePack.Resolvers.DynamicObjectResolver
    Assembly Version: 0.0.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.Threading.Tasks.Extensions
    Assembly Version: 4.1.0.0
    Win32 Version:
    CodeBase: file:///C:/AudioForVATSIM/GeoVR.Client.dll
----------------------------------------
System.Buffers
    Assembly Version: 4.0.2.0
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------
InputBox
    Assembly Version: 1.0.0.1
    Win32 Version: 1.6.32.0
    CodeBase: file:///C:/AudioForVATSIM/AudioForVATSIM.exe
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



Pages: [1] 2 3