ark

Strange GTN750 Configuration Panel Problem (resolved)

Recommended Posts

Posted (edited)

In P3Dv4.4, I see the following:

1. I load the default Baron58, open the GTN750 popup, and then open the GTN Configuration Panel, make a change, save the panel, close the GTN750.

2. Select a new a/c like the Carenado Commander 114, open the GTN750, then open the Configuration Panel, but the panel is still labeled as the Baron58 panel, and if I make a change it is in fact the Baron50 GTN ini file that gets changed.

If after restarting the sim I reverse the above sequence and start with the Carenado Commander 114 and then switch to the Baron 58, when I open the Baron's Configuration Panel what I get is the Commander 114's configuration panel, so the same type of problem.

Is anyone else seeing this or do I perhaps have a system problem of some type?

Thx,

Al

Edited by ark

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi,

I'll cross check this right now, I was about to release the next update... We've changed a number of things around the 'settings' for the update which might also fix this.

Share this post


Link to post
Share on other sites
10 minutes ago, RXP said:

Hi,

I'll cross check this right now, I was about to release the next update... We've changed a number of things around the 'settings' for the update which might also fix this.

OK, thanks very much for looking into it. It seems to be a general problem not related to particular aircraft, at least on my system.

Al

Share this post


Link to post
Share on other sites

Hi,

v2.5.14 is just released and we weren't able to repro. However the new update also solves a more general problem related to some settings not 'reset' when changing aircraft, which may be related to the issue you are reporting in the end.

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, RXP said:

Hi,

v2.5.14 is just released and we weren't able to repro. However the new update also solves a more general problem related to some settings not 'reset' when changing aircraft, which may be related to the issue you are reporting in the end.

Installed v2.5.14 but unfortunately still have the same problem. If I use the 2D configuration popup, then close it and immediately load a different plane (without restarting the sim), then when I open the 2D configuration popup for the new plane it is still the 'old' plane's configuration panel.

I don't see this problem in FSX, only P3D4.4.

If no one else is seeing this I assume it is some strange problem on my system.  I do appreciate you having looked into it.

Al

Edited by ark

Share this post


Link to post
Share on other sites

This is most peculiar. What is the hint on the panel which tells you it is other aircraft config being still edited?

Share this post


Link to post
Share on other sites
10 minutes ago, RXP said:

This is most peculiar. What is the hint on the panel which tells you it is other aircraft config being still edited?

At the top of the 2D configuration panel window it gives the path to the RXP ini file which includes the aircraft folder. And if I make a change, that is in fact the ini file that gets changed. I checked this in FSX and it worked correctly, so it seems to just be a P3Dv4.4 problem on my computer. It would seem something is not getting updated when changing the aircraft using the P3D drop down Vehicle\Select... menu option.

Al

Share this post


Link to post
Share on other sites

Which is weird: when changing aircraft, FltSim completely unloads all the gauges (they are DLL), then loads all the new gauges even though both panels are using the same gauges. In other words: once our GTN unloads it just unloads. When the GTN re-loads, it starts anew.

Are you talking actually about the Configuration Panel ( Device Options, Gauge Options etc..) or the Panel Assistant (Add/Remove GTN to the panel) ?

Share this post


Link to post
Share on other sites
Posted (edited)

After loading the Baron58 and opening and closing the 2D GTN configuration popup, and then selecting the AC11Commander114 using the P3D Vehicle Selection menu as described above, here is what I see when I try to open the AC11Commander114 2D configuration popup:

0db2dbf378.JPG

Click on the picture to enlarge it and note it says beech_baron_58 as part of the file path at the top of the configuration window.

Al

Edited by ark

Share this post


Link to post
Share on other sites
Posted (edited)

I also sometimes have problems which might be related to the one above.

I make a change with the 2D configuration popup, but it does not take effect. That is,  I make a change with the GTN configuration popup, close the 2D window (save the change) and then immediately reopen the 2D popup and find that the change did not take effect. If I then check the RealityXP.GTN.ini file I can see the change did not happen there either.

So if the 2D configuration popup reads the RealityXP.GTN.ini file each time when opened (popped up) I can see why it shows no change -- the ini file never got updated. So it seems that for some reason the ini file in the aircraft folder is not getting updated when the 2D popup is closed.

