jellisampvo

Hi Jean-Luc, So I tried running a flight that lasts about 1 hour from TFFM (Marie Galante in Guadeloupe) to TUPW (Virgin Gorda in British Virgin Is.). Just as happens every time, the Sim crashed about 20 miles out during the descent to the airport. I have screen shots I would love to attach but I am not sure how to do that. I am including the rxpGtnSim.dll.log file for you to look at. I have the sim configured as GTN_750_1. 21/04/25 19:12:08.002 03008 - ] # rxpGtnSim32.dll version 2.5.28.0 21/04/25 19:12:08.001 03008 INFO ] 21/04/25 19:12:09.698 11952 INFO ] GTN 750.1 - TRAINER 6624 21/04/25 19:12:09.698 11952 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\Bin 21/04/25 19:12:09.699 11952 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\data 21/04/25 19:12:09.699 11952 INFO ] C:\ProgramData\Garmin\Trainers\Databases 21/04/25 19:12:09.700 11952 INFO ] C:\ProgramData\Garmin\Trainers\GTN\nonvol 21/04/25 19:12:09.706 11952 WARN ] GTN 750.1 process is running as-admin 21/04/25 19:12:09.990 11952 INFO ] using: %LOCAL_APPDATA%\CrashRpt\UnsentCrashReports\GTN Trainer_6.62.4.0RXP 21/04/25 19:12:13.472 11952 INFO ] GFX Debug: enabled. I received the same error as before: Faulting application name: GTN Simulator.exe, version: 6.62.4.0, time stamp: 0x5ecfde0d Faulting module name: ntdll.dll, version: 10.0.19041.928, time stamp: 0xa0caab76 Exception code: 0xc0000374 Fault offset: 0x000e6a73 Faulting process id: 0xe94 Faulting application start time: 0x01d73a06e3d07902 Faulting application path: C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\Bin\GTN Simulator.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 8487fb31-dd77-4930-a4ca-e795341fa4e9 Faulting package full name: Faulting package-relative application ID: Thanks again for all your help. Jeff

Hi Jean-Luc, Thanks for all the info. I appreciate you taking the time to look into this. I do not run any type of debugger or logger in the background. Never really wanted to bother with that. As to adding the debug settings, I will do that and then try a flight longer than 30 minutes and see what happens. When I get a CTD, I will post the log file as requested. Finally, I only run the GTN 750, and only as GTN_750_1. I currently have if built into the panel instead of using it as a pop-up. Again, Thanks for all your efforts. Jeff

Hi Jean-Luc, Thanks for the information and sorry for the delayed response. I have been out of town on business. To answer your question about a debugger, I do not normally. Do you have any suggestions on a specific debugger to use or something you would like me to run in the background while conducting a flight? Please let me know what the next steps I should take are. Thanks again for all you efforts. Jeff

Well Bert, the short answer is that I have about 200 airports that I personally have fixed or added to FS9 along with a ton of addons. However, before I purchased the RXP GTN, I made sure it was compatible with FS9 SP1. Further, FS9 is a very stable platform and has been for years. I realize the graphics aren't great, but since I only use this for actual flight training, and not as a game, the graphics are not that important. Also, even though RXP claimed that certain features would work in the GTN and they do not in FS9 I am not addressing that issue. My only concern is that the GTN causes crashes, which it should not. I have spoken directly with Garmin about the issue, and since their simulation product works fine on my system (See above) and with the Windows 10 Pro (Version 20H2) installed, they are quite certain that it has to be a programming issue. As I said in my first post.....I have all the other RXP addons for FS9 and they work just fine. Thanks again for everyone's input. I hope a resolution can be found for this just like the issue of the Visual Slope not working correctly in FS9 was fixed. Jeff

Just as a further follow-up. This problem has existed even after several fresh installs of Windows 10 Pro, 4 GPU replacements, and 3 HD replacements in an effort to fix this issue. Also, I have tried running the GTN as both part of the aircraft panel and as a pop-up and this has no effect on the issue. In addition, once this error happens, FS9 freezes completely as does the computer, and the only way to get out of FS9 is to bring up the task manager and shut down the computer. It will not even let me just close FS9. Finally, If I remove the RXP GTN from the equation, then everything runs perfectly. I have all of the old RXP products, and they all still work with my system, as does the updated GNS 530W. But I purchased the GTN simulation because I use it the real aircraft that I fly and like the integration when it works. Thanks again, Jeff

