Recommended Posts

Hello Again,

 

 I just purchased the BAE Jetstream 32. It has the GTN integrated into the panel. Sometimes when I load the aircraft I receive the license invalid error. It has happened four out of five load attempts. It worked on the second attempt, and has not worked since. I will attempt to add the screen shot of the message, and the instructions that came with the aircraft. 

 

I do have a valid license, and the GTN works fine in all other aircraft. 

 

Thank you,

Tommy

README File:(The RealityXP GTN 650 and 750 as you may know are installed outside each plane as general plugin for all the planes in xplane.
For that reason everytime you choose the GTNs you want to have inside of each plane it automatically creates a file called RealityXP.GTN.ini. 
if that file is not protected, every change in the RealityXP options in the plugins menu, will generate another ini file that will break the compatibility you achieve before. 
For that reason the RealityXP.GTN.ini is write protected and should be all the time, unless you want to modify any parameter of it. That is the way to do it and not via the menu in this plane. Then after you have saved new options you will need to write protect again the file.

For the Jetstream32 I have created options to show both GTNs but never at the same time.
You will be able to show each GTN via the new Yoke menu in the center of it. Each mouse click will change between the different configurations:

1. Default X-Plane 430 GPS + Weather Radar
2. RealityXP GTN650 + Weather Radar
3. RealityXP GTN750 only.

If you don't own any of the GTNs the screen will appear black, so better choose a GTN you own or put the default GPS.)

 

I could not get the screen shot to upload. Anyone have advice on that?

 

Share this post


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

Is this happening when you change GTN type using the BAE Jetstream 32 Yoke menu, or just when loading the aircraft?

I don't think the file being write protected would have any incidence, as I guess the developer has validated this form of integration before releasing, but the entire 'settings' system has not been designed to cope with read-only INI file specifically though.

Share this post


Link to post
Share on other sites
1 hour ago, RXP said:

 

Is this happening when you change GTN type using the BAE Jetstream 32 Yoke menu, or just when loading the aircraft?

 

Yes, it is when using the integrated GTN 750, (from the yoke menu). When the aircraft is loaded, the 430 is the default, in order to display the GTN, it needs to be selected on the yoke menu.

So, what I should do is change the Read/Write properties of the RealityXP.GTN.ini fie in the Bae Jetstream 32 folder, start the aircraft, setup the GTN, then reset the properties back to Read only?

Hope this info helps.

 

Thanks, 

Tommy

Share this post


Link to post
Share on other sites

Tommy, unless you are changing settings with the settings panel, and these settings are mandatory for this integration, there is no need to write-protect the INI file. For example, you should be able to change DB (americas/worldwide) without breaking the aircraft integration.

With this in mind, we've worked yesterday in adding a 'locked' parameter in the INI file which will permit 3rd party vendors to out-out settings from the settings panel, without requiring locking all the other settings in write-protecting the file.

We're planning releasing the official 2.4.6 update today which will include this new feature along other things, and we expect 3rd party vendors to catch up the changes from then.

Share this post


Link to post
Share on other sites

I

On 5/9/2017 at 6:47 AM, RXP said:

Tommy, unless you are changing settings with the settings panel, and these settings are mandatory for this integration, there is no need to write-protect the INI file. For example, you should be able to change DB (americas/worldwide) without breaking the aircraft integration.

With this in mind, we've worked yesterday in adding a 'locked' parameter in the INI file which will permit 3rd party vendors to out-out settings from the settings panel, without requiring locking all the other settings in write-protecting the file.

We're planning releasing the official 2.4.6 update today which will include this new feature along other things, and we expect 3rd party vendors to catch up the changes from then.

I'm not changing anything, just loading and starting the aircraft as instructed, when I choose the GTN 750 on the Yoke menu, the GTN screen gives me the license invalid message.

(This forum will not let me post a screenshot)

 

Tommy

Share this post


Link to post
Share on other sites

Tommy, I'm not saying you are doing something wrong, I was just answering to your question "then reset the properties back to Read only" while explaining why at the same time. Here it is again (swapped and highlighted sentence bits): 

there is no need to write-protect the INI file / unless you are changing settings with the settings panel, and these settings are mandatory for this integration,

Nevertheless, you might want to try out v2.4.6 just released and see if this helps:

In the meantime, we'll contact the vendor to let them know about the new INI setting we've added in v2.4.6 which renders read-only files unnecessary.

 

Share this post


Link to post
Share on other sites

Hi Jean-Luc,

 I hope I didn't come across demeaning, I did not mean to.

 

I just updated to v2.4.6 and still am receiving the same invalid license message on the GTN. Please note, that I am using the GTN supplied by the aircraft, not the plugin GTN. if that makes sense?

 

Thanks for all of your help,

Tommy

Share this post


Link to post
Share on other sites
9 hours ago, Piper5299X said:

and still am receiving the same invalid license message on the GTN.

I'm yet to know what they are exactly doing with the GTN, but it looks like it has side effects, because like you've mentioned, it works fine otherwise. We're in contact with the vendor so we'll help them out.

Share this post


Link to post
Share on other sites
On 5/12/2017 at 4:30 AM, RXP said:

I'm yet to know what they are exactly doing with the GTN, but it looks like it has side effects, because like you've mentioned, it works fine otherwise. We're in contact with the vendor so we'll help them out.

I found a work-around. X-Plane must be restarted, and select the JS32 before any other AC. No more invalid license message.

One drawback, the Direct-To button no longer works. Must select the Show Window from the Plugins dropdown for GTN2 in order to be able to use the Direct-to. 

One more thing I just found out...If you pause, or go to replay mode, the invalid message returns.

Thanks again,

Tommy

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