That error message gives a hint at the problem but isn't quite enough information.
Was there a button to show more details of the crash? If not, you could try opening the Windows Event Viewer and finding the Error in the Application log. Hopefully there will be some more detail there.
Sadly no Show More button. Event Viewer essentially just has what I've already reported, the XML file includes data about Windows and the computer but no file names. The Event Viewer link to a file in ProgramData doesn't exist. I've just noticed that the report is made multiple times as if there are several files not accessible.
Where does the test version store its files, I have an appdata/local/joinFS but no appdata/local/joinFS (test) - should that exist?
Could you run the stable version. Enable logging to a file. Then run the test version. After it crashes, look at the log - current file and post the details, thanks.
We have a gent that "Had" the same problem.
Going thru the 1.4.3 test run, logging, then back to point 8 pretty much let us know what was up..
A simconnect reinstall (all of them except Russian) from the "redist" took care of it.
Join FS Log -
03/02/2018 20:29:05.058 Started
03/02/2018 20:29:05.079 SimConnect 10.0.61259.0 not installed.
03/02/2018 20:29:05.487 No such host is known
03/02/2018 20:29:15.084 SimConnect 10.0.61259.0 not installed.
03/02/2018 20:30:32.466 Disconnected from simulator
Windows Log -
Log Name: Application
Source: Windows Error Reporting
Date: 03/02/2018 20:18:31
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-GNUMERR
Description:
Fault bucket 1366725810301173237, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Peter wrote:Could you run the stable version. Enable logging to a file. Then run the test version. After it crashes, look at the log - current file and post the details, thanks.
Done that, in fact turned on detailed logging too. File contains one line
EDIT: Just tried renaming the folder and 1.4.8 creates a new folder and a log file in there. Where are the settings saved? Is this in the Registry cos it knew to create the log file.
picnic wrote:As i said this is on a server with no FS so I've not installed SimConnect on it. 1.4.3 works would you expect different behaviour here with 1.4.8?
That's possibly related. Until very recently it was a requirement to have SimConnect installed otherwise JoinFS wouldn't run. However, I removed that link to allow it to run successfully. I wonder if something has broken that change?
Something has changed as I had the same crash and installed the simconnect .msi 10.0.61259.0 from P3D redist \FSX-SP2_Xpack and the crash is gone...win 10 latest fixes.( new system installed yesterday).
Ok I can confirm that it's a the SimConnect missing that makes a difference. I also installed the redist\FSX-SP2_Xpack from P3D and now 1.4.8 runs without crashing.
Do you mean the user list entry for yourself? The 'Connected' column refers to your network connections to each user, so it should always be Yes for your own entry in that list since your always connected to your own client. That should never show up as No for yourself and it's nothing to do with the connection to your simulator.