I consistently get this error when attempting any flight lasting more that 30 minutes. It happens all the time and at first I thought it was a GPU issue. However, after a lot of searching and testing, I have come to the conclusion that there is some sort of coding error in the RXP GTN simulator as it relates to FS9 and Windows 10. My system build is as follows: CPU: AMD 3960X 24 core processor GPU: AMD Radeon VII RAM: 128GB HD: Samsung 1tb NVMI PRO drive Audio: Creative Labs AE-9 Sound Card Here is the Error: Faulting application name: GTN Simulator.exe, version: 6.62.4.0, time stamp: 0x5ecfde0d Faulting module name: ntdll.dll, version: 10.0.19041.844, time stamp: 0xa9ac4e88 Exception code: 0xc0000374 Fault offset: 0x000e6a73 Faulting process id: 0x17a0 Faulting application start time: 0x01d73233f8e627df Faulting application path: C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\Bin\GTN Simulator.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: e9b4be8a-e1bd-4b1f-97fe-cf47a24de9c7 Faulting package full name: Faulting package-relative application ID: I want to restate that I have already tried everything mentioned in this forum and everywhere else on the web. Please let me know what else I might try. Thanks in advance for all the help

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

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

Hi Jean-Juc, I have now tried that last thing you requested, which was a fresh install of FS9, insuring that NO other 3rd Party Modules were installed. Even disconnected All Flight Controllers. As I had suspected, the results are exactly the same. The Gear Warning is still erroneous and the TAWS does not function correctly in either mode. As I stated before, I still do not understand how my downloaded gauge can look differently from the ones on the You tube videos for the FS9 Sim or the Garmin Trainer, and still be functioning correctly. I realize you seem to want to ignore the possibility that there is something corrupted in the FS9 download version, but I am quite sure after all the research that I have performed, that this has to be the case. As I stated in several previous posts, My Unit - The One on My Computer does not even have a Checklist Button anywhere, and since the Visual Approach System, the Auto Config Detection System, and the TAWS System Do Not Function Correctly, a person with average computer knowledge can only presume that there is something either corrupted in the downloader, or there are several bugs in the coding in the FS9 version of the Gauge. I realize that you are busy, with as you put it in your previous post, more important issues. Also, I realize from your previous posts and the ones of Les O'Rilley, that since it is only 35 bucks, I should just go away. However, I am quite sure that I am not the only person who is having these issues, and I did verify before I purchased this item, that it worked in FS9. Perhaps, we can give this the attention it deserves and try to fix this for the betterment of all the users of this gauge in FS9. Thanks again for all your efforts. Jeff

Hi Jean-Luc, I tried changing the values in Item Number 2. This had no effect on the Erroneous Gear Warning. It still happens at about 500' AGL even though the flaps are full down and the gear shows 3 down and locked. Also, I tried as you suggested for the TAWS and renamed the previous novol file and then Re-started FS9. Sadly, this had no effect either. I await your further ideas to attempt to correct the issues. Thanks, Jeff

Hi Jean-Luc, Thanks again for your help. As to Item Number 1, there is not another Flaps setting area in the Aircraft Config File. As to Item Number 2, I will try changing the last values to 160, and 200 , 200 and see if that makes a difference. As for the TAWS, I will give that a try and report back. Again, thanks for all your help. Jeff

Hi Jean-Luc, Just checking to see if you were able to look at the files posted above? I have checked them against other FS9 stock retractable gear aircraft and do not see anything out of place. Please let me know what you find. Also, please notice I tried all your previous suggestions and posted the results above. Thanks, Jeff

Hi Jean-Luc, I have now also tried what you suggested in Number 2 of your post. This has had no effect in the RXP GTN 750 unit. As I previously stated in all my posts, the Garmin Trainer Unit is working perfectly in All TAWS Modes and in all Aircraft Modes Available. Thanks again for all your help. Jeff

