9 minutes ago, Nyxx said:

I start to use it had one flight fine the 2nd the sim just froze, did not chrash, I had to "end tast" just froze. So will bin it till there is another build. Thanks for info.

I had a freeze once or twice but mostly CTDs. Glad WT is now aware of the issue and working on a fix.

Don't mistake the freeze issue, which happens under certain circumstances when calculating TOD during flight, with CTDs that people are reporting. Its a different thing and will be fixed with the next update coming very soon.

We have no clear indication of the NXI causing CTDs or why that would be. But we are of course investigating.

Also to set the record straight again

NXI: Is a new instrument built from the ground up with the goal of replicating the G1000 NXI, which is available on the marketplace as "early access" until it is polished enough to be in the core sim

WTG1000: Is the "old" mod of the stock  legacy G1000 we had for months and is no longer maintained. There is a 0.4.0 release for SU5 compatibility though, which is just the stock G1000 + engine pages.

You should never have both installed at the same time.

Edited August 8, 20214 yr by dga711

1 hour ago, dga711 said:

Don't mistake the freeze issue, which happens under certain circumstances when calculating TOD during flight, with CTDs that people are reporting. Its a different thing and will be fixed with the next update coming very soon.

We have no clear indication of the NXI causing CTDs or why that would be. But we are of course investigating.

Also to set the record straight again

NXI: Is a new instrument built from the ground up with the goal of replicating the G1000 NXI, which is available on the marketplace as "early access" until it is polished enough to be in the core sim

WTG1000: Is the "old" mod of the stock  legacy G1000 we had for months and is no longer maintained. There is a 0.4.0 release for SU5 compatibility though, which is just the stock G1000 + engine pages.

You should never have both installed at the same time.

Thanks for the clarification Dominik. To confirm, i was not using the WTG1000. As several other people have confirmed, installing this mod causes CTDs (for some) in planes that are equipped with the G1000. If you want i can share more details about my setup, settings, etc. Feel free to PM me if you think it would help. 

Edited August 8, 20214 yr by RobJC

Part of the crash dump analysis by WinDbg:

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff7c96cf458 (FlightSimulator+0x0000000000b6f458)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000023700303785
Attempt to read from address 0000023700303785

PROCESS_NAME:  FlightSimulator.exe