Also, I use a single GTN750 and often find that for some reason it is no longer listed as the Master Device in the GTN ini file (MasterDevice = false). If I try to edit the ini file directly (because the 2D configuration popup doesn't work) I find the change I made does not work (stick) unless I make the change when the subject aircraft is NOT loaded into the sim.

I wonder if when an aircraft is loaded into the sim if perhaps the sim loads and uses a working copy of the ini file rather then directly using and updating the ini file in the aircraft folder? So any text editor ini file changes do not take effect until the next time the aircraft is loaded into the sim? 

I'm reporting all this just in case something might be a clue to what is causing these problems. I'm using Reality XP version 2.5.14.

Al

 

 

Edited by ark

Share this post


Link to post
Share on other sites

Let's try to find out what is causing this.

Can you please review both panel.cfg files and make sure there isn't any other GTN gauge configured but not visible (whether a popup window left hidden/closed or a VC gauge set somewhere) which might account for the 'Master Device' setting reseting somehow? (although I fail to see why this would do this).

Can you also try the same but using just stock aircraft, B58 and Mooney for example?

Otherwise, the only reason this could happen is the gauge DLL isn't unloaded when changing aircraft on your system, and for some reasons, P3D4 would just be fine finding out the DLL is still loaded and it would just re-use the existing one (although I doubt it). Could it be the gauge DLL file (rxpGTN.dll) was added to the P4D4 DLL.xml file and gets loaded with the simulator instead of with the aircraft?

You can cross check whether it gets unloaded 'easily':

  1. Load a GTN aircraft
  2. Open the settings panel (just for the sake of reproducing)
  3. Close the panel and load a non-GTN aircraft
  4. Open Process Explorer (link below)
  5. Locate P3D4 process and select it in the list (not double clicking, just selecting)
  6. In Process Explorer menus select View Lower pane - Show DLLs
  7. See if there is any rxpGTN.dll still loaded in the process (there should be only rxpGTN_menu.dll which is the one behind the add-on menu and expected)

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

 

Share this post


Link to post
Share on other sites
6 hours ago, RXP said:

Let's try to find out what is causing this.

I loaded the Baron 58 and opened and closed the GTN 2D configuration window. I then used the P3D Vehicle select menu to load the Alabeo Extra which does not have any GPS at all. I then ran Process Explorer.  Since I'm not familiar with this program I thought it best to just show what I found below. If I used the program correctly, it does appear there is a rxpGTn.dll loaded. If I did something wrong just point me in the right direction and I will try again.

Al

15a235efda.JPG

Share this post


Link to post
Share on other sites
Posted (edited)

Indeed there is and it shouldn't, this might explain why it is behaving like you describe: when loading another aircraft, P3D4 will find the gauge already loaded in memory and use it.

The only reason I see this happening for now is your DLL.xml file is referencing the rxpGTN.dll gauge file, as-if it were a 'module' you'd load with the sim.

If you load the sim with the Alabeo Extra directly, is the DLL still showing?

If it does, this means it gets loaded with P3D4 automatically regardless of the aircraft panel.

If it doesn't this means there is something preventing the gauge DLL to unload with the aircraft and this is usually because of anti-virus keeping a lock on the files.

Edited by RXP

Share this post


Link to post
Share on other sites
Posted (edited)
50 minutes ago, RXP said:

Indeed there is and it shouldn't, this might explain why it is behaving like you describe: when loading another aircraft, P3D4 will find the gauge already loaded in memory and use it.

The only reason I see this happening for now is your DLL.xml file is referencing the rxpGTN.dll gauge file, as-if it were a 'module' you'd load with the sim.

If you load the sim with the Alabeo Extra directly, is the DLL still showing?

If it does, this means it gets loaded with P3D4 automatically regardless of the aircraft panel.

If it doesn't this means there is something preventing the gauge DLL to unload with the aircraft and this is usually because of anti-virus keeping a lock on the files.

If I load the Alabeo Extra directly after starting the sim, the rxpGTN.dll is not loaded according to Process Explorer.

Next I turned off Windows Defender (my only antivirus), restarted the sim and went through the same Beech Baron 58 - Mooney Bravo experiment as above, and unfortunately the problem still persists -- still had the wrong 2D GTN configuration popup when I switched planes.

Al

 

Edited by ark

Share this post


Link to post
Share on other sites
Posted (edited)

For today's date, App Crash only showed the following top two entries from a number of hours ago (click to enlarge the image).

8632cb4aa6.JPG

But I had just run the Baron58 - Mooney experiment again with the same 'wrong' results, and nothing with a reasonably current time stamp showed up in App Crash. And just to be sure, I repeated the experiment and again nothing new showed up in App Crash.

Although the first entry above was hours old, I looked at the data for this heap corruption and the only entry I could find with the rxpGTN.dll was this:

LoadedModule[247]=C:\Program Files (x86)\Reality XP\GTN Simulation\FltSim\64\rxpGTN.dll

Al

 

 

Edited by ark

Share this post


Link to post
Share on other sites

There seems to be a number of errors from your P3D4 itself as-is then. I'd start by going to the Manage Add-Ons menu and disable all but the RXP add-ons and compare how it goes, after rebooting the computer.

It might be there is another gauge or a module or a scenery causing troubles. StackHash errors are typically found in this case when an add-on 'hacks' into the application and fails somehow, 1st in my list would be FSUIPC.

Share this post


Link to post
Share on other sites
Posted (edited)

I tried removing the few addons I have, updated Orbx Global Base and libraries, reinstalled the P3Dv4 Client, uninstalled and reinstalled RXP GTN 750 --  nothing helped.  I can't think of anything else to try at this point.

Jean-Luc, I want to thank you very much for all the time and effort you have put into trying to fix this problem -- wonderful support! Fortunately it is one I can work around for now by restarting the sim if necessary when switching planes, or by directly editing the GTN ini file. If I ever happen to stumble on the bug in my system that is causing the problem,  I'll report back here in case someone else runs into a similar issue.

Al

Edited by ark

Share this post


Link to post
Share on other sites

I thank you for your kind words but I'd like to figure this one out as well, in case it is just a bug in our gauge failing to close. It shouldn't be the case otherwise I'm sure there would be more reports similar to yours but there could be an edge case which is failing though.

Besides removing a few add-ons, have you tried using the "Manage Add-Ons" menu and unchecking all add-ons but RXP to see how this works?

Share this post


Link to post
Share on other sites
4 hours ago, RXP said:

Besides removing a few add-ons, have you tried using the "Manage Add-Ons" menu and unchecking all add-ons but RXP to see how this works?

Yes, did this, the only add-ons listed besides RXP where Accu-Feel and Orbx.

I also went into the P3D DLL.XML file and disabled the FSUIPC and Active Sky dll files, and also made the Prepar3d.cfg file rebuild. Still have the same problem.

I also use the Rex-Milviz WX radar, although not with the Baron58 or Mooney, and also use TrackIR but have not used it during these trouble shooting tests.

Al

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

I am not sure when this problem first started, but do you think it would be worth trying an older version of the GTN750 -- say a year old version, just to see if it makes a difference with this problem? This would tell us if recent GTN changes do or do not make a difference.

Al

Edited by ark

Share this post


Link to post
Share on other sites
4 hours ago, ark said:

Yes, did this, the only add-ons listed besides RXP where Accu-Feel and Orbx. 

I also went into the P3D DLL.XML file and disabled the FSUIPC and Active Sky dll files, and also made the Prepar3d.cfg file rebuild. Still have the same problem.

Thank you for the additional details and your enduring patience!

When I mean all add-ons I really mean it, especially these like Accu-Feel, Orbx amd Active Sky which most likely 'hack' inside the FltSim process. The same with other add-ons like 'Reshade' or any other post-processing effect.

I'll PM you for the other part.

Share this post


Link to post
Share on other sites
Posted (edited)

Jean-Luc,

I think the problem has been fixed, at least for now. I redefined my default aircraft/flight using the F-35 and the problem went away.  It is very strange, but a number of simmers I've talked to have found using the F-35, instead of the F-22 or other default aircraft,  as the default (first loaded) aircraft/flight in P3Dv4.4 has fixed some very odd problems. If usually is sufficient to just load the F-35 in the spinning preview window before switching to the desired aircraft. If that fails, loading the F-35 onto a runway and then switching aircraft may work.

Many thanks again for your continued support that went well 'above and beyond'!

Al

Edited by ark

Share this post


Link to post
Share on other sites

Hi Al,

Thank you for the update on this and for sharing with others. I'm sure this will help others encountering the same situation in the future.

I'm also glad to find out it is not a defect in our product but more an annoyance with the specific simulator installation.

It won't tell us what is happening in your system, and if ever there is anything we can do in our product which could help preventing this from happening at all, which is quite frustrating a little in the end, but I'm glad you've been willing to pull the extra strength to help analyze if not why it is happening, at least what is happening, so that it gives a direction to help fixing this.

 

Share this post


Link to post
Share on other sites

I would like to better understand what was causing the problem in more detail, but the best I can come up with at this point is that loading the F-35 initializes the system variables in a way that prevents the problem. Guess that will have to do for now.

Al

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now