Nick M

Members
  • Content count

    109
  • Joined

  • Last visited

Community Reputation

6 Neutral

About Nick M

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  1. Okay, no worries; I'll keep an eye on the forum here for any updates. If I think of anything which may be helpful in tracing the issue in the meantime, I'll let you know. Nick
  2. Actually I just got round to performing the same test in P3DV4 using the default Maule M7. The result is exactly the same as described above for FSX-SE. (Even down to the bit about the HSI NAV flag showing in GPS mode in spite of there being valid direct-to course guidance.) However, it sounds like you've not been able to reproduce the same behaviour with your installation(s) Jean-Luc? If not, I can't think of any software I have installed that may be relevant. Other than the A2A aircraft add-ons, EZdok and Orbx scenery, all I have installed in P3DV4 is FSUIPC and I made sure to disable this completely (by moving the FSUIPC5.dll itself) for the latest round of tests. Thanks, Nick
  3. If I click the link in iTunes, it just takes me back to the "iTunes Preview" browser page with the "this app is only available on the App Store for iOS devices" message. I guess it knows I'm trying to download it on a PC or Mac which won't run the software. Perhaps the app store download restrictions have changed recently? Nick
  4. Okay, I tried the test as described in FSX-SE, Jean-Luc, and results appear to be the same for both the C172SP and C208B. With the CDI in GPS mode, a GPS direct-to loaded, and both NAV radios tuned to an in-range VOR... The NAV1 CDI shows deflection to the GPS track and NAV1 DME shows the GPS range*. The NAV2 CDI show the NAV flag and NAV2 DME range is 0.00 NM. Morse ident for NAV2 is inhibited, but ident for NAV1 can still be heard. In other words, needles, DME and ident agree and the NAV2 radio effectively seems to be in a 'failed' state. I can test a bit later with something like the Maule M7 in P3DV4 too, but in my tests so far, behaviour has been consistent across both sim platforms. One other observation: In the C208B, the HSI NAV flag (i.e. NAV1) is visible with CDI in GPS mode, even though the CDI apparently shows valid deflection for the GPS course. Thanks, Nick *I hadn't actually noticed the problem with the DME set showing GPS range until you mentioned it!
  5. Are you accessing iTunes via an iPad Jean-Luc? I can't seem to download the app using iTunes on Windows or even on my MacBook. Nick
  6. Hmm! "This app is only available on the App Store for iOS devices." How very - Appley! Nick
  7. Thanks Jean-Luc, I'll give that suggestion a try. Bert - thanks for your post too! Regards, Nick
  8. Okay, glad I asked the question in that case Jean-Luc. First of all... Yes, good point. I checked and the log file in question shows: 17/09/18 15:28:38.571 07088 - ] # rxpGNS2.dll version 2.3.2.0 17/09/18 15:28:38.574 07088 INFO ] I also confirmed the same version number in properties of the dll itself. This time, I captured images to show the issue in FSX-SE using the default C172SP. However, the same behaviour applies to the A2A products and default aircraft in P3DV4. First of all let's check the behaviour with "connect GPS to VOR indicator" deselected. Here, as image 1 shows, all is okay with the CDI in GPS mode. NAV1 and NAV2 are both tuned to an in-range VOR on 117.00 MHz. NAV1 CDI is showing deflection to the GPS direct-to course. NAV2 CDI is showing deflection to the VOR radial. In image 2, we've got "connect GPS to VOR indicator" selected and the CDI in VLOC mode. Nothing else changed, and again, all is as expected. NAV1 CDI is showing deflection to the VOR radial. NAV2 CDI is showing exactly the same thing. Image 3 should highlight the problem. Here, the only thing we've changed from image 2 is the CDI mode back to GPS. As expected, NAV1 CDI is again showing deflection to the GPS direct-to course. However, this time NAV2 CDI is displaying its NAV flag. It's not deflected to the VOR radial as it should be, or even to the GPS track. Hope this helps to clarify the issue. To be honest, I'm not sure if with the previous version image 3 would have showed NAV2 CDI deflected for GPS course too; I didn't have any GPS guidance active when testing (previous comparison image). Thanks, Nick
  9. Hi Jean-Luc, Update installed, but it seems the "connect GPS to VOR indicator" bug still remains (i.e. GPS taking over both VOR indicators). I assume this one was identified too late to make it into this update? Thanks, Nick
  10. Aha! Thanks for the tip. Yes, this works successfully once the aircraft in question is reloaded. No animation for the inner knob push action, but I presume this was a limitation of the GNS V1 integration too. (i.e. there's no L:Var for this event.) Cheers, Nick
  11. Thanks Jean-Luc. Look forward to the update! Actually, I have another quick question about integrating the GNS V2 with third-party add-ons such as those by A2A. With the GNS V1, the 3-D modelled rotary knobs were apparently animated in the virtual cockpit and responded to mouse control; however, with V2 this feature does not work. Because of the lack of knob animation and sound effects, the feel of interacting with a real unit is rather unconvincing. Just wondered if it's possible to address this in future? Thanks, Nick
  12. I understand from this topic that one of the advantages of the RXP GNS products is that the aviation database ("worldwide.bin" file) can be updated with the corresponding file from the Garmin GTN trainer (which will just need to be renamed). However, a recent change to the GTN trainer means that these files are no longer compatible (i.e. they can't simply be interchanged any more) and I'm unable to find any download links for previous versions of the GTN trainer. Therefore, I was just wondering if anyone still has a copy of the most recent version of the GTN trainer which does include a compatible aviation database? If so, would it be possible to share just the relevant *.bin file (something similar to "006-d0170-00.bin"), to avoid hosting a large download? Thanks, Nick P.S. I have already updated the GNS "bmap.bin" file with the corresponding file from the current GTN trainer.
  13. Okay, thanks for the quick reply. I'll hand fly LPV approaches for now - I can always use the practice, especially in IMC! Nick
  14. Okay, thanks for the added information Jean-Luc; I agree that we seem to be getting there! In answer to your questions... Yes, the radio setting has always been "COM1 / NAV1" and VLOC source "Automatic (NAV1)". I tried changing it to "NAV1" too (and indeed "NAV2"), with no change in behaviour. I took a slightly different approach, and just tested in the default P3D Maule. The result: if "connect GPS to VOR indicator" is selected, setting the GNS CDI option to GPS overrides both the VOR1 and VOR2 gauges as shown here, irrespective of whether the VLOC source option in the *.ini is set to "automatic", "NAV1" or "NAV2". (In the example, both NAV radios are tuned to a valid frequency, but their respective VOR indicators are each showing nav flags because they're being overridden by the GNS which doesn't have any GPS guidance active.) From what you've said above, does this seem to indicate a bug with the RXP gauge? Nick
  15. Yes, if "connect GPS to VOR indicator" is enabled, the autopilot will intercept and track the GPS glideslope as it should. However, when this option is ticked and the GNS CDI mode is set to GPS, the GNS controls both the VOR1 and VOR2 gauges. In other words, the NAV2 radio can't be used for navigation at all, unless the GNS is in VLOC mode. Hope that makes sense? Compare image 1 and image 2 if it helps, where NAV2 is tuned to the HQM VOR (there's no approach loaded in the GNS). Even if I'm following a GPS flight plan or approach, it's always good to be able to use NAV2 and the VOR2 gauge to track ground-based navaids. Nick