Maybe fsuipc-lvar-module files crash MSFS.

[DaveSCUSA]

I just purchase a new PC and installed MSFS, FSUIPC7 and several other add-ons. Attached is a screenshot of the add-ons. I downloaded all freah versions (including FSUIPC7).

During the starting of MSFS, it crashed. Tried at least 3 times, crashed every time. I removed the items in the Community folder and added back one at a time.  The aircraft started flying at the end  of the runway and no crash. The last added was the FSUIPC7.log folder which crashed.

One of the first attempts that didn't crash was a start in safe mode which obviously bypasses the Community folder.

I have attached the Log, .ini and fsuipc-lvar-module files (obviously not the .hvar files).

FSUIPC7.log FSUIPC7_prev.log FSUIPC7.ini FSUIPC_WASM.ini layout.json manifest.json FSUIPC7_WASM.wasm

[John Dowson]

15 hours ago, DaveSCUSA said:

I have attached the Log, .ini and fsuipc-lvar-module files (obviously not the .hvar files).

But why attach the WASM - I distribute that. i need the FSUIPC_WASM.log file, not the files that are installed by the FSUIPC7 installer.

A WASM module should not crash MSFS - the WASM will just crash and MSFS will continue. Please see the Asobo forums for all MSFS CTDs.

This will most probably be something specific to your new PC. I cannot help with this.

[DaveSCUSA]

Since I am not familiar with WASM, as I'm sure most of your customers aren't, I didn't know ilog existed. Not sure I even saw it. I'll go check.

[DaveSCUSA]

I recreated the crash. MSFS crashes (closes down) just after the FSUIPC7 console is displayed (the MSFS Main Menu screen has not yet displayed).

As suspected, There is no FSUIPC_WASM.log file.

You could at least provide pointers on how to debug this issue. 

FSUIPC7.log

[John Dowson]

1 hour ago, DaveSCUSA said:

Since I am not familiar with WASM, as I'm sure most of your customers aren't, I didn't know ilog existed. Not sure I even saw it. I'll go check.

Please see the WASM section in the Advanced User manual:

Quote

WASM module ini file and parameters

The WASM module takes its default settings from ini files. These are named FSUIPC_WASM.ini and can be located:
    1. In the WASM folder, under your Community/fsuipc-lvar-module folder
    2. In the WASM persistent storage area, which is:
        For Steam installs, in the following folder under your user account:
              AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work
        For MS Store installs, in the following folder under your user account:
              AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvarmodule\work
    The FSUIPC WASM log file (FSUIPC_WASM.log) can also be found in this location.

 

26 minutes ago, DaveSCUSA said:

As suspected, There is no FSUIPC_WASM.log file.

There is, if you look in the correct location...

27 minutes ago, DaveSCUSA said:

I recreated the crash. MSFS crashes (closes down) just after the FSUIPC7 console is displayed (the MSFS Main Menu screen has not yet displayed).

If you look at the log file you attached, you will see that FSUIPC7 had noy yet even tried to connect to MSFS before it had crashed:

Quote

...
      547 Auto-started via EXE.xml with DetectToConnectDelayAuto=30, InitialStallTime=15
     3359 Simulator detected
     8375 MSFS no longer running - exiting
...

So FSUIPC7 has nothing to do with this crash. MSFS crashed soon (8 seconds or so) after it started FSUIPC7.

You can attach the FSUIPC_WASM.log when you find it, but it will not show anything as your crash has nothing to do with FSUIPC7 or the FSUIPC WASM module. The WASM module doesn't do much at all (except initialise itself) until an aircraft is loaded and ready-to-fly, and your crash is (mostly) happening before then.

31 minutes ago, DaveSCUSA said:

You could at least provide pointers on how to debug this issue. 

If using DX12, try disabling that - this is known to cause CTDs for a lot of people. Also try disabling some on-line functionality, such as live-traffic and live weather to see if that helps.

If you remove everything from your Community folder, does MSFS still crash (on occasion) or not? If you install just FSUIPC7 (and nothing else), does it then crash?

I, as well as most other MSFS users I guess, also sometimes experience CTDs or, more usually, MSFS hanging on start-up. Usually these issues just go away on their own accord without me doing anything, although I have had to re-install on occasion.

