Hi Jeff,

Several years ago I had trouble with two different GA aircraft models from the same developer.  With one model, in exterior views, a strange light square was attached to the top of the cockpit and only visible when looking at the aircraft from the left rear quadrant.  It was even there on the simulator free flight screen as the model revolved when the aircraft was selected.

The other model had another strange behavior with lighting.  If I flew west away from a setting sun behind me, the cockpit gradually became immersed in brighter and brighter light until the panel was totally washed out.  At that time the entire scenery ahead of me began to be flooded with light and grew brighter and brighter until it was totally washed out as well.  Strange to say the least and it only occurred with that model, and the effects were 100% repeatable.

I chased the developer and his staff for nearly 6 months for a fix for each issue, growing angry when I found a previous thread from one other single user who had an identical issue, but only with one of the two models.  Tens of other users reported no such issues.  I finally learned that with the model that had an issue flying away from a setting sun, that if I slowed to below V^LE, lowered the gear, turned on the landing lights, then retracted the gear, the issue resolved and did not come back during that flight.  On a number of different systems the developer’s staff was unable to repeat what I experienced. I found I had to respect that.

About this same time of the year in 2015 I built a new system.  I installed both models among a number of others I brought forward.  With the new system the issues with the two respective aircraft never occurred.  Not once.

Sometimes it is just not the developer’s product.

I took some time to write this because I have the upmost confidence in RXP and it’s products.  If you are aware of other users experiencing your same issue please bring them forward.  This is a sensitive time for RXP and I personally would like to see its available time moving forward rather than chasing ghosts.  That is not meant to be harsh.  Just real. Resources such as time are badly needed. I believe the number of FS9 users out there has diminished to a bare minimum.  Most developers have long since ceased support for that version of the simulator.

Edited August 29, 20205 yr by fppilot

Hi Frank,

First let me restate for the record, that I have all of the RXP legacy products, they all still work, and I am very pleased with their performance. 

Also, please understand that before I posted anything here other than a pre-purchase question, I exhausted every possible research source to try and ascertain if I was attempting to use the product incorrectly, or if I had some setting wrong in FS9, the RXP GTN Unit, or the Garmin trainer.  After watching about 30 hours worth of video, and spending over 100 hours trying different aircraft, airports, and settings, (including a Fresh Install of FS9) I posted here trying to see what might be the issue.  As you can see from the previous posts, the RXP GTN unit is not reading the aircraft config settings correctly.  This is the first clue I have that something is wrong or corrupted in the coding.  Secondly, as I stated in my last post, I do not even have all the buttons,(Greyed Out or Not), that are supposed to be in the RXP unit.  The Garmin Trainer works great, and all the functionality including Visual Approaches,  both TAWS settings, and the Checklists perform as expected.  I have tried everything Jean-Luc asked, and I am quite sure after seeing no results to the suggestions he is completely baffled by what is going on.  For the record, I do electronics technical work, and as I posted previously, am also a pilot IRL using a real GTN 750/650 linked to the G600 EADI/EHSI with SVT.  In my work in electronics, I often run into issues that do not solve easily.  However, regardless of the age of the unit, I always do my best to solve the issues for the customer and work to find the best possible solution in every situation.(Even when there is the chance that it means I do not get paid or lose money)  I believe that every problem is solvable and that from finding that solution, you gain knowledge that you otherwise would not have, and that knowledge can be applied to other projects in the future.

To your point about FS9.  I use FS9 because when I had to replace my system due to Motherboard Issues, my new system would not load FSX Accelerator.  I have all the versions of FS since the original one, and have all the original packaging and discs associated.  Also, the new system will not run XP.  On my old system, I had a dedicated SSD that had XP professional on it and that was what I used for FS9 and FSX.  Everything worked great there.  Obviously I did not have the GTN unit then.  When I could not get FSX to load on my system, I tried with some modicum of success to load FS9.(Had to use the hard coded license key instead of the disc 4 option)  I also know others, both for personal use and for Business Flight Training use, that still use FS9 either due to Frame Rates being better, or the fact they have paid for so many add-ons and hardware that do not transfer to FSX.  In the current state of my system, FS9 runs fine and all the Legacy RXP products work in either the stock FS9 aircraft or the add-on aircraft that I have.(Some Payware and some Freeware)  In addition, the payware planes and other items also work fine.  

My current system is an AMD Gaming MB with the AMD 2950X 16 core Processor, 128GB DDR4 Ram, Radeon VII 16GB GPU, EVO 960pro 2TB SSD, 17TB of Storage, and Duel ViewSonic 27" gaming monitors.  On this system I have all the latest updates installed, so I would highly doubt that the system is causing the issue.  I simply list my system specs so you know I am not trying to run things on a slow or antiquated system.

