with the new ingame navigraph charts, when try to view simbrief ofp, the msfs simulator freezes completely, regardless of he selected airplane (standard Cessna 172 or FBW A320). I have to kill the simulator.
HW Win 11, RX3090, MSFS2020 1.36.2.0
Same here. It says in error maybe occurd because of DirectX version. I’m using Win11 with RTX 3080 and DirectX12.
Hello! Welcome to our forum!
@Schaepper , are you also using DX12?
And both of you, does the issue persist in DX11?
Kind Regards,
Malte
It also happens on my installation with 7900XTX latest drivers and DirectX 12. Did not test on DirectX 11
I have also this problem. I am using windows11, RTX3080 TI, DirectX12. I did not use DirectX11 yet. Newest drivers.
Hello everyone! Thank you for the reports.
Could you try in DX11? We would like to narrow this down as much as possible, and no one on the team is using DX12 due to the many issues reported with it.
Looking forward to your results!
Kind Regards,
Malte
Hallo Malte
Thanks for your reply. And yes, the issue does not happen when using DX11. I used the tandard C172 to test it. And it worked.
regards Ueli
Thanks for the confirmation! Then it seems like this is unfortunately too low-level for us to be able to debug the issue. Perhaps Asobo could help, but I am not sure they want to put resources into debugging issues that do not occur without a panel like ours triggering them…
At the same time, we are at a loss - they have the source code for the simulator and are the only ones who can meaningfully debug this. We could go on a chase and try removing/changing things piece by piece until the issue stops, but it is not a priority for us seeing as even the MSFS developers consider the DX12 option unstable, as far as I know.
I will write this down and add it to our backlog for investigation, but as mentioned it will likely have low priority unless this starts occurring for DX11 too. Sorry for the inconvenience!
Kind Regards,
Malte
So I can agree. With DX11 it doesn’t freeze, but with DX12 it does freeze. My next test will be to see if the non in game navigraph causes it to freeze.
@skysail
I cannot really agree with the solution of avoiding DX 12. I think the ingame navigraph app is part of your solution (and therefore in the community folder) and I assume, that your software is reading your simbrief ofp and tries to show it in your app. And therefore it is maybe not the issue of Asobo.
And even though DX12 is in Beta state doesn‘t mean, that users don‘t use it, since this is the only way to improve the fps. And these users are paying subsciption fees to Navagraph every year. So it would be a good idea that at least some of the developers would use DX12 to be prepared so DX12 will be out of Beta. And avoid issue like this.
Best regards
Ueli
3 Likes
Hi Ueli,
It seems the DX12 beta causes problems with viewing SimBrief OFP’s. We shall likely test DX12 ourselves, but we are saying supporting it for users is a low priority as the Beta already has many issues.
Cheers
Ian
Hello, I had the same problem on DirectX 12, and switching to DirectX 11 after starting a flight didn’t fix it, it just froze again. I had to switch to DirectX 11 before starting the flight to fix the problem.
If this is not easily fixable and/or not a priority, you might want to put a warning somewhere about DirectX 12, that you don’t support it yet and it may cause issues, for example when signing-in to Navigraph from the simulator.
I lost about 30 minutes so far troubleshooting this, as loading the simulator again after it freezes takes a lot of time, and I hit this issue 3 times so far. I was even concerned that my hardware might have issues again (my 13900K requires significant underclocking, around 10%, to be stable).
This is a simulator issue that could go away at any time with any update, and potentially even come back again after that. You are intentionally using unstable (experimental even) rendering APIs and the error message you get when the simulator crashes should tell you this and prompt you to try with DX11 instead.
Was this not the case for you? The last time I saw a screenshot of this issue, it clearly said that the problem was likely caused by DX12 being enabled.
If you have any suggestions as to where such a warning could be placed, we’re open to considering it! But again, this is not an issue in Navigraph software and it could be gone at any time - making the warning misleading instead.
Kind Regards,
Malte
No, I do not:
I am using an almost 10 year old API, not some experimental API.
The simulator doesn’t crash. As I mentioned, it freezes, and I have to terminate the process. So obviously it can’t tell me anything, since I ask the operating system to terminate it.
No, it was not the case for me. Even the title of this thread mentions freezing, not crashing. Nobody mentioned crashing here, except you. There are indeed mentions of crashing in the linked threads, but that’s not what this thread is about.
Yes, I had a suggestion:
Sorry, this is what I meant - it should be beta and not experimental!
It is an old API, but the integration into MSFS is in beta. These are technicals, but you’re right in stating that they are old! I should have been more clear on this. Still, it is not stable.
I am referencing this topic which was merged into this one: MSFS Crash opening Simbrief OFP
The symptoms are the same, I can reproduce both the freezing and the crashing on my own PC with DX12 enabled. Sometimes you get the message, but other times (especially if you are impatient and force the sim to close - done that many times and it seems like you do the same) the message does not appear. Both issues are fixed if you switch to DX11.
Ah! Thank you, I missed that note! The issue with this approach is that the simulator sometimes has a hard time remembering things. This means that we could end up in a scenario where the panel prompts users every time the simulator is restarted, which would probably be quite annoying and do more damage than good… Quite a tricky situation indeed!
We have tried fixing the storage issue many times, but nothing seems to be reliable - there’s always a small percentage of users that are affected. We can see that our values are stored before the simulator is quit, but then the values are gone on startup for some users, while others remain unaffected 
Kind Regards,
Malte
1 Like
@skysail
ok, ofp displays fine on ingame efb by pmdg and others using dx12. only an issue on navigraph ingame charts.
so either the data import is borked or rendering is messed up. has navigraph tried sending the ofp as an image file or tried working with others like pmdg to understand this issue, rather than blame dx12 as being beta? all other apps/addons working fine using dx12, just this navigraph bug is a nuisance.
july 2024 and it hasn’t been fixed yet, freezed my sim 2 hours into the flight.
Would’ve loved to know it was a problem, use the desktop app, otherwise you are compromised to DX11 which is terrible for fps.
Hello everyone!
Slowly but surely, the team is coming back from vacation. We spent some time investigating this and diving deeper today, and many crashes later, we believe we have finally found the issue!
The simulator does not like our shadow outline of the OFP when running in DirectX 12. It is still impossible for us to tell why this is, but after picking the panel apart piece by piece, we traced it down to a single line of styling! It’s a weird one, for sure.
We have issued a hotfix, which should already be available! If you are currently using the panel, you might need to restart the flight or simulator. The reported version on the settings page should be 8.35.1.
We are sorry for the inconvenience this issue has caused for those using DX12, and we look forward to your confirmation that it has indeed been fixed! Please let us know if you see any further issues.
Kind Regards,
Malte
1 Like
Thank you for fixing this!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.