Jump to content
The simFlight Network Forums

Stefan01

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stefan01

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  • Location
    Germany
  1. Dear Pete and John, Thank you very much for the quick reply and advice. I have implemented the last suggestion and it works. I have created a new folder Sound in the FSUIPC6 folder and copied the sound files there. I changed the line for the sound.path to sound.path("C:\\Users\\Myname\\Documents\\Prepar3D v5 Add-ons\\FSUIPC6\\Sound") as suggested. After starting, the sound was heard again when switching the thrust reverser on and off. If I remember correctly I installed FSUIPC6 into the folder "C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6" as suggested by the installer. Aft
  2. I have a problem with FSUIPC 6.0.12 registered and the Lua Script ThrottleManager. The previous versions were still installed in the Modules folder in the main directory of P3D. There the Throttlemanger worked with my different aircrafts from PMDG and FSLabs without any problem. After installing FSUIPC 6 outside the directory of P3d, the throttle manager only works to a limited extent. The thrust reverser still works, but the sound that normally sounds when switching the thrust reverser on and off is no longer audible. My installation locations are as follows FSUIPC in the folder "C:\Use
  3. Hi, Pete, Thank you very much for the clarification. I actually used the time acceleration on the ground to shorten the waiting time until the brakes cooled down. I would never have thought that the function depends on the altitude. Thanks again for the quick clarification. Stefan
  4. Thanks for the quick answer. I will wait till P3D has a bugfix. Thanks again Stefan
  5. P3D V4.3.29.25520 FSUIPC 5.14 I have set the hot key for simulation rate =ctl+Space. In the past with this hotkey the simulation rate was always set to normal. I don't know when that changed. Now the simulation rate is reduced by only 2 steps, for example from 64 to 16 and from 16 to 4 etc. The key combination is not assigned to any other function in P3d. Does anyone have any idea what I can do to set the simulation rate to normal with using the hot key once? Thanks a lot Stefan
  6. If you need more logs to analyse please let me know. regards Stefan
  7. 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
  8. P3d v4.2; Fslabs 2.0.1.232; 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
  9. 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
  10. 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 Li
  11. 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 4.0.28.21686 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
  12. 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
  13. 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
  14. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.