Nick M

Thanks for the update Fess. Yeah, if you manually moved parts of the installation around due to the Comanche not showing up in P3D v4.2 (before you found the topics describing the "add-ons.cfg" trailing backslash edit) this will almost certainly be the reason the Accu-Sim update didn't work as expected. Good to hear you're back in business anyway. Nick P.S. The info on the "add-ons.cfg" edit for A2A aircraft in P3D v4.2 is also pinned at the top of this forum.

Okay, thanks Fess. Your best bet to get support for A2A products is to post on their tech support forums. The Comanche forum is here: http://a2asimulations.com/forum/viewforum.php?f=125. Nick

Fess, After you reinstalled Prepar3D v4.2 and the A2A Comanche, did you remember to install the latest Accu-Sim update from A2A that addresses the ground steering issue? (Accu-Sim Update 10_12_2107.) It's available on their support forums here: http://a2asimulations.com/forum/viewtopic.php?f=23&t=57819. Nick

Yes, if you select the default installation path for your A2A add-ons in "Documents\Prepar3D v4 Add-ons", the "add-ons.cfg" file in "\AppData\Roaming\Lockheed Martin\Prepar3D v4" is the one which will be written to. The other "add-ons.cfg" file in "ProgramData" is used in the event of installation to a custom directory. Nick

Aha - thanks for the extra info Elaine, that's great. Nick

Thanks for pinning the post Elaine. Just for info, I did raise the matter on the Prepar3D forums too, and Rob McCarthy responded that it was being looked into, but the topic has since disappeared by the looks of it. The original post was here and I can't seem to find it elsewhere on the forum there. Hopefully it's just a glitch as I don't think I said anything controversial! Nick

Just though I'd repost this information from the A2A forums in case it's helpful to A2A Simulations customers who rarely visit their forums. The release of Prepar3D v4.2 yesterday seems to have thrown up an issue affecting some A2A customers. The Problem A2A aircraft installed to a custom directory such as "F:/Prepar3D v4 Add-Ons/A2A" no longer appear in the list of vehicles in Prepar3D v4.2. The Cause The A2A installers command the Prepar3D.exe to write the custom installation path to an "add-ons.cfg" files stored in the user's "ProgramData" directory. In Prepar3D v4.0 and v4.1, this path supported a trailing backslash, but in Prepar3D v4.2 it appears this is no longer the case. The Fix (For Now, Anyway) To resolve this issue, please open the "add-ons.cfg" file in the following location... C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg ...Find the line beginning "PATH=" which records the location where your A2A add-ons are installed, and edit this line to remove just the trailing backslashbefore saving the file. For example, if the line reads "PATH=F:\Prepar3D v4 Add-Ons\A2A\" edit it to read "PATH=F:\Prepar3D v4 Add-Ons\A2A" instead. Note: By default the "ProgramData" directory is hidden to protect its contents so you may need to 'unhide' it as described here. Thanks, Nick

The A2A forum is probably the best place to find info on operating their Comanche. Hopefully this topic will help a bit. In short, you won't go far wrong with the multi-weight (20W-50) option. Cheers, Nick

Also, bear in mind that it's easy to freely browse the forums here and evaluate the standard of support being offered and even ask questions, before you take the decision on whether to purchase or not. With some other add-ons, it's necessary to purchase the product before you are able to view (let alone post on) the dedicated tech support forum. Nick

Yes - thanks for another very useful update. I do appreciate the configurable power on/off functionality. And not to forget... New: Added wind vector to map page. Regards, Nick P.S. Because I already had the v2.3.5 RC installed, the "check updates" feature showed my installation as already up-to-date. However, this was easily resolved by re-downloading the e-commerce installer.

That's good new indeed Jean-Luc! Thanks for the prompt addition of this feature and for the notification. Interesting also to read your explanation above as to why the power on/off switch functionality isn't currently implemented. I'd also be happy to see this in a future update if possible. And whilst we're talking of future updates, one other quick question (I believe others have mentioned the same thing). Any chance you'll add some subtle click sounds associated with button presses and knob rotation in a future update? Thanks, Nick

Scott, If it's any help, I could send you a preconfigured panel.cfg file for any of the A2A GA planes you plan to use the GNS 530 V2 with - just let me know which one(s). Cheers, Nick

Ted, Provided that the virtual cockpit has the 3-D geometry in place to support an existing GNS unit (or units), it shouldn't be a problem to integrate the equivalent RXP GNS V2. That's exactly what I've done with A2A and RealAir's products. It just requires some minor edits to the panel.cfg file which can be done manually or with the help of the RXP installation tool. Nick

