Note: Navigraph was updated before the flight.
It’s always “fun” to be asked to enter a code in the middle of a VR flight, even though you’ve already been working in Navigraph outside of VR.
After entering the code, I was assured: “Navigraph Account Linked (FlightFX VisionJet was successfully linked with your Navigraph account.)”
However, when I then tried to call up a map on the avionics, a new code was displayed that I had to enter.
When I got fed up with this and tried to open the ingame Navigraph to continue, the sim crashed.
No, that happens from time to time.
Possibly after Navigraph updates?
What is annoying is that a code is requested ingame, even though you are already logged in outside and have worked with Navigraph.
If you are also traveling in VR, this is doubly annoying.
Please stop asking for a code ingame when you are already logged out or create a way to register in VR without having to take off the VR goggles.
We have not updated that plugin in over a year. Additionally, you are using a version that comes bundled with the VisionJet, which means we can’t update it even if we wanted to - FlightFX would need to push the update!
If an update to the panel (which is updated every time that the Charts app is updated) starts crashing the simulator, we would, of course, want to know about it! If you keep experiencing crashes, please try to figure out if there are any patterns. When does it happen? Are you interacting with something specific? Are you using DX11 or DX12?
No joke, the last crashing issue we had only occurred in DX12 and was caused by a shadow in a specific area of our interface. Somehow, that shadow tripped up DX12 enough to cause a crash!
The panel inside of the simulator has no way of knowing about your credentials or other ongoing sessions you have with Navigraph - that would have been a huge security issue. That said, you should only have to sign in once - but due to bugs in the simulator itself that are out of our control, this is not always the case for some people!
Most times, other users have got this issue when they move the packages folder to somewhere non-standard, such as another drive. That is not a definite culprit though - we have many cases where that is working as intended too This issue has been quite elusive to say the least.
Do you have the same issues with multiple sign-in requests in other aircraft with our official plugins? Such as the TBM 930 or Longitude with the G5000/G3000 plugin from Navigraph Hub.
We’d love to be able to do this, but the limitations lie in the platform itself (the simulator) and there is seemingly nothing that we can do in this scenario. However, it would still be interesting to hear if our official plugin works better for you!
Honestly, I don’t understand what makes you think that the in-game Navigraph is bundled with the airplane.
I installed the airplane long before I rented Navigraph.
So from my point of view, the ingame plugin comes from Navigraph itself.
Or how do you think you can tell that it is a plugin from the aircraft manufacturer?
Why should the aircraft manufacturer have an interest in requesting a code before I can use Navigraph in the avionics?
By the way, I use DX12 because I can’t use DLSS with DX11.
I’m sorry, it seems that I did not come across clearly enough! Let me try to elaborate.
Navigraph has developed a suite of avionics plugins. These currently cover the G1000, G3000, G5000, and G3X. If you are running MSFS on a computer, you can install these plugins through the Navigraph Hub. They will apply to all default aircraft with matching avionics and to some third-party aircraft that have not explicitly opted out of these modifications!
Some third-party developers, such as FlightFX, also publish to the Xbox platform. Navigraph has yet to be approved for publishing on the marketplace, so we can not deliver our avionics plugins for this platform ourselves! Since FlightFX wants their products to have Navigraph support on all platforms - they receive a custom version of the plugin from us, which they then include with the aircraft for all users, regardless of whether they have a Navigraph subscription.
You can tell if this is the case by looking at the message you receive when signing in. As you mentioned here:
In this case, you see “FlightFX VisionJet was successfully linked”. If you were signing into one of our global plugins (distributed through the Navigraph Hub), you would instead see “Navigraph Avionics was successfully linked”.
What all this means is that if we release an updated version of the plugin, we also need to send an updated version to FlightFX, and they need to include the updated version in their aircraft!
I hope the above explanation has helped to clarify my original statement! Now, back to the question: Do you have this issue with our integrations for any other aircraft, or is this only affecting the Vision Jet? This is vital information in order to determine the cause.
I had started the sim earlier this day with an empty community folder. The Cirrus SF50 VisionJet G2 was selectable, which means that it is a native component of the MSFS.
Furthermore, I have installed the avionics plugins you mentioned since I started renting Navigraph (about 2 years ago). See Screenshot.
With kind regards
Kurt
In this message, you can tell that you are using the FlightFX Vision Jet since it is explicitly mentioned.
So to circle back: Do you have this issue with our integrations for any other aircraft, or is this only affecting the Vision Jet? Since you have our plugins installed, you should be able to verify this by flying any of the G3X, G1000, G3000, or G5000-equipped aircraft that come with the simulator.
Fwiw, I’m having exactly the same issue both in 2020 and 2024. It started with the installation of SB dispatch in 2020. In that instance I was able stayed logged in for the Longitude but not for the link in the world menu. In 2024 I also have to continuously relog into the EFP app AND the Longitude. My 2024 community folder is in the default location.
This issue has been quite elusive to say the least.