I recall reading something in the WT Discord about similar freezes that has been fixed for the next update.
Anyway let me try that approach out.
1 Like
I read in the WT Discord that Custom Waypoints would be introduced with the upcoming next release.
1 Like
Thank you! I’m relieved to know this is not just happening to me. Your situation sounds more remediable than mine was. After awhile I couldn’t even get to the cockpit; the sim crashed when I clicked “Fly” on the World Map, or alternatively, when I clicked “Ready to Fly” if I got that far. I had to go through yet another uninstall/reinstall to fix the issue. I hope the Working Title folks will take heed of the comments here and fix this issue, and the G1000 NXi’s ILS approach issue.
That may explain why, when I was able to use the G1000 NXi, the ILS approach to RWY 10R at Monterey – which I’d flown many times – suddenly had a “hold” loop at the first intersection (ZEBED), where there was never one before. Now that I’m back to the plain-vanilla G1000, that’s gone away.
As per the charts there’s a hold at ZEBED. Depending on arrival it may be needed as a PT.
If you don’t need to fly it, it can always be skipped.
Yeah, something about a bug in certain situations when VNAV is active. The quick workaround is to set the the Alt preselector to 0.
1 Like
Ran into an issue today where I could not enter a xpdr code starting with a zero using the G1000 NXi. I uninstalled this mod and was able to do it using the stock g1000. ATC cancelled my IFR clearance after getting a little upset because I could only set to ‘425’ instead of ‘0425’.
1 Like
Just to update, I did the same UPOLO 8A arrival with the BE36 and didn’t have any freeze before or at SUNNY at 3,700. But it froze shortly after that when I pressed FPL to check the next constraint.
So yes, it’s reproducible.
Edit: As mentioned earlier it will be fixed in the next update.
Thanks yes I may have had FPL up at the time.
1 Like
I had a 0264 code and the internal ATC was seeing the full code even though I had 264 displayed on the G1000. It appears to be a display issue, not ignoring the leading zero when it reports to the internal ATC.
Per the charts, ILS 10R does have a hold in lieu of procedure turn at the initial fix. The fact that the other system does not display it is a limitation of the stock flight plan system. The NXi is displaying it correctly.
Just to give a thorough update on the NXi and CTDs,
Instruments that are coded in Javascript can only cause a crash due to an underlying bug in the simulator that is triggered when the instrument calls the API that has the bug. Instruments in Javascript cannot, however cause a crash on their own, no matter how bad the error is in the Javascript itself. This always makes us scratch our heads a bit when we encounter people with repeatable crashes, because it means only one of two things:
-
There’s a bug in the simulator triggered when we make a call into the sim, which is not good
-
There’s a totally unrelated bug that has nothing at all to do with the instrument at all, but people (understandably) believe it is the source of their issue without sufficient isolation testing
Oftentimes the situation is much more the latter than the former (and it’s awfully hard for a user to tell with so many moving parts), but in this case (as @dga711 mentioned previously in this thread) we’ve located a race condition in the sim during map initialization in the sim that is timing dependent. This is why it affects only some users. Additionally, this is also why it is affecting the NXi and not other instruments with maps, as the NXi loads faster than the stock instruments, making this timing tighter and making the race condition in the sim map system show its face.
We’ve identified a workaround we can use on the instrument end that seems to lessen or eliminate the issue. We won’t quite know for sure how helpful it will be until we get it out in the wild in the next release, but it seems to eliminate the CTD for the users that have tested it.
These issues are especially sticky for us as developers because they both feel like they should be theoretically impossible as well as being terrifically difficult to debug, as we aren’t able to reproduce it repeatably (or oftentimes at all).
That being said, we always do investigate these when a pattern this strong emerges from the noise.
-Matt | Working Title
10 Likes
As written previously I CTD when loading into the airport from the map screen.
If it helps, my specs: MB=MSI MAG Z490 TOMAHAWK, Intel 10700K, 64 GB 3200 RAM, RTX3070, Samsung SSD
Is it that some PCs are too slow or too fast, in other words, does it seem to affect lower end PCs rather than higher end?
It’s totally random. It’s going to be the sum total of your hardware, your particular hardware specific load times, and whether you hit this sim bug with map initialization in exactly the right window. For some people that happens to be nearly always, for some that happens to be never. I don’t know that there would be any way of determining whether a specific hardware combo is better or worse for it.
That being said, we feel like our workaround should alleviate it, but we’ll see as the feedback comes in with the next release.
-Matt | Working Title
1 Like
Very tricky. For me it is Always on subsequent flights. It sounds like a nightmare to identify.
Thanks
Got it. I tried to remove the hold from the flight plan before taking off for ILS 10R at Monterey – but I couldn’t remove it in the PROC menu. Is there some way to do that?
Just highlight the hold on the FPL page and hit the CLR button, and confirm you want to delete the leg. That should clear it.
-Matt | Working Title
1 Like
Please translate … And assuming this is causing CTDs in my sim if I use the G1000 NXi, at what point does it happen – after I’m in the cockpit or sooner? My biggest issue is being unable to even get to the cockpit. Worse than the sim crashing mid-flight, the sim has crashed when I tried to start a flight, either by clicking “Fly” or “Ready to fly.” It’s those kinds of crashes that drove me to yet another sim uninstall/reinstall. Since the last reinstall, and without the G1000 NXi on my PC, I haven’t had a CTD of any kind in two-plus hours of flight time over the past couple of days.
This is an issue within the sim that can happen when the sim initializes the moving map system, which happens both on flight load (starting the flight) and on flight unload (going back to the main menu).
-Matt | Working Title
1 Like
I used to get a freeze 100% of the time when arriving at the initial waypoint of the approach on an RNAV approach. I’m assuming this is the same issue? When might we be seeing the next release that is supposed to fix it?