jaybird1nyc

I'm having the same issue. No idea why, but add me to the list.

Rob, Just had the BEST flight with v4.1. Flew north, up the Hudson river, VFR. Past NYC, the Tappan Zee, West Point, etc (Using Bijan Fall Season) all the way up to Saratoga. Mostly hand flown, almost a sin to press AP. Best flight I've had in a long time. Don't known how you can get that 'feel' so perfect (as Carl said) but we are so fortunate to have you with us. I pray you will continue, good health at the forefront. I mashed the donate button as soon as I landed. Not life changing, obviously, but just as a thank you for the past, the present, and whatever the future holds for us... Godspeed Rob Best, Jay

I'm betting that Epictetus never had a flight sim that just HAD to be tweaked 🤪

Can everyone having these recent CTD issues try turning all traffic OFF just to test. No live traffic and no AI traffic and try a couple of flights. It might bring all of us closer to figuring out if it's traffic related or not. It could be some ATC interaction with traffic, so it wouldn't matter if it's live traffic or AI traffic. It could also be a new SimConnect issue having to do with traffic, or ATC. No traffic and report back

Ryan, I have the same problem and I reported it via Zendesk. They wrote back with a few suggestions, none of which worked, and marked it solved. I re-opened the ticket and they wrote back saying it has been logged as a bug and escalated. Have you reported it? -Jay.

Looks like this is it: https://www.flightsim.ee/products/migration-tool/

Just wanted to wish my American brothers and sisters in the flightsim community a very happy 4th: May God Bless America

Same for me, Bert. I'm sure JL is all over it!

Howard, I have to agree with Mad_Mac's view. It works fine with P3Dv4.4 and it's also my "go-to" ATC replacement. Has been since FS9. There are a number of issues and the support is still pretty much non-existent. That being said, I still use it on every flight and put up with it's eccentricities (I'm being kind) because it does the job. In my long experience using VoxATC the vast majority of problems are caused by 3rd party airports having errors in their AFCAD. It really helps if you have at least a working knowledge using Airport Design Editor. Regarding the issue that vadriver brought up about the indexer not reading P3Dv4 scenery correctly, I have not had that issue at all. The indexer correctly recognizes all of my 3rd party scenery, and many, many airports that I've edited myself, whether they are in the scenery.cfg or via the add-on XML method. Any other questions, fire away! Jay

Oh, lol, I thought you meant to actually enter expert mode...DUH. Maybe we should call it Mad_Mac Mode 😁 I also noticed that the '0. Report clear of runway' prompt won't go away. I'm gonna try that tip next time, if I can actually remember to close my flight plan that is 🤔

@ Mad_Mac I was just testing my newly installed P3D 4.4 using VoxATC (all good so far!) and I was thinking about what you said re not being able to close your VFR flight plan. Once you switch to an IFR plan that option is no longer available. So, I guess that's one more thing we're gonna have to live with until it gets fixed. I don't think you can switch to advanced mode while VoxATC is enabled, so I'm not sure if it's even worth it to do the whole disable, run the advanced settings app, switch to advanced (Expert?) mode, then enable VoxATC again just to close the flight plan. Guess it's up to you if you want to. Most of the time I don't even bother to close my flight plan... Yeah, I know... @ supersym I didn't know that's how it was in France, with some non-towered fields being 'controlled' by those agents you mentioned. I should have specified that my 'fix' was probably only useful in the US. Sorry about that. Happy Flights, Jay

I use ADE all the time, but by just adding a tower frequency all you are doing is converting a non-towered airport into a towered airport (as far as VoxATC is concerned). Kind of ruins any sense of realism of flying into an uncontrolled field. Thanks Kevin, maybe it'll get fixed in the next release. I did report this to Tegwyn 2 years ago...

