jaybird1nyc

Members
  • Content count

    190
  • Joined

  • Last visited

About jaybird1nyc

  • Rank
    Member

Flight Sim Profile

  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Contact Methods

  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    KBLM

Recent Profile Visitors

1,775 profile views
  1. 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.
  2. Hi Scott, Really glad it worked! Why ask why, right. It just works. Happy flights. Best, Jay
  3. 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
  4. 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
  5. 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.
  6. 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
  7. 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
  8. 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.
  9. 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
  10. 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
  11. I guess it's worth trying. I doubt you could mess anything up that couldn't be fixed simply by re-indexing with the 7.4 version. I'm highly sceptical that anything would be "fixed" but, hey, give it a go, see what happens. I, also, have had issues with all of the betas and now the release version not properly processing add-on airports. My issues were primarily with VoxATC not picking up approaches that I had updated using Airport Design Editor.. You are correct that this wasn't the case with v6. The developer has acknowledged that there is indeed a problem, I have sent him many error logs, and we have been in contact regarding this issue. He seems confident that it will be fixed soon. Oh, and regarding your weather issue, I also use AS16 and I don't have any issues with winds being reported as calm at any destination airport I've tried (unless they actually ARE calm). I do have 'no wx updates on approach' selected. Jay
  12. Jay, I got a reply from Tegwyn early this morning. He said he was looking into it. You're not wrong about it being the pilot's responsibility to contact unicom and then to self-announce your pattern entry and turns all the way in. It's just that the behavior in V7 is unlike any previous versions. It's not like you CAN'T do it all without VoxATC displaying the required calls to make, It just feels like you're left hanging. Also, why would ATC tell you to "Report airfield in sight" and then when you do, they don't respond at all? Has to be an issue in VoxATC. Hopefully, Tegwyn can find out what's going on quickly. There was indeed a problem in all the beta versions where you were unable to contact Utopia Radio. Yes, you are correct that the quick fix was to edit the airport in Airport Design Editor and add an FSS frequency. It's a moot point now that V7.4 is out. The problem was fixed. One less thing to do...
  13. Installed the v7.4 demo yesterday and I still have the same issue as with all the previous betas. After approach tells you to "Report airfield in sight", and you do so at the appropriate time, there is no further instruction given. Traffic advisories do continue, but you are left hanging with no instruction to contact Unicom/CTAF and no pattern callouts. Sorry, this applies only to non-towered fields. Flying VFR into towered fields works fine, as it did with the betas. I've sent Tegwyn this info, but no reply as of yet... On a positive note, the issue about being unable to contact "Utopia Radio" to open your flightplan has been fixed - YAY Jay
  14. Well, sure, you can fly only IFR until it's fixed (we hope!) You can even fly to/from non-towered fields under IFR. The developer added a feature that was my suggestion, that being, the ability to get IFR clearance at a non-towered airport. This feature was not available in previous versions and it really works well. I've made a number of suggestions but most have not been implemented, but this one was. You actually can fly VFR FROM a non-towered field. You just have to take a look at the bgl with ADE to see if it has a dedicated FSS frequency, and if it doesn't, add one, compile, and replace the existing bgl with the updated version. For me it's not a big deal. I only use add-on airports and ones that I have done myself. So, it's not that many to deal with, and you only have to do it once. You still can't fly VFR TO a non-towered field due to the issue we've already discussed. I'm also having some really weird issues with Vox processing add-on bgls. I think I'll start another thread, maybe somebody smarter than me has an idea. Jay
  15. Above is a post I made back on May 1st, so, yes, this is a verified bug. Only way around this is to use only towered airports for your destination. Seems to work OK using towered fields, even under VFR plans. The other issue I mention in the post, about being unable to open a VFR flightplan when asked to contact "Utopia Radio" seems to be a deal breaker. Only way I've found to avoid this error is to inspect the departure airport's bgl using Airport Design Editior and checking the Comms list to see if it has a dedicated FSS frequency. If it doesn't then it will use the dreaded "Utopia Radio" and you're stuck. So, I just add an FSS frequency, re-compile the bgl and replace existing one with the modified version. Jay