Jump to content

mas618

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by mas618

    EFB version 2.0 status

    in EFB v1 (Read only, no longer supported)

    Posted

    Hi Martin,

     

    I fully understand all of you who want to know the release date. I really want to know it too ... :mrgreen:  Seriously, we have started the alpha tests some months ago and some features must now be reworked due to the experience of the testers. All in all we are on a good way, but I cannot say when it is finished yet. Thanks for understanding and being patient.

    Thx for answering (without really answering) but I fully understand and I will patiently wait for release! Happy summer to all!

     

    Martin

    Starting Dataprovider causes Vpilot Trafficproxy/simcon cras

    in EFB v1 (Read only, no longer supported)

    Posted

    Ok - I think, THINK it is solved...

     

    I wanted to do another test, so I made sure to only start the DataProvider at first, and I had simconnect output enabled. This time, I can get everything up and running ;) I swear to God I did that before, but maybe a couple of restarts did the trick... Sorry to have wasted your time - but thanks you for your help!

     

    Can't wait to have v2.0 on fsuipc, to get out of simconnect!!

     

    Martin

    Starting Dataprovider causes Vpilot Trafficproxy/simcon cras

    in EFB v1 (Read only, no longer supported)

    Posted

    Yes I did, and to add, I did some further testing, and it seems that the data provider only crashes, when I operate the Mindstar GNS, and more specifically, when I make the first waypoint. However, I can operate the GNS without issues when the data provider is not running. To my knowledge the GNS does not use simconnect other than for hardware input, which I don't use. So to me (and I'm really not knowledgeable about this) it seemed that there is a simconnect "conflict" between the Mindstar and the EFB...

     

    But what really boggles my mind is that the app crash relates to the traffic proxy..?

     

    I den read in some other forum, that the Mindstar "listens" for hardware input via simconnect....

     

    Really hope you can solve this..

     

    Is there a simconnect log I can look into?

     

    Martin

    Starting Dataprovider causes Vpilot Trafficproxy/simcon cras

    in EFB v1 (Read only, no longer supported)

    Posted

    Hello guys.

     

    Everytime I start the Dataprovider, my trafficproxy on server machine crashes (connected to Vpilot) on client laptop via simconnect.

     

    I use several add-ons, but I can reproduce a crash everytime by starting the dataprovider.

     

    Situation:

    Server:

    p3d v.2.4, ENAL, Aerosoft Twitter extended , Mindstar GNS, EFB dataprovider, Traffic Proxy, TrackIR, FsCaptain, reg. FSUIPC

     

    Client: ASN, Wideclient, Vpilot, EFB DsiplayUnit - all connected via Simconnect.

     

    Appcrash log (detailed text)

    Log Name: Application

    Source: Windows Error Reporting

    Date: 22-12-2014 14:28:37

    Event ID: 1001

    Task Category: None

    Level: Information

    Keywords: Classic

    User: N/A

    Computer: FSX-Pc

    Description:

    Fault bucket , type 0

    Event Name: CLR20r3

    Response: Not available

    Cab Id: 0

     

    Problem signature:

    P1: trafficproxy.exe

    P2: 1.0.5365.23193

    P3: 540ef8e9

    P4: Microsoft.FlightSimulator.SimConnect

    P5: 10.0.61259.0

    P6: 46fad670

    P7: 175

    P8: 37

    P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX

    P10:

     

    Attached files:

    C:\Users\FSX\AppData\Local\Temp\WERBBF1.tmp.WERInternalMetadata.xml

     

    These files may be available here:

    C:\Users\FSX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_trafficproxy.exe_794410a01990bff73ece2e504d5814e1fe608e72_11fdc006

     

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 6e22e4ef-89de-11e4-a5ea-5404a6c591c7

    Report Status: 1

    Event Xml:

    1001

    4

    0

    0x80000000000000

    55172

    Application

    FSX-Pc

    0

    CLR20r3

    Not available

    0

    trafficproxy.exe

    1.0.5365.23193

    540ef8e9

    Microsoft.FlightSimulator.SimConnect

    10.0.61259.0

    46fad670

    175

    37

    PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX

    C:\Users\FSX\AppData\Local\Temp\WERBBF1.tmp.WERInternalMetadata.xml

    C:\Users\FSX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_trafficproxy.exe_794410a01990bff73ece2e504d5814e1fe608e72_11fdc006

    0

    6e22e4ef-89de-11e4-a5ea-5404a6c591c7

    1

     

    -------

     

    Log Name: Application

    Source: Windows Error Reporting

    Date: 22-12-2014 13:44:34

    Event ID: 1001

    Task Category: None

    Level: Information

    Keywords: Classic

    User: N/A

    Computer: FSX-Pc

    Description:

    Fault bucket , type 0

    Event Name: CLR20r3

    Response: Not available

    Cab Id: 0

     

    Problem signature:

    P1: trafficproxy.exe

    P2: 1.0.5365.23193

    P3: 540ef8e9

    P4: Microsoft.FlightSimulator.SimConnect

    P5: 10.0.61259.0

    P6: 46fad670

    P7: 175

    P8: 37

    P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX

    P10:

     

    Attached files:

    C:\Users\FSX\AppData\Local\Temp\WER678A.tmp.WERInternalMetadata.xml

     

    These files may be available here:

    C:\Users\FSX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_trafficproxy.exe_794410a01990bff73ece2e504d5814e1fe608e72_07ed6b23

     

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 46c26251-89d8-11e4-a5ea-5404a6c591c7

    Report Status: 1

    Event Xml:

    1001

    4

    0

    0x80000000000000

    55171

    Application

    FSX-Pc

    0

    CLR20r3

    Not available

    0

    trafficproxy.exe

    1.0.5365.23193

    540ef8e9

    Microsoft.FlightSimulator.SimConnect

    10.0.61259.0

    46fad670

    175

    37

    PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX

    C:\Users\FSX\AppData\Local\Temp\WER678A.tmp.WERInternalMetadata.xml

    C:\Users\FSX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_trafficproxy.exe_794410a01990bff73ece2e504d5814e1fe608e72_07ed6b23

    0

    46c26251-89d8-11e4-a5ea-5404a6c591c7

    1

     

    -------

     

    Log Name: Application

    Source: Windows Error Reporting

    Date: 22-12-2014 13:44:25

    Event ID: 1001

    Task Category: None

    Level: Information

    Keywords: Classic

    User: N/A

    Computer: FSX-Pc

    Description:

    Fault bucket 649764617, type 17

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

     

    Problem signature:

    P1: Prepar3D.exe

    P2: 2.4.11570.0

    P3: 542314d3

    P4: StackHash_4079

    P5: 6.1.7601.18247

    P6: 521ea8e7

    P7: c0000374

    P8: 000ce753

    P9:

    P10:

     

    Attached files:

    C:\Users\FSX\AppData\Local\Temp\WER3A53.tmp.WERInternalMetadata.xml

     

    These files may be available here:

    C:\Users\FSX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b5e6755d43fc77e1a9d0ec96fd0c54637343e10_02514b63

     

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 3fd23865-89d8-11e4-a5ea-5404a6c591c7

    Report Status: 0

    Event Xml:

    1001

    4

    0

    0x80000000000000

    55170

    Application

    FSX-Pc

    649764617

    17

    APPCRASH

    Not available

    0

    Prepar3D.exe

    2.4.11570.0

    542314d3

    StackHash_4079

    6.1.7601.18247

    521ea8e7

    c0000374

    000ce753

    C:\Users\FSX\AppData\Local\Temp\WER3A53.tmp.WERInternalMetadata.xml

    C:\Users\FSX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b5e6755d43fc77e1a9d0ec96fd0c54637343e10_02514b63

    0

    3fd23865-89d8-11e4-a5ea-5404a6c591c7

    0

     

    Screenshot of error:

    http://s354.photobucket.com/user/mas618 ... 9.png.html

     

    Thx

     

    Mas

×
×
  • Create New...