Wes Yin

Hi nigelmcelwee, The installation is basically first backing up your existing files and then copying/overwriting them as the new files. crazedpilot gave a great outline, above. I successfully updated the nav data for Garmin Trainer 6.41.1. It won't go wrong for you.

I confirm checking the box Use Simulator AI Traffic Count solves the problem. It is worth noting that this option applies to each aircraft separately. Thank you. I fly on PilotEdge, which injects AI traffic. I hope they will still be shown on the GTN. I haven't had time testing it though.

I am running the latest version of RXP GTN 750 with Garmin Trainer 6.41.1. In the Map mode, at my current location is always a diamond with 00, as if the GTN recognizes myself as a traffic. This occurs regardless of the aircraft in use as long as it is in the air. There is no TAWS warning. Another minor issue is that AutoPilot Nav often has a 20-200 feet offset to the left of the GPS route, i.e., flying parallel to the GPS route, even several minutes after AP Nav has been flying on the current leg. This problem could be specific to the aircraft though. It is more apparent on Carenado's PC-12 than JustFlight's Arrow III. Link to the screenshot: https://ibb.co/cPkMY7

I understand, and I can see from an expert FSX developer's point of view, those versions of FSX are clearly different. Several months ago, I, however, had put my FSX aside for four years and was in the process of reinstalling the software to revitalize my flight sim skills. I had bought RXP GNS 430, Flight Line N, and Flight Line T back in 2012, so when I saw they support FSX, I wanted to install them with the latest edition of FSX at that time. While I was aware of some different versions of FSX, I did not know that those RXP products were incompatible with FSX:SE until reading fscats' post. The phrase "FSX Acceleration Only" on the product page, while technically accurate, does not clearly say what RXP does not support. After all, several of my other purchases in 2011-12 for FSX continued to support FSX:SE, and some of them did not explicitly say. Also, web pages may be outdated. This is just a fact, not that I mention it to argue against RXP's decision. So, indeed, I was careful enough to research to find fscats' post above, which saved me money and, more importantly, time. I ended up went straightforward to P3D. I was only slightly disappointed and I hoped to find some coupon or discount that I could use to upgrade my legacy RXP GNS to the GNS or GTN for P3D. Maybe they had only existed for some time and were already over. I didn't find any so, at that point, I became disappointed. I thought I just tell you what I really felt as a previous customer.

Thanks a lot.

I apologize if this has been suggested or is already in the road map. Suppose a key (say "Joystick Button 1") is assigned to three camera presets: A, B, C. Pressing Joystick Button 1 will cycle through them, which has been a very nice feature. When I manually adjust the camera out of a preset, say B, I hope pressing Joystick Button 1 again can restore the preset B rather than immediately moving on to C. This would be useful, for example, using the joystick hat switch to check out the runway position during a circuit and returning to my favorite pilot view. Currently, after checking the runway, I have to press Joystick Button 1 a few times to cycle back to the last preset I would like to restore. So, in short, I hope a shortcut key or button will work like: restore, then cycle.

One possibility is your system setting on Languages and Unicode. It is worth trying setting the Unicode field to English. Anyway, I hope it will be solved, or I will have the same issue, too, as I plan to re-install the same thing.

I echo. RXP should warn the potential buyer of its incompatibility with FSX SE. You saved me $$. Thank you.

When I clicked on "Enable", the initialization ended up with fatal errors with all aircrafts and flight plans. It turned out that P3D v3.4 creates flight plan files (.pln) in which the degree, minute, second characters are affected by your system Region setting. This is normal, but VoxATC sticks with the most basic format. I live in the US. Going to Control Panel --> Region and resetting everything corrected the problem.

Thanks, John. The screenshots are very beautiful. I am studying this forum and inclined to buy OpusFSX very soon.