Jump to content
The simFlight Network Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stefan01

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
  1. Version 7.141 problem solved. Many Thanks Stefan
  2. If you need more logs to analyse please let me know. regards Stefan
  3. I used to place the wideclient.exe in the folder "C:\Program Files (x86)\Wideclient". Running in this place it was not possible to get the logfiles. So I moved it to folder "C:\Wideclient". Here it is running sometimes with no problem. Enclosed logs WideClient_error after reboot with error , WideClient_ok_1 to 3 after reboot everything is fine. I have no idea what causes the error but I try different start scenarios, perhaps it is influenced by the sequence how I start the apps. Regards Stefan WideClient_error.zip WideClient_ok.zip WideClient_ok_2.zip WideClient_ok_3.zip
  4. P3d v4.2; Fslabs; AS for P3dv4 6620, FSUIPC 5.124 registerd and Wideclient 7.140. Both PC on WIN 10 latest version Hi all I have updated to WideClient 7.14 and experienced some problems. A small tool to calculate the takeoff performance data named TOPS - TAKEOFF PERFORMANCE SYSTEM FSX P3D which is running on my second PC was unable to load the flight data. IVAP which is also running on the second PC was not able to detect when I switched in the aircraft the transponder from stdby to TARA. After I installed WideClient 7.10 again everything was ok. Regards Stefan
  5. Pete/Scot, I was able to solve the problem. Due to the fact that somehow the problem startet with the start of Linda I checked which files are relatetd to the devices. I found in linda-cfg the file config-hid.lua and restored an older version. That solved the problem. Somehow something became mixed up in this file. Thanks again Stefan
  6. Pete/Scot thanks for your quick answer. I have no powersaving function set in WIN 10 and if I leave the pc for hours without action, all the devices still work. I have now set P3d so that it will start without any addons. It takes 50 seconds to start, the most time was used to load the AI aircraft from MTL for IVAP. I have done 3 tests with different config. 1.) Start P3D and FSUIPC only. I renamed the Lind.lua to Linda.lua.txt. to prevent the loading of the lua file. In that case the CH Fighterstick is ok. 2.) Start P3D and FSUIPC but in that case with Lind.lua . But in Linda settings I have unchecked start GUI with sim. Anyhow I got the message Linda restarting pls wait… and Linda ready In that case Ch Fighterstick was not working .But I can “repair” as written above. 3.) Start P3D with Start P3D and FSUIPC and in Linda settings I have checked start GUI with sim. That is how I normally start. …and in that case Ch Fighterstick was not working. But I can “repair” as written above. I used Linda and I enclose the FSUIPC and the Linda log from the test No. 3 So it seems that the problem is more LINDA related. After Scotfleiger is already reading this do you think I should writte this again in the Linda forums? Thanks again Stefan FSUIPC5.log linda2.log linda2.log.debug
  7. Hi Pete When I boot win 10 Pro and check with “devices and printers” the game controller settings of the CH Fighterstick it is ok( buttons and axes work) When I start P3DV the buttons and axes of the CH Fighterstick are not active. The other devices work fine. When I open the FSUIPC GUI select axes assignment and “reload all assignments” buttons and axes of the CH Fighterstick are active ( I can use them). Best regards Stefan FSUIPC5.log
  8. In the meantime I have found a topic in the P3D Development forum. Ref: "LINDA LUA crashing P3D3.4 on Exit" http://www.prepar3d.com/forum/viewtopic.php?f=6310&t=122273 Stefan
  9. Sorry but I don t know how to switch off the LINDA logging to FSUIPC.log Knowing that P3d is crashing during shutdown I made one more tests. I removed the line Run1=KILL,C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\linda.exe From FSUIPC.ini Than I started P3D and after that LINDA.exe with mouse click. I closed first LINDA and then P3D.The result P3D is also crash during shutdown as I could see in the event viewer. So it seems that the crash has nothing to do with FSUIPC. Stefan
  10. You are right. When i terminate P3D it seems to crash. In the event viewer I get the information that P3D crashed. This is not visble but it seems that during the shut down an unhandled exception occurs which crashes the app. Thanks for your help Stefan
  11. This is the log after P3D was terminated and LINDA was terminated (manually 60seconds after P3D ). I have checked this with task manager. When Linda was running after P3D was terminated I was not able to cut and paste the FSUIPC.log file because LINDA blocked it. After LINDA was closed I was able to cut and paste the lof file. I also enclosed the FSUIPC.ini Stefan FSUIPC4.log FSUIPC4.ini
  12. Now it seemed to work. I have made my name and mail invisible I hope this is ok. This matter is not urgent it is more or less a question of comfort. Enjoy your off-time. Stefan FSUIPC4.log
  13. I tried to upload the log but dont know if I was sucessfull
  14. P3D v3.4.9.18400 I have placed the CallSim... line in the section [General] CallSimConnectEnd=No CallSimConnectEnd=Yes Makes no difference When I exit P3D I can see in the task manager when P3D Symbol disappears a few seconds later behind the LINDA symbol the message “Not responding” in red for a short while. I also set Linda.exe to WIN 7 compatibility mode, nothing changed Stefan
  15. Up to now the KILL command for LINDA.exe worked fine. That means when P3D was shut down after a few seconds the LINDA.EXE app was also terminated throug the KILL command. LINDA.EXE does not start another programm as far as I know and I did not change anything regarding this app. Manually means after P3D is terminated I make a mouse click on the red cross on the upper right corner of the LINDA window, than LINDA.exe is closing. Is it possible to downgrade to FSUIPC 4.9.555 running the installer of 4.9.555 to find out if this changes the situation? Or can I do something else to find out why the KILL command is ignored? Stefan