Ok let me recap:

1) the RXP GTN User's Manual describes 2 settings you may manually add to the ini file for "troubleshooting" purposes.

2) did you manually add any of these in the ini file already?

3) If so, then just remove them and compare how it goes.

4) if not, then you might want to add the following in the [GTN_750_1] section (if this is the GTN you are using in this aircraft), in the RealityXP.GTN.ini file located in this aircraft folder:

[GTN_750_1]
...
LogTrainer = 5
DebugValue = 1

On 12/19/2019 at 8:52 PM, RXP said:

Ok let me recap:

1) the RXP GTN User's Manual describes 2 settings you may manually add to the ini file for "troubleshooting" purposes.

2) did you manually add any of these in the ini file already?

3) If so, then just remove them and compare how it goes.

4) if not, then you might want to add the following in the [GTN_750_1] section (if this is the GTN you are using in this aircraft), in the RealityXP.GTN.ini file located in this aircraft folder:

[GTN_750_1]
...
LogTrainer = 5
DebugValue = 1

So I tried just about everything with no luck. Sorry again for the long reply back but I had another business trip plus the holidays. But anyways after another crash I decided to compare with the f1 GTN. It came in a bundle and I picked up the 750 and 650 and put it in my Lear. So far no crashes. I did notice that the screen for the f1 product is a lot smoother when moving between pages and scrolling. My RXP GTN wasn’t lagging but it wasn’t that smooth either. At any rate for some reason my computer just could not run the RXP product. It all points to a memory issue but my 2070 has 8gb of RAM and I have 32gb of hard RAM in my computer. While running P3Dv4.5. I thought I would never see another memory crash after switching to P3D lol. 

Edited December 29, 20196 yr by RXP

Hi,

We're preparing an update which may further help resolve the issue you're having.

In the meantime, you might want to try this:

1) Remove all LogTrainer and DebugValue lines

2) Add the following in the [GTN_750_1] section* :

CpuAffinity = -2

 

This is undocumented setting making the GTN trainer using all your CPU cores instead of a single one. This is not necessary at all, but it will be smoother and might cure the issue you are reporting, at the expense of all your cores dedicating a little bit of their time to the GTN instead of the simulator.

 

* Or any other GTN_###_#] section corresponding to the GTN you are flying with