Jeff, Just to follow-up on some points you made. Once you are approved for your approach request you are on your own as far as vectoring and altitude. You are expected to fly the approach as published, until you report the FAF. At that point you're told to switch to either tower or CTAF freq, where you will be given clearance to land. Oh, something I just remembered, if your approach request is met with 'unable at this time' then just wait until you are given a new squawk code and then make the request again. You will get approved this time. Don't have any clue why. About the multiple approaches issue. VoxATC will only display the approaches that are coded in the AFCAD. I have also tried to add, let's say, a Y and Z RNAV to the same runway using ADE. While I didn't know the default ATC would recognize both (haven't looked at default ATC in many years) I did know that VoxATC won't. My own workaround is this; if it's really necessary to have a Y and Z, for example at KEWR there's an RNAV X and Y into runway 29 that are completely different, and I use both, then I use RNAV for one and add a GPS approach for the other. I also add the proper X or Y to the header which helps me remember what I did, and which one is which. Does that make any sense? Jay

I know you're just joking, but of course that would work. 😉 I tried your suggestion a while back, and it will work, but you don't the 'happy ending' that you do using my trick. 😁 The only hassle is switching to an IFR flight plan before arriving at your destination. Now I always have a VFR and IFR plan set up in advance to make it easier and I just disable VoxATC, use FSUIPC's 'Load Plan' menu to quickly switch plans, and the re-enable VoxATC. It's an acceptable workaround until it gets fixed (if ever...)

Hi all, First, I admit this a hack, not a solution, but bear with me and hear me out. I fly alot of GA into non-towered fields and I miss not being able to complete the flight since VoxATC v7 has a still has that unresolved bug that leaves you hanging after you report the arfield in sight. If you don't know what I'm talking about then this hack doesn't apply to you. Ok, here goes, you need to be on a IFR flightplan into a non-towered field. At the appropriate time, request an RNAV approach. When you get close to the field (5-10 mi) start to line up for a standard VFR pattern entry. Report the IF to VoxATC. Enter the downwind leg as per normal VFR procedure. Report the FAF to VoxATC. You will be told to switch to advisory frequency. Upon doing so, you will see the old menu choices (!) 0. Report Downwind, 1.Report Base, 2. Report Final, etc. Ok, I said it was a hack! Gimme a break, jees... But it works. Ok, further investigation allows you to begin the flight as VFR and then, at some point, switch to an IFR plan to the same field. At that point continue with the above instructions. Someone help me out with this, PLEASE!!! (I check for VoxATC v.7.4.3 every day...) Regards, Jay

Hi Jeff, I'll take a swing at this since nobody has chimed in yet. Once you request a different approach from VoxATC, it won't provide vectoring or altitudes any longer. It's now up to you (and your GPS!) to do these. Requesting different 'types' of approaches also cause VoxATC to require different responses, eg. asking for a VOR approach will trigger VoxATC to ask when your base turn is complete, and when you are beacon outbound, etc. Requesting an RNAV approach will only require 2 replies, first will be the IF (Intermediate Fix) and then the FAF (Final Approach Fix). After you respond to the latter, you will then be handed off to either the tower (if airport has one) or to the advisory frequency (CTAF). Now, more specifically, KTIX RNAV(Z)18. Looking at the approach plate, I see that FORNI is a transition, therefore shown as an IAF (Initial Approach Fix). Now, I don't know if the airport you are using is coded correctly, but, assuming it is, do you see the FORNI transition on your GPS? If you do, then what you would do is navigate to FORNI, at or above 1600', then turn right to 137 to CUTON, at or above 1600', report CUTON, then VoxATC would ask you to report POPHY, the FAF. Once you do that, you should be told to switch to Tower at 118.9. Also, you seem to be mixing the 2 RNAV18 approaches, Y and Z. I don't know which one is coded in the airport you're using, but you need to pick only one. I don't believe that FSX/P3D allows more than one type of approach per runway. Maybe someone with more knowledge about this will add their insight. Hope this helps a little Regards, Jay

Hi Kevin, I can absolutely tell you how it used to work. Now, we are only referring to VFR flights into uncontrolled fields. VFR flights into towered fields works fine. Ok, so, you takeoff from your departure field, controlled or uncontrolled, doesn't matter. Soon after you are prompted to switch to a departure or some other interim frequency. There you report your position and altitude and request traffic advisories. You are then given a squawk code and given traffic advisories as needed enroute. As you near your destination you are prompted to switch to the appropriate approach controller. Soon after you are prompted to "Report airfield in sight". When you do so, there is no further contact from Vox, only traffic advisories. Now, what should happen, and what USED to happen prior to v7 is that when you report airfield in sight is that you were prompted to switch to advisory (CTAF) frequency. You then asked unicom for field advisory and then were given prompts to 1.Report downwind, 2.Report Base, 3.Report Final, 4.Report clear of runway. (Possibly report going around, but not sure) That's how it used to work. Without that final handoff to the CTAF there's no way to properly complete a VFR flight into a non-towered field. I reported this behavior to Tegwyn nearly 2 years ago. Hope this helps. Best, Jay

It's not about "improved VFR". VFR flight in to uncontrolled fields worked fine up until v7, so something got broken and was never fixed. I reported it to Tegwyn nearly 2 years ago, when beta7 was released and he never addressed it. Not asking for any improvement, just that it works the way it used to. Jay

Very disappointed that the issue regarding VFR into uncontrolled fields hasn't been fixed. It was reported over one year ago, I just reported it to Tegwyn - AGAIN I haven't noticed any other differences compared to 7,41 Jay

I would like to see this fixed as well. This was the same behavior in the original version and never addressed, although being reported to the developer. Additionally, the 2D Autopilot pop-up VS wheel direction is reversed. I mean, it's not like a deal-breaker, but it's just frustrating. Great job in updating one of my all-time favorite planes but why not apply a bit of polish to a great aircraft? Should be a relatively simple fix for the developer...

Hi Rob, Yes, this issue affects me, and others here on the forum have reported the same. It has been reported to the developer and we shall wait and see if it has been addressed in the next update, hopefully in the not too distant future! In the meantime just bear with it, not much else to do. Jay

On my system it only seems to happen when the FO is reading back a frequency change and the radio actually changes the frequency a bit too soon.

Hi Scott, Really glad it worked! Why ask why, right. It just works. Happy flights. Best, Jay

Hi Scott, I have been trying to get this working and, like you, I haven't been able to get the VOR 1 needles to move. I also tried, unsuccessfully, all the combinations of LINK: this to that, etc. I think I've found something that works, at least it seems to work for me. Maybe you can try it. It seems the default state is for COM1/NAV1 is set to OFF. If I go into the menu, toggle the panel to KX170 and then manually turn on both receivers and then go back and switch back to the 530/430 config it seems to work. I even tried flying an LPV approach and I got needle deflection on both the vertical and lateral. I'll paste my RealityXP.GNS.ini below, but I'm not sure if any of it matters. The only thing that worked was to manually switch on COM1/NAV1 radios. Note: I only use the 530, haven't tried the 430 yet and also this is using the Warrior, but it should be the same for the Arrow. RealityXP.GNS.ini: [GNS_530_1] ; is the master device if true. MasterDevice = true ; selects COM/NAV Radios '1' or '2'. RadiosPair = 1 ; uses computer time if true, simulator time otherwise. ComputerTime = false ; integral lighting percent (0 to 100) Rheostat.Display = 100 ; integral lighting percent (0 to 100) Rheostat.Buttons = 75 ; connects GPS to HSI if true. LinkHsi = false ; connects GPS to HSI course if true. LinkCrs = true ; connects HSI OBS to GPS if true. LinkObs = false ; connects GPS to VOR if true. LinkVor = true ; connects GPS to Autopilot if true. LinkOto = true ; connects CDI key to NAV/GPS switch if true. AutoNavGps = true ; selects VLOC NAV '1' or '2'. '0' selects same source as 'RadiosPair'. AutoNavSource = 0 ; sets device power source: ALWAYS_ON,AVIONICS_BUS,MAIN_BATTERY PowerSource = AVIONICS_BUS ; sets device power knob switch mode: NONE,DEFAULT_ON,DEFAULT_OFF PowerKnob = DEFAULT_OFF ; connects GPS to Shadin Air Data computer if true. UseAirData = true ; connects GPS to Shadin Fuel Data computer if true. UseFuelData = true ; connects GPS to RYAN 9900BX if true. UseRyanTcad = false ; sets TCAD sound alerts volume in percent: 0 to 100. RyanTcadVolume = 50 ; connects GPS #1 to GPS #2 if true (both required). UseCrossFill = false ; enable device failures if true. UseFailures = false ; uses Simulator GPS commands if true. UseSimGpsCmds = true ; updates Simulator GPS flight plan if true. LinkSimGps = false ; saves the active route as a Simulator flight plan if true. AutoSavePln = false ; use legacy mouse (left CCW, right CW, middle Push) (override instances settings) UseAltMouse = true ; use legacy GNS WAAS 3rd party aircraft panel variables (L:Vars). UseLegacyVars = false ; sets fuel type: AVGAS,JETA,JETB FuelType = AVGAS ; sets TAWS type: TERR,TAWS TawsMode = TERR ; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY TawsSurface = HARD_SOFT ; TAWS minimum runway length (feet) TawsMinLength = 40 ; HSI lateral deviation scale factor. CdiScale = 1 ; HSI vertical deviation scale factor. GsiScale = 1 ; sets master sound volume in percent: 0 to 100. MasterVolume = 100 ; selects the CPU running the trainer process: 1 to 32 ; 0: last core, -1: automatic. CpuAffinity = -1 ; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 [GNS_530_1.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popleft = 15531 ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 [GNS_430_1] ; is the master device if true. MasterDevice = false ; selects COM/NAV Radios '1' or '2'. RadiosPair = 1 ; uses computer time if true, simulator time otherwise. ComputerTime = false ; integral lighting percent (0 to 100) Rheostat.Display = 100 ; integral lighting percent (0 to 100) Rheostat.Buttons = 75 ; connects GPS to HSI if true. LinkHsi = false ; connects GPS to HSI course if true. LinkCrs = true ; connects HSI OBS to GPS if true. LinkObs = false ; connects GPS to VOR if true. LinkVor = false ; connects GPS to Autopilot if true. LinkOto = true ; connects CDI key to NAV/GPS switch if true. AutoNavGps = true ; selects VLOC NAV '1' or '2'. '0' selects same source as 'RadiosPair'. AutoNavSource = 0 ; sets device power source: ALWAYS_ON,AVIONICS_BUS,MAIN_BATTERY PowerSource = AVIONICS_BUS ; sets device power knob switch mode: NONE,DEFAULT_ON,DEFAULT_OFF PowerKnob = NONE ; connects GPS to Shadin Air Data computer if true. UseAirData = true ; connects GPS to Shadin Fuel Data computer if true. UseFuelData = true ; connects GPS to RYAN 9900BX if true. UseRyanTcad = false ; sets TCAD sound alerts volume in percent: 0 to 100. RyanTcadVolume = 50 ; connects GPS #1 to GPS #2 if true (both required). UseCrossFill = false ; enable device failures if true. UseFailures = false ; uses Simulator GPS commands if true. UseSimGpsCmds = false ; updates Simulator GPS flight plan if true. LinkSimGps = false ; saves the active route as a Simulator flight plan if true. AutoSavePln = false ; use legacy mouse (left CCW, right CW, middle Push) (override instances settings) UseAltMouse = false ; use legacy GNS WAAS 3rd party aircraft panel variables (L:Vars). UseLegacyVars = false ; sets fuel type: AVGAS,JETA,JETB FuelType = AVGAS ; sets TAWS type: TERR,TAWS TawsMode = TERR ; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY TawsSurface = HARD_SOFT ; TAWS minimum runway length (feet) TawsMinLength = 40 ; HSI lateral deviation scale factor. CdiScale = 1 ; HSI vertical deviation scale factor. GsiScale = 1 ; sets master sound volume in percent: 0 to 100. MasterVolume = 100 ; selects the CPU running the trainer process: 1 to 32 ; 0: last core, -1: automatic. CpuAffinity = -1 ; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 [GNS_430_1.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 Jay

Just wanted to say thank you to Jean-Luc for putting these fabulous units on sale. I finally got off the fence and bought both the GNS-430W and 530W. Already got them working in my beloved A2A C-172 & C-182, including working, fully coupled LPV approaches! Next is the Cherokee and Comanche. Can't wait! I'm probably gonna regret passing on the GTN650/750, but this is all I could handle right now. If anyone has been waiting for the right time, this is it. Thanks again Jean-Luc, great work! Jay