jaybird1nyc

Bronze
  • Content Count

    195
  • Joined

  • Last visited

Community Reputation

6 Neutral

About jaybird1nyc

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    KBLM

Recent Profile Visitors

1,896 profile views
  1. jaybird1nyc

    Observations with 7.42.

    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
  2. jaybird1nyc

    Observations with 7.42.

    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
  3. jaybird1nyc

    Observations with 7.42.

    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
  4. 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...
  5. jaybird1nyc

    Issue: FO readback cut off

    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
  6. 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.
  7. jaybird1nyc

    Just Flight Arrow/Turbo Arrow install?

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

    Just Flight Arrow/Turbo Arrow install?

    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
  9. jaybird1nyc

    Reality XP - GTN 750/650 - 30% OFF

    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
  10. jaybird1nyc

    VOXATC Panel in FSLABS A320

    Did you run the Indexer after installing the A320? The Panel Installer won't show any newly installed aircraft until the Indexer is run. Just a thought.
  11. jaybird1nyc

    Difficulty Contacting FSS

    Mac, Yes, that's a good point. I've also noticed that sometimes the prompt changes to "Contact tower on xxx.xx" very soon after beginning taxiing. After it does that, it's too late. That's why I try to contact FSS before taxiing. This is one of those, "I'm going to report this to the dev" items that I never get around to reporting because I always seem to be waiting on a fix to a much more important issue that I reported. Of which there always seems to be... Jay
  12. jaybird1nyc

    Difficulty Contacting FSS

    Hi John, This has happened to me on a number of occasions. So, as you're aware, this behavior is only seen when flying VFR out of a towered airport. You are given taxi instructions and then the prompt tells you to contact FSS to open your flightplan when at the runway hold after runup, at least that's how I remember it being presented. Please correct me if I'm wrong. If you wait until you're at the hold point you get stuck in the loop you've described. My workaround is to contact FSS immediately, don't wait until you're at, or even anywhere near the runway. This has to be done BEFORE the prompt changes to "contact tower on xxx.xx" That always works for me. Try that out and let me know. Good luck! Jay
  13. jaybird1nyc

    Version 7.41 Released

    Mac, Yes, I just tried a quick test flight and my results were similar to yours. Some improvement, but certainly not the overall fix I was hoping for. Some other issues also cropped up, such as the green light taxi path being drawn as a straight line from my parking position all the way to the runway start point. And no taxi instructions as well. And about half of the ATC voice instructions not being heard. Not much good news to report here, but I just did some quick flights to test my previous squawks.
  14. jaybird1nyc

    Version 7.41 Released

    If memory serves it has always been the developer's recommendation to uninstall any previous version prior to installing the new version. Jay Ah, and from the VoxATC webste: The current version of VoxATC X is 7.41. If you wish to upgrade, uninstall your current VoxATC X, VoxPopBase and any VoxPop voices then download and install this version (and the VoxPop voices available here). Registration keys for versions earlier than 7 will not work with this version An updated version of UT2Bridge will be available in a couple of months. Don't upgrade yet if you use Ultimate Traffic with VoxATC
  15. jaybird1nyc

    Version 7.41 Released

    From the VoxATC website: News 6 September 2017 Version 7.41 released Update to 7.4 to fix the following issues: Incompatibility with P3D V4 add-ons that use its new facilities Incorrect behaviour at the end of vectors to the an ILS approach in Europe Faulty sppech recognition issues at some airports Incorrect handling of scenery layers so that add-on airport data not used properly