Other than that, I cannot help with MSFS CTDs. You can check the windows Event viewer for a crash report - this should give further information on where/why MSFS crashed, and you can include this information if you want to report to Asobo.

 

[DaveSCUSA]

1 hour ago, John Dowson said:

Please see the WASM section in the Advanced User manual:

1 hour ago, John Dowson said:

Please see the WASM section in the Advanced User manual:

I have no need or desire to look at details.

1 hour ago, John Dowson said:

So FSUIPC7 has nothing to do with this crash. MSFS crashed soon (8 seconds or so) after it started FSUIPC7.

If so, why does it not crash when the fsuipc-lvar-module folder is removed from the Community folder or starting MSFS in "Safe" mode. FSUIPC7 starts in both cases with the EXE.xml file and has no issues.

1 hour ago, John Dowson said:

For MS Store installs, in the following folder under your user account:
              AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvarmodule\work
    The FSUIPC WASM log file (FSUIPC_WASM.log) can also be found in this location.

Perhaps as you can see by the attached image, there is no ...\fsuipc-lvarmodule\work folder in the Packages folder and therefore no log. I have changed the DirectX to DX11 and still have the issue.

I don't understand why you insist that it is not an FSUIPC7 and WASM conflict if envery thing runs corrctly without the wasm Folder. As I mentioned in my first entry, I moved add-on items back into the Community folder one at a time the FSUIPC WASM folder last. MSFS worked fine until I readded the WASM folder and it crashed. Continued with further testing and shown the crash occurs when the fsuipc-lvar-module folder is present, not crash when absent.

[John Dowson]

11 hours ago, DaveSCUSA said:

Perhaps as you can see by the attached image, there is no ...\fsuipc-lvarmodule\work folder in the Packages folder and therefore no log. I have changed the DirectX to DX11 and still have the issue.

The images you attach show the LocalCache folder. Try the LocalState folder.
If there is no fsuipc-lvar-module folder under your Packages folder, then it is either because the WASM module is never started (or never ran long enough to generate/create a log file).
Alternatively, there is something seriously wrong with your MSFS installation.

11 hours ago, DaveSCUSA said:

I don't understand why you insist that it is not an FSUIPC7 and WASM conflict if envery thing runs corrctly without the wasm Folder. 

If FSUIPC7 or the FSUIPC WASM was causing MSFS to crash on start-up, don't you think I would have noticed that here? I would also expect thousands of complaints, yet it is only you...

11 hours ago, DaveSCUSA said:

As I mentioned in my first entry, I moved add-on items back into the Community folder one at a time the FSUIPC WASM folder last. MSFS worked fine until I readded the WASM folder and it crashed. Continued with further testing and shown the crash occurs when the fsuipc-lvar-module folder is present, not crash when absent.

Does it crash if the FSUIPC WASM is  the ONLY item in your Community folder, and not without it installed?

Try downloading and installing again. You recently reported a similar strange issue with FSUIPC7 crashing on start-up - you said you resolved that issue but you never said what the issue was. Maybe whatever this issue was is causing this?

But I repeat, for the last time, this is not an issue in FSUIPC7 or with the FSUIPC7 WASM. The issue lies somewhere else, and I cannot help you any further with this.

I really don't understand why you are always having so many issues...

[DaveSCUSA]

9 hours ago, John Dowson said:

If FSUIPC7 or the FSUIPC WASM was causing MSFS to crash on start-up, don't you think I would have noticed that here? I would also expect thousands of complaints, yet it is only you...

I'm only asking for help in how to fix this. Perhaps I am one that has a unique setup, using FSUIPC7 facilities not often used and there is a conflict I can't find out of ignorance. Also, how many customers just give up or don't know there is a forum.

9 hours ago, John Dowson said:

Alternatively, there is something seriously wrong with your MSFS installation.

Perhaps, I'll reinstall MSFS and FSUIPC7. Seven hours to download and install MSFS.

9 hours ago, John Dowson said:

If FSUIPC7 or the FSUIPC WASM was causing MSFS to crash on start-up, don't you think I would have noticed that here? I would also expect thousands of complaints, yet it is only you...

Upon further testing, it is the combination of WASM and the DA62 Mod aircraft in the Community folder that crashes.

