jabloomf1230

The FS market has expanded so much since MSFS was released that I doubt that the Navigraph survey results will be representative. The Navigraph survey tends to reach serious users rather than casual simmers. The MSFS market isn't 1000x times bigger, that's just hyperbole, but I'd bet that it's 90% of the installed base.

This is probably too much work, but could you consider color coding the gates by Airline code in the same manner that Airport Design editor did? Perhaps the ADE author would let you use the ADE airline datafile with the RGB codes. The file is parkingspaces.dat.

TrackIR is one of the most reliable pieces of PC hardware that I have ever used. I bought a high end VR headset, got tired of the poor visual quality, software glitches, poor performance and the lack of comfort. I went back to my trusty TrackIR.

I think that the taxiway naming scheme is highly dependent on what airport you are talking about. Many of the bigger US MSFS stock airports have taxiways named correctly. When it comes to taxiway network glitches, that's another story altogether. Most of the taxiway geometry is correct, but every so often a taxiway is isolated because it is incorrectly connected to a vehicle path. And gate numbering is haphazard also. Of course, there are no airline codes for MSFS gate parking spots for the stock airports. In any case, the data source dictates whether gates and taxiways are true to the real world airport. Asobo and Blackshark AI couldn't do anything about either missing or incorrect data. 3rd party ATC apps can only work with the airport data that's available. VOXATC isn't any different in that regard. If your local MSFS stock airport has mistakes, your best option is to search for a version in flightsim.to, etc. that is correct. What I do for airports that I fly to to on a regular basis is to create a whole new airport in MSFS developer mode that inherits everything from the stock MSFS airport. Then I fix the taxiways, gates and add airline codes. It's not so bad, once you try doing it.

So far with the closed MSFS beta, the answer is no. Taxi schemes vary so much for each airport. Prevailing conditions also impact the scheme. At some airports, ATC may issue a taxi clearance to a runway with intermediate taxiways (as you've suggested), while at others ATC may issue a taxi clearance to a holding point and then issue a second clearance as the aircraft approaches that point. Most airports that I'm familiar with, use standard taxi routings to the runway's furthest hold point. It's difficult to see how to allow the flexibility that you suggest without making the logic overly cumbersome for all airports. I will pass this along to the full development team, though.

I agree with Kevin on all those points. I will add, that the VOXATC panel does allow for pilot-initiated options during a flight. Just like the P3d and MSFS ATC, there are numerical options (0, 1, 2,...) that are available at various junctures, as appropriate. These options allow the pilot to prompt ATC to ask for different cruise altitudes, different approaches/arrivals and to turn on the taxi guides, in case on gets lost trying to follow the ground controller's directions for a complex departure airport. The pilot can also report cruise position, altitude, etc. to ATC as needed. BTW, the VOXATC taxi guides are not those ridiculous giant blue things that are spawned by the default MSFS ATC. They are inobtrusive horizontal cones that point the way. The VOXATC UI also displays simple maps of the departure and arrival airports as appropriate. The VOXATC UI panel is HTML-based and its webserver can be mirrored to any device with a browser.

Actually, VOXATC requires that you have a microphone (headset or desktop will do) available, but for IFR flights, you can switch the communications to a virtual First Officer, so no microphone is needed until you reach the parking spot of your destination airport. You can also use speakers rather than a headphones. Of course, the more these options are used, the less immersive is the experience.

I'm hoping that the BSQ Duke meets our high expectations, which were set by the unrelated incredible FSX/P3d version. When I had XP installed, I bought the Duke for that platform and it was a disappointment. BSQ and A2A have both positioned themselves as the premier GA aircraft vendors for MSFS, so I suspect that the Duke will be great also.

I use Windows built-in, Cereproc and Ivona voices. With the two VOXATC filters, that gives you 3 unique voices for each SAPI voice. Whether the release MSFS version will have different voices is unknown, but the VOXATC closed beta has more than enough voices just based on the Windows built-in set.. The main advantage of VOXATC is that it controls and communicates with its AI aircrafts' "pilots", just like it does with the user.. It's incredibly realistic for that reason alone. That feature seems quite lightweight with regard to sim performance.

I'm running the most recent version of LNM and I only noticed that the 3rd party airport is not displayed on the map because it has different gate numbers than the MSFS stock airport. The map display is definitely the stock MSFS airport, as I checked some of the other features. The 3rd party airport shows up correctly in MSFS. Here's what LNM sees: The add-on airport viability button has no impact on what's displayed. I've also rescanned the scenery library and rebooted to no avail. Any thoughts? EDIT: I disabled World of Jetways KALB.bgl, so it wasn't a LNM issue at all.

Just a quick update for VOXATC for MSFS. The author is fine-tuning the MSFS user interface and also incorporating a few extra connections to another MSFS AI aircraft add-on. Someone asked for the latter on the MSFS official forums. 😉 In my opinion, the MSFS 2020 version of VOXATC will satisfy the most picky simulator pilot, when it comes to ATC. The only unknown at this point is the uncertainty surrounding the release of MSFS 2024. Asobo could break things in MSFS that could render 3rd party add-ons useless.

REX WeatherForce.

I used to maintain 3 flight sims. But I learned the error of my ways and uninstalled P3d5 and XP.

Kevin and I have been testing VOXATC for MSFS and it's pretty much set to go.

The mistake that MS has made was shutting out a large portion of the installed base even though most of those PCs are powerful enough to run the OS. I installed Win 11 on my laptop and after playing around with it I see zero advantages in upgrading either my desktop PC or my wife's laptop. I'll wait until Windows 12. 😉