Hi Jean-Luc, Thanks for the efforts. I will address the items in order. As to Number 1, here is the aircraft file: [flaps.0] type = 1 // 1 - tail, 2 - lead span-outboard = 0.5 // 0.0 .. 1.0 extending-time = 5 // seconds flaps-position.0 = 0 // degrees flaps-position.1 = 20 // degrees flaps-position.2 = 40 // degrees damaging-speed = 180 // KIAS blowout-speed = 250 // KIAS [contact_points] point.0=1, 13.00, 0.00, -4.0, 1181, 0, 0.596, 39.9, 0.296, 2.5, 0.9516, 4.8, 4.8, 0, 0.0, 0.0 point.1=1, -1.67, -8.58, -4.7, 1574, 1, 0.596, 0.0, 0.642, 2.5, 0.8152, 4.5, 5.2, 2, 0.0, 0.0 point.2=1, -1.67, 8.58, -4.7, 1574, 2, 0.596, 0.0, 0.642, 2.5, 0.8152, 4.8, 4.9, 3, 0.0, 0.0 point.3=2, -3.33, -23.92, -3.00, 787, 0, 0.000, 0.0, 0.000, 0.0, 0.0000, 0.0, 0.0, 5, 0.0, 0.0 point.4=2, -3.33, 23.92, -3.00, 787, 0, 0.000, 0.0, 0.000, 0.0, 0.0000, 0.0, 0.0, 6, 0.0, 0.0 point.5=2, -22.67, 0.00, 0.00, 787, 0, 0.000, 0.0, 0.000, 0.0, 0.0000, 0.0, 0.0, 9, 0.0, 0.0 point.6=2, 23.08, 0.00, -1.50, 787, 0, 0.000, 0.0, 0.000, 0.0, 0.0000, 0.0, 0.0, 4, 0.0, 0.0 As to Number 2 listed above, I will give that a try shortly and let you know the outcome. As to Number 3 listed above, I tried that before starting this thread and encountered the same results. By the same results, I mean that neither the TAWS A worked or the Visual Approaches worked correctly. Just a reminder, that the Garmin Trainer in the TAWS A mode, and the RXP Sandel 3400TAWS unit when installed in this aircraft, both work just fine. Thanks again for all your efforts, Jeff

Hi Jean-luc, Thanks for all your help. I gave you the .ini file from the aircraft folder in FS9. I just wanted to be sure you didn't need the one in the RXP Folder in the ProgramData section of the C: Drive. So as to the TAWS issues, The aircraft I am flying is a Turbine Royal Duke which is a Twin Turbine powered aircraft that is Pressurized and has Retractable Gear. I changed the values of the flaps and gear because the auto detect does not match real life or the aircraft config file and .air files of the aircraft in FS9. I also fly the real version of the plane and have a real GTN 750 in the plane with TAWS A active. In the real plane and in the FS9 aircraft config files the values I inputted are the same as what you see in the RXP GTN 750 ini file. The "Too Low Gear" warning happens even though the gear is extended once I get to 500' agl. Also, it happens at every airport. (Can't be an error in FS9 since I have used the RXP Sandel 3400TAWS gauge in this same aircraft with No Issues.) Additionally, I only asked about the checklists again since My Downloaded Version of your RXP GTN 750 does NOT even show a checklist button, so I wondered if there was something corrupted in My files. (The Garmin Trainer Database and System work fine in the TAWS A Mode.) The Visual Approach mode steps I follow, are: Go to Procedures Button Click on Approach Button Find "Visual to RWY" required Click on that RWY Number Button Then Click on Select and Activate the Approach Button According to everything I have read in the manuals and observed in the training videos online for the RXP GTN 750 unit, this is the only way to ensure that it actually loads the approach correctly for the autopilot to fly it. Also, I am using the Garmin Data Base that was included in the download, and with the Shadin Airdata enabled, I do get the correct GSL values at the airport of choice. These values also crosscheck with the Garmin Training Unit values at the same airport with the same Baro reading. So in both cases (TAWS and Visual), I am at a loss as to what would allow the Garmin Trainer Unit to work correctly, but the RXP GTN 750 to have these errors. I look forward to the next trouble shooting steps you suggest. Thanks again for all your efforts, Jeff