STACK_TEXT:  
000000ed`8277f520 00007ff7`c96cd44c     : 00000000`00000000 00000000`0000003d 00000000`0000003d 00007fff`5a4feb32 : FlightSimulator+0xb6f458
000000ed`8277f550 00007ff7`c96cce1e     : 00000239`dca7efb0 00007fff`00000007 00000000`00000a6e 00000239`dca7efc0 : FlightSimulator+0xb6d44c
000000ed`8277f5d0 00007fff`5a4f871b     : 00007fff`5a470000 00000000`00000a6e 0000023a`283ce030 00000239`53be4ff0 : FlightSimulator+0xb6ce1e
000000ed`8277f610 00007fff`5a4f4a9b     : 3f947c08`8f1b0000 00000239`53be4ff0 00000237`e28e5600 00000000`00000a6e : CoherentUIGT!Coherent::UIGT::ViewListener::operator=+0x72bb
000000ed`8277f680 00007ff7`cac3c870     : 00000000`00000000 00000239`48a51ea0 00000237`e28e5600 00000000`00000000 : CoherentUIGT!Coherent::UIGT::ViewListener::operator=+0x363b
000000ed`8277f6c0 00007ff7`cac37cdd     : 00000237`c2422120 00000000`00000000 00000000`00000023 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xf5fad0
000000ed`8277f700 00007ff7`cacce49a     : 00000237`e8b76d60 00000000`00000000 00000000`0000001c 00000000`00000019 : FlightSimulator!FlightSimGetProcessId+0xf5af3d
000000ed`8277f730 00007ff7`cacce97d     : 00000237`c2596300 00000000`00000000 80000000`00000000 00007ff7`ca4fa57f : FlightSimulator!FlightSimGetProcessId+0xff16fa
000000ed`8277f770 00007ff7`caa3997d     : 00000003`c9e0bce8 00000237`c2596300 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xff1bdd
000000ed`8277f7c0 00007ff7`caa392c0     : 00000000`00000000 00007ff7`cd19e190 00000000`00000001 00000000`00000007 : FlightSimulator!FlightSimGetProcessId+0xd5cbdd
000000ed`8277f810 00007ff7`ca4f0e25     : af358769`00009fe0 af358769`e4469aa8 00007ff7`ca4f3330 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xd5c520
000000ed`8277f850 00007ff7`cb2dcc92     : 00000000`00000005 00000000`00000000 00000000`00000000 01d78bc9`96408443 : FlightSimulator!FlightSimGetProcessId+0x814085
000000ed`8277f890 00007fff`9d467034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0x15ffef2
000000ed`8277f8d0 00007fff`9f202651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000ed`8277f900 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_FlightSimulator.exe!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  1.18.15.0

The stack_text section may give some hints.

I have had the freeze on TOD calculation bug - which WT will address in the next relase - but other than that the NXi has been rock solid for me. In fact, after using the NXi it's difficult to go back to the other planes. 

I'm using it in the DA62X, with the default blue livery. 

Not convinced at all that you found "the major source of CTDs", maybe on your system who knows. 

Here is a nice video, demonstrating Vnav in the WT 1000 NXi

https://www.youtube.com/watch?v=C-nlNQYdx9c

The crash on loading could be from a synchronization issue. FS or avionic could be trying to read from an object, process, thread or buffer the is not fully initialized/allocated, then a read access memory violation exception is thrown.

Edited August 8, 20214 yr by Emerson67

Okay I went through and did some things to further isolate this issue.

NVIDIA: 471.41
Windows 10: Up to date (multiple updates performed)
Hyperthreading: On
UserCfg.opt: Terrain LOD: 2, everything default (no hacks)
Marketplace Purchases: Removed All of them
Community Folder: Empty
SimObjects Folder: Removed everything except Asobo
Packages Folder: Removed everything except Community and Official Folders.
USB Hardware: Mouse/Keyboard + HP Printer hooked up (no TrackIR, Yokes, Joysticks, etc. installed)

MSFS Environment:

Multiplayer: All Players
Air Traffic: Live Traffic
Weather/Time: Live
Aircraft: Cessna 172 (G1000)

Test #1: Garmin G1000 NXI (not installed)

From: KSFO
To: KSEZ
Result: Success (meaning airport and plane loaded, able to takeoff) 

From: EGLL
To: LFPG
Result: Success

From: EGLL
To: EDDH
Result: Success

From: KDEN
To: KTEX
Result: Success

From: KLAX
To: KSEZ:
Result: Success

RESTART PC:

Test #2: Garmin G1000 NXI (installed)

From: KSFO
To: KSEZ
Result: Success 

From: EGLL
To: LFPG
Result: Success

From: EGLL
To: EDDH
Result: CTD
 

Aircraft: Baron G58

Test #3: Garmin G1000 NXI (not installed)

From: KSFO
To: KSEZ
Result: Success (meaning airport and plane loaded, able to takeoff) 

From: EGLL
To: LFPG
Result: Success

From: EGLL
To: EDDH
Result: Success

From: KDEN
To: KTEX
Result: Success

From: KLAX
To: KSEZ:
Result: Success

RESTART PC:

Test #4: Garmin G1000 NXI (installed)

From: KSFO
To: KSEZ
Result: Success 

From: EGLL
To: LFPG
Result: Success

From: EGLL
To: EDDH
Result: CTD

Aircraft: King Air 

Test #5: Garmin G1000 NXI (installed - but King Air does not use G1000)

From: KSFO
To: KSEZ
Result: Success (meaning airport and plane loaded, able to takeoff) 

From: EGLL
To: LFPG
Result: Success

From: EGLL
To: EDDH
Result: Success

From: KDEN
To: KTEX
Result: Success

From: KLAX
To: KSEZ:
Result: Success

Switch to Caravan (NXi still installed - Caravan uses G1000)

From: KLAS
To: KSFO
Result: Success 

From: KLAX
To: KPHX
Result: CTD

Just for comparison, I fly using five Garmin variants in GA planes:

• g1000 NXi - no issues
• WT g1000 Mod (g1000 NXi removed via CM) - no issues
• pms50 GTN750 w/ WT g1000 - no issues
• pms50 GNS530 - no issues
• WT g3000 (TBM) - no issues

This is not to diminish the issues some are having - just showing that installations and systems are reacting differently.

1 hour ago, RandallR said:

Just for comparison, I fly using five Garmin variants in GA planes:

• g1000 NXi - no issues
• WT g1000 Mod (g1000 NXi removed via CM) - no issues
• pms50 GTN750 w/ WT g1000 - no issues
• pms50 GNS530 - no issues
• WT g3000 (TBM) - no issues

This is not to diminish the issues some are having - just showing that installations and systems are reacting differently.

Oh i hear you, Randall. Those of us who have issues with this mod can easily reproduce the problem, yet others cannot. There must be some commonality here.

Edited August 8, 20214 yr by RobJC

In case this helps, I have an Intel CPU - my GPU is the RTX 2060 Super

Just wanted to come back with an update.

since removing the G1000 nxi ive had about a dozen flights today, ranging from 1hr 34mins down to a couple of minutes - I’ve had no CTDs!

Quick update on this. WT have a fix for this bug. Hopefully they will push a new update to the marketplace this week but they are not certain of that yet. I am running the fixed version and so far no crashes. I am sure WT/Dominik can add more details, but it looks like a timing issue probably related to Asobo moving Coherent into a different thread. 

It will be great if they have fixed it as I love the NXi, but I uninstalled it due to CTD's as well. 

I completed an hour long flight through the Austrian Alps then - it was great!  Then after a touch and go, I had to pause the sim for a few minutes (escape key), and when I came back it had crashed to desktop. Strange how it would crash when paused, but there you go.  Getting better though!

Edited August 10, 20214 yr by bobcat999