Fremmed
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Fremmed
-
-
On 9/12/2020 at 2:57 PM, John Dowson said:
Could you attach your FSUIPC7.log file please.
Sure.
-
On 9/9/2020 at 11:01 AM, John Dowson said:
I also released a new build yesterday. This has the automatic re-connect in and also (hopefully) fixes the crash that this introduced - please download and try this version. Report back if it re-connects and continues working please (or if it doesn't!), bit no more logs needed at the moment for this.
Still crashes on disconnect on my end.
-
5 hours ago, Pete Dowson said:
I'm pretty sure it always used to. but then it needs to use camera views and so far we've not had much success with the usual SimConnect controls for those. So it makes one think ...
Pete
I've done more testing now, and the same crashing happens with or without TrackIR running, but at much larger (a factor 10 probably) intervals when it's not.
-
8 hours ago, John Dowson said:
Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.
230MB 🙂
I cut about a half million lines of simread events from the middle.
-
1 hour ago, Pete Dowson said:
I'm pretty sure it always used to. but then it needs to use camera views and so far we've not had much success with the usual SimConnect controls for those. So it makes one think ...
Pete
FWIW, the trackIR shows up as a controller in the control options now. I assumed that meant it was accessed as a HID device. I don't think that used to be the case, though. I'll do some testing with an without it nonetheless.
-
1 hour ago, John Dowson said:
Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.
Of course. Will post later today.
9 minutes ago, John Dowson said:Btw, are you using any other SimConnect clients, or any 3rd party add-ons that use FSUIPC?
Lots usually, but during that testing, the only thing I had running in addition to FSUIPC and the sim itself was Track-IR, which I don't think is using SimConnect?
-
3 hours ago, John Dowson said:
Maybe try cutting it down a bit - I am only interested in the logs around the disconnection (and just before), so you can remove anything before this if that helps. Otherwise you could post a dropbox link (or other file sharing service) if you use that. Thanks,
John
Yes of course.... In doing that I did find something interresting in the simconnect log: It seems like every disconnect is preceded by a: 2121.74087 [326] I/O Error! (2, 80004004)
I don't have any other traces of any hardware errors on my system though, so It's not obvious what exactly is the problem. Fwiw, 0x80004004 usually means "Operation aborted". I think it'd be a bit weird to call network issues "I/O error", but I'll try some offline flights in any case.
Btw, the crashing fsuipc logs the following:
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
Description:
Faulting application name: FSUIPC7.exe, version: 7.0.0.0, time stamp: 0x5f51fe86
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x06701e03
Exception code: 0xc0000005
Fault offset: 0x00000000000213ad
Faulting process id: 0x1d64
Faulting application start time: 0x01d6847397f963e6
Faulting application path: E:\Gamezorz\misc\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: db32fc42-7500-494b-9845-39b796126e58
Faulting package full name:
Faulting package-relative application ID: -
Just now, John Dowson said:
Yes, sorry - I should have updated the build date in that version.
Try zipping them first. They are text files and should compress pretty small.
John
Yeah, the simconnect log is 45MB. So even after compressing 90% they're still about 250 times the limit. 🙂
-
I have the same issue but perhaps even a bit more severe than the others in here, since the build from page 1 in this thread actually crashes and dies when the disconnect happens.
It seems to me that it disconnects after a certain amount of data sent to flightsim: If I'm on autopilot and basically not touching the controls, it can live for hours -- if I'm doing crazy flights up rivers and under bridges and whatnot, it can crash in less than a minute. Almost makes me guess that Asobo is profiling simconnect data and have a counter that overflows or something.
Anyway, I have some logs for you, if you want them -- both fsuipcs logs from the debug build in this thread, and from the release of the 28th of august (they identify themselves as the same version in the logs, that's maybe not ideal), along with their respective simconnect logs..
However, these logs are larger than the forum will let me attach, and I don't feel like having pointers to any of my own ways of sharing files dangling around on the internet. But I can PM you a URL if you want.
FSUIPC7 intermittent disconnects: TransmitClientEvent failures
in FSUIPC7 MSFS
Posted
I think you did. No disconnects so far here. Thank you.