[WideFS not connecting when run as admin]

Specifying the protocol seems to have worked, the client now connects to the server. Why it worked with regular privileges and not with elevated ones I'm still wondering. Anyways, that far it works, now to make FliteDeck see my GPS position, because currently it does not :D

Thanks for the help

Luca

[WideFS not connecting when run as admin]

I should have attached my WideFS.ini, sorry for that. Adding the serverIPAddr parameter was the first thing I did when this issue came up, read the docs back and forth trying to figure it out. I might try the protocol =TCP setting, didn't think it'd have an impact as it works on regular user privileges

 

; PLEASE SEE WideFS documentation for parameter details
; =====================================================

[Config]
ServerIPAddr=192.168.1.10
Port=8002
Window=924,452,886,589
Visible=Yes
ButtonScanInterval=20
ClassInstance=0
NetworkTiming=5,1
MailslotTiming=1000,1000
PollInterval=2000
Port2=9002
ReconnectMinutes=0
ResponseTime=18
ApplicationDelay=0
TCPcoalesce=No
WaitForNewData=500
MaxSendQ=100
OnMaxSendQ=Log
NewSendScanTime=50
Priority=3,1,2

; -----------------------------------------------
[User]
Log=Errors+

[GPSout]
Port=COM1
Speed=19200

; ===============================================
[Sounds]
Path=C:\Program Files (x86)\WideFS\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio(SST))

 

[WideFS not connecting when run as admin]

Hi Pete

Thanks for the swift response, let's hope we can get this resolved before CTP :P

Anyways, logs attached below, also my diagnosis flow in images here: https://imgur.com/a/6BP2W

Hope this helps you figure out this mess

Thanks!

Luca

Elevated user privileges WideClient.log

WideServer.log

Regular user privileges WideClient.log

[WideFS not connecting when run as admin]

I have both ports 8002 and 9002 excluded from the firewall on both TCP and UDP both in and out, shouldn't be an issue I don't think, I also don't kow how that would be affected by user privileges

[WideFS not connecting when run as admin]

Hello everyone

The issue I've run into is fairly simple. I'm running WideFS server registered on my sim PC and wideFS client on my Surface. When I run the wideFS client normally it connects to the server just fine but it won't produce GPS output (which I need for Jepp FliteDeck), and when I run it as admin it does generate GPS data (can be monitored in VSPE, the client is writing data to the connector), but the client won't connect to the server anymore.

I'm pulling my hair out over this one, maaybe you can help

Cheers

Luca

Edit: Just for additional info, seems like WideFS Client is running version 6.999z4, WideFS Server is on 7.971 and FSUIPC is on version 5.121b, same behaviour with version 4.971 though

[P3D V3 CTD when FSUIPC is enabled]

Thanks for the quick answer and sorry for not getting back to you sooner.

 

Sadly, this didn't fix my problem, and the weather program I'm using is ASN which works beautifully on other peoples machines, so I'm hesitant to blame it.

 

Thanks anyways

 

Luca

[P3D V3 CTD when FSUIPC is enabled]

Hello.

 

Whenever I have FSUIPC activated in the DLL.XML of P3D it crashes after 20mins max, whereas I can fly for at least eight hours straight when it is not active. The error log mostly says the faulting file was weather.dll, but I've also had atc.dll related crashes.

 

It's really too bad because I really like the utility of the addon (and the fact that some third-party addons require it to run makes it somewhat of a neccessity), and I would be really happy if it worked again

 

Thanks a lot and greetings

 

Attached: Error log (sorry that it's in german, though I suppose the structure will be the same)

 

Protokollname: Application
Quelle:        Application Error
Datum:         18.10.2015 17:06:12
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      ******
Beschreibung:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.0.10.14945, Zeitstempel: 0x560b4abe
Name des fehlerhaften Moduls: weather.dll, Version: 3.0.10.14945, Zeitstempel: 0x560b49cc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00034987
ID des fehlerhaften Prozesses: 0x1cc0
Startzeit der fehlerhaften Anwendung: 0x01d109b621b40746
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\weather.dll
Berichtskennung: c4ce5fc3-75a9-11e5-82dd-08002700cc53
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-10-18T15:06:12.000000000Z" />
    <EventRecordID>23803</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LucaPC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.0.10.14945</Data>
    <Data>560b4abe</Data>
    <Data>weather.dll</Data>
    <Data>3.0.10.14945</Data>
    <Data>560b49cc</Data>
    <Data>c0000005</Data>
    <Data>00034987</Data>
    <Data>1cc0</Data>
    <Data>01d109b621b40746</Data>
    <Data>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\weather.dll</Data>
    <Data>c4ce5fc3-75a9-11e5-82dd-08002700cc53</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>