Nick M

  • Content count

  • Joined

  • Last visited

Community Reputation

19 Neutral

About Nick M

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nick M

    A2A ground steering P3D v4.2

    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.
  2. Nick M

    A2A ground steering P3D v4.2

    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: Nick
  3. Nick M

    A2A ground steering P3D v4.2

    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: Nick
  4. 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
  5. Aha - thanks for the extra info Elaine, that's great. Nick
  6. 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
  7. 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
  8. Nick M


    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
  9. Nick M

    Reality XP Tech support-Moving forward

    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
  10. 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.
  11. 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
  12. Nick M

    rxpGNS2-FSIM(2.3.5) - crash ?

    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
  13. Nick M

    Flight1 vs RXP GNS ?

    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
  14. Nick M

    Flight1 vs RXP GNS ?

    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
  15. 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