9 hours ago, John Dowson said:

You recently reported a similar strange issue with FSUIPC7 crashing on start-up - you said you resolved that issue but you never said what the issue was.

I no longer remember this item.

I found the logs. The most current one is the DA62 and WASM crash.

As I said, I'm just trying to find how to debug and fix the problem with your help. I'm not accusing FSUIPC of not recognizing an issue as you seem to consider I am dong.

I see the mention of the file MainMenu.FLT in the two logs that have errors. I have included the file.

MainMenu.FLT FSUIPC_WASM.log FSUIPC_WASM_prev.log FSUIPC_WASM_prev2.log

[DaveSCUSA]

I am also trying to use FSUIPC7 to connect 2 Sayo 12 Key devices to MSFS. Not sure if this is an average or common usage. Not knowing all the intricacies of the FSUIPC7, I may ask stupid or uninformed questions.

You assume your customers know as much as you and where items (files, documentation, subject location) are located. Your assumption seems that all your customers should have read all the documentation. Six percent of all activities as human performs are in error. Mistakes are made.

[John Dowson]

4 minutes ago, DaveSCUSA said:

I'm only asking for help in how to fix this.

And this not being an FSUIPC issue, I have given you all the help I can.

5 minutes ago, DaveSCUSA said:

Perhaps I am one that has a unique setup, using FSUIPC7 facilities not often used and there is a conflict I can't find out of ignorance.

I can guarantee you that this is not the case, MSFS is crashing BEFORE FSUIPC7 is even connected. The WASM may have started or not, but if it has it isn't doing much yet as MSFS is crashing on start-up.

7 minutes ago, DaveSCUSA said:

Also, how many customers just give up or don't know there is a forum.

Well, none I hope, There are FAR more who don't know or use the documentation...

8 minutes ago, DaveSCUSA said:

Upon further testing, it is the combination of WASM and the DA62 Mod aircraft in the Community folder that crashes.

Not sure why that would be...have you tried the support of the DA62 Mod?

10 minutes ago, DaveSCUSA said:

9 hours ago, John Dowson said:

You recently reported a similar strange issue with FSUIPC7 crashing on start-up - you said you resolved that issue but you never said what the issue was.

I no longer remember this item.

Wasn't that long ago - this one: 

 

15 minutes ago, DaveSCUSA said:

I found the logs.

Ok, but why was that so difficult? You complain about the documentation but never seem to consult it. I posted the relevant section and you still couldn't find it...

Of the 3 logs you posted, both of the _prev logs show that the WASM ran as expected and was closed/stopped cleanly by MSFS, i.e. no crash. For the FSUIPC_WASM.log, that shows the WASM was initialised and is waiting for an aircraft to be loaded, and MSFS was still running or MSFS has crashed.

I am sorry but I have no idea what is causing your crash, but it is not FSUIPC. I don't know what could be causing this CTD. I can try that mod here but I doubt very much I will get a CTD - there are several people using this mod with FSUIPC that I have already helped. See https://forums.flightsimulator.com/t/da62x-improvement-mod-v1-0-oct-4/294584/2650

Make sure that you are using the latest version of the mod - maybe download it again and re-install it (and make sure you delete the current mod from your Community folder first).

 

[John Dowson]

1 minute ago, DaveSCUSA said:

You assume your customers know as much as you and where items (files, documentation, subject location) are located. Your assumption seems that all your customers should have read all the documentation. Six percent of all activities as human performs are in error. Mistakes are made.

That would be a stupid assumption to make... I expect my customers to AT LEAST consult the documentation before posting. And for the majority of issues, there are only two documents you need to be familiar with - the User guide and the Advanced User guide. I am spending hours repeating things endlessly that are already documented, not only in the documents but in many support requests. As an example, if I ask for the FSUIPC_WASM.log, id you open the Advanced User guide, search doe FSYUPC_WASM.log, you will see the documentation oin where this is located. Quick and easy. It took several message exchanges and many hours for you to find this.

And please can you refrain from such message and this ongoing criticism of my support (or perceived tone). The more you continue to do this, the less inclined I am to help you. 

[John Dowson]

I have just checked and also have the DA62X mod installed, although I haven't used it for a while.