Scott, I guess it's difficult for most of us to make direct comparisons between the two principal GNS products on the market because the likelihood is that we'll buy either one or the other. In my case it was the RXP GNS 530 and I've been more than happy with the product itself and the support from Jean-Luc. As an RXP customer from a while back, I'm well aware of the hiatus in terms of development and support for existing products, but I welcome the return of RXP: competition drives innovation and all that! My decision to go for the RXP offering was driven mostly by the richer set of features. However, I'll admit that the pricing made me think carefully. Although the RXP products are very good value compared to F1's original pricing structure, F1 did drop their prices dramatically as you noted. I also suspect this was a direct result of the reemergence of RXP as an active developer for FSX/P3D. Whilst I didn't expect RXP to match the new pricing level set by F1, I hoped for something like a half price 430 for 530 customers, and vice-versa. It's worth pointing out that although both products use the Garmin trainer, the RXP GNS units use an updated version 3.3 which is compatible with newer database files from the GTN trainer. There are also a number of other features which seem useful to me: the keyboard shortcuts as mentioned above, the excellent in-sim GUI for changing settings and of course the TAWS-B/TCAD and crossfill functions. Another factor which drew me to the RXP was the fact that the pop-up display doesn't disable the unit's screen in the VC. New features are being added continually and one that I really like is the fact that the NAV volume control can be used to adjust the volume of morse idents. (I believe it works by adjusting the global 'cockpit sounds' level.) There are a few things I don't like with the RXP implementation though. The COMM volume switch on the bezel works too, but its power-off position isn't implemented at present, though I'm hopeful it will be with a future update. The wind vector is also missing, though J-L has indicated that this may be fixed in the next update too. I also dislike the startup screen somewhat, specifically the fact that it shows a "registered to [my name]" message or words to that effect, which is a bit of an immersion killer in my opinion. Anyway, my vote is for RXP! Nick

Thanks for the update Jean-Luc - is there any chance you could post the changelog? (Apologies if I've missed this elsewhere.) One thing which still seems to be missing in my (530) installation is the wind vector. I seem to recall this was discussed before; is it something you're hoping to add with a future version? Regards, Nick

You're welcome Jay. One other thing to bear in mind is that to use the full functionality of the KAP 140 autopilot simulation in the A2A Cessnas, you'll need to make sure "connect GPS to VOR indicator" is ticked in the RXP configuration panel. You'll also want to make sure you have the the latest RXP update installed. Regards, Nick

Hello, Just to give a bit of context for the benefit of anyone who reads this thread, the text you quoted relates to swapping around predefined panel.cfg files that A2A Simulations provide with their products to enable add-on GPS integration. Ordinarily this process would be done by the "A2A Aircraft Configurator", but at the time of writing, this utility doesn't support the new P3D-compatible RXP GNS. To clarify, you can just delete the existing "panel.cfg", and then rename your edited copy of "panel_RXP_530.cfg" to just "panel.cfg", thereby replacing it. If you wish to restore the default panel.cfg for any reason, simply run the A2A Aircraft Configurator and select "DEFAULT". Thanks, Nick

Thanks for the update Jean-Luc, I can confirm that the "connect GPS to VOR indicator" bug is indeed resolved, so with this option ticked it's now possible for the A2A KAP 140 simulation to follow LPV (etc.) guidance whilst using NAV2 to tune an independent frequency. The adjustable COM and NAV ident volumes are also a very welcome feature. The latter works by adjusting the "cockpit" volume slider if I understand correctly? Also, the new facility to adjust the HSI lateral deviation scale helps me to understand the lateral tracking issue we're seeing in the S-TEC 30 equipped A2A Comanche and Cherokee. However, I'll post any relevant remarks in the original thread discussing this issue. Thanks again, Nick

Hi Jean-Luc, Thanks for the update - I look forward to trying this one out. With respect to the CDI and GSI animation in the A2A aircraft, both seem to be working as expected. It was just the autopilot tracking which was the issue. In fact, on a (probably) unrelated note, I did test the A2A Comanche with the GNS 530 installed and observed the same behaviour described in this thread. Once I have your build installed, I'll retest with both the A2A autopilot simulations and let you know if there seem to be any outstanding issues. Cheers, Nick

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

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

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

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!

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

Hmm! "This app is only available on the App Store for iOS devices." How very - Appley! Nick