I would welcome any suggestions that you might have regarding how to fix the issues with the RXP GTN 750, and thank you for your input and perspective.

Thanks again,

Jeff  

Edited August 29, 20205 yr by jellisampvo
error in specs

Hi,

First, please, don't presume lack of immediate answer is lack of interest. Please do count the number of messages in the RXP forum, then count the number of messages I've written on Avsim, compute the percentage and you'll certainly see I'm not dismissing any support request.

Having said this, when you eliminate the obvious one by one, the remaining cause is harder to find and takes more time and this is normal and expected.

However I'd just like to make sure we're talking about the same things:

1) The GTN trainer standalone is a showroom of static features (re: the icons which "are supposed to"). Some of the icons are disabled in our implementation and this is both normal and expected like I've explained before. No need to talk about the icons again it just add noise to the discussion.

2) (this is just my personal opinion) With the system you're running I'm still not sure about the idea you can't run any modern simulator better, or at least with more than average performance (much more). I could run FSX-SE on an old iMac 2013 Intel i5 with NVidia 575M 2GB in bootcamp at 110 FPS+

3) Reinstalling FS9 for testing was not about solving the TAWS, it was about cross-checking the Visual Approach leading to 500ft error. Is this working better now?

4) The TAWS auto-detection system like I've explained is only auto-detecting what is in your aircraft config files. If these are wrong, so is auto-detection and this is not a product flaw. Hopefully you can manually set the values you want which you did and there is no problem to solve anymore about this.

5) The TAWS not detecting gear down is a first. It is really just a simple and stupid piece of code just reading the "GEAR LEVEL DOWN" simvar (or equivalent) and just setting a flag to 1 or 0 accordingly. There could be a bug in our TAWS interfacing code which is not conveying this value correctly but if this were the case, the forum would have much more reports about this. At this stage I'm out of any suggestions but I'm looking around for probable causes.

Hi Jean-Luc,

As to Number 1.  The GTN Trainer is an interactive unit that allows a person to actually complete flights in a simulated environment to train on the features and systems inside the unit.  I do not care that you have some features grayed out, however, as I have stated several times, the Checklist Button ( It seem to be on the other users of your system) is not in my unit.  I realize you think this is not relevant to the TAWS or Visual Approach issues, but once one eliminates the obvious, no matter how unlikely something is, it must be a part of the issue.  I have only ever mentioned it because I seem to be the only one without the button.(Functioning or Not)  Also, when I mention the Trainer, it is only because your product needs the Trainer to be functioning properly in order for it to work correctly.

As to Number 2.  FSX Accelerator will not load on my system.  As I have stated before, I have the original discs and codes, but Windows 10 Professional throws out error codes every time I try to install FSX.  That is the main reason I personally use FS9.  However, as I also stated before, I have several friends who use FS9 as the graphics engine for their Flight Ground School Training devices.

As to Number 3.  The Visual Approach was unaffected by the reinstall.  To restate, after the reinstall, I made sure that no 3rd party software or hardware was installed or interfacing with FS9.  Even using just the default keyboard functions to fly the stock aircraft - tried 4 different ones - the results were exactly the same at any airport.

As to Number 4.  The Auto Detect is not actually reading correctly.  If you look again at the Aircraft Config File that I attached to this thread, you will see that the values detected DO NOT match the values in the file.  I realize it is simple coding, but if you check, it did not read what was there.  This again is why I keep saying that I wonder if the Downloader for FS9 is not somehow corrupted or that is does something in the file that causes some type of error.

As to Number 5.  Is the "GEAR LEVEL DOWN" value something I can change in the GTN CONFIG, or is it internal coding?  I do not see that line in the GTN CONFIG.

Thanks again for you efforts.

Jeff

We've released a new update today which is among other things solving the issue with the Gear Handle sensor with FS9 (there was a specific problem only with FS9 indeed and this was triggering under a situation we couldn't repro at first):

As for the Visual Approach issue you're having we can't repro at all: in all our tests and with FS9 specifically, it is always landing the aircraft where it is expected. I'm honestly not sure what is specifically triggering this on your system at this stage but I'll keep looking for probable causes and I will definitely address the issue if we can only find out what is the source of this.

As for the checklist this will have to wait a little longer. We have too much on our plate right now to allocate any time further investigating this specific item which I understand is paramount for you in enjoying the use of our product, and which will be addressed if it is failing, but in the overall GTN as-a-navigation-device scope of things it remains a convenient feature only which is not immediately impairing the full use of the product for its main purpose.