Jump to content
The simFlight Network Forums

Dynamic friction problem in P3D v2.2


Recommended Posts

Hello everyone!

 

Having trouble getting the dynamic friction to work in P3D.  I have installed the DynamicFriction.lua, entered "[Auto]

1=Lua DynamicFriction" in the ini file, but the log file brings up an error.
 
This is a complete stock, and very fresh, installation of Prepar3d so I haven't tweaked or changed anything.
 
Any ideas?
 
********* FSUIPC4, Version 4.929 by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini"
Running inside Prepar3D v2 on Windows 7
Module base=53D80000
User Name="K*******y"
User Addr="k*********1@hotmail.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       15 System time = 11/04/2014 19:56:03
       15 FLT path = "G:\Users\Keith\Documents\Prepar3D v2 Files\"
       15 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\SimConnectP3D2.dll
       15 Found it: trying to connect
       31 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"
      406 LogOptions=00000000 00000001
      406 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
      421 WARNING: Failed to install Mouse Macro hooks!
      421 Wind smoothing fix is only partially installed
      421 SimConnect_Open succeeded: waiting to check version okay
      421 Trying to use SimConnect Prepar3D
     2312 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.2.10437.0 (SimConnect: 2.2.0.0)
     2312 Initialising SimConnect data requests now
     2312 FSUIPC Menu entry added
     2343 G:\Users\Keith\Documents\Prepar3D v2 Files\New Save.FXML
     2343 C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR
    29671 System time = 11/04/2014 19:56:32, Simulator time = 19:56:06 (02:56Z)
    29687 Aircraft="Beech Baron 58 Paint1"
    30687 Starting everything now ...
    31859 Advanced Weather Interface Enabled
   157328 Sim stopped: average frame rate for last 128 secs = 19.9 fps
   163968 System time = 11/04/2014 19:58:47, Simulator time = 19:58:13 (02:58Z)
   163968 *** FSUIPC log file being closed
Average frame rate for running time of 128 secs = 19.9 fps
Memory managed: 67 Allocs, 67 Freed
********* FSUIPC Log file closed ***********
 

 

Link to comment
Share on other sites

You are running a version of FSUIPC which was released before P3D 2.2. I am surprised it doesn't cause a crash!

 

I have been on holiday.so unable to match P3D's release date last week. Version 4.93 of FSUIPC will be released later this week and will work with P3D 2.2. Meanwhile I suggest you remove FSUIPC4.DLL from the Modules folder, or at least be understanding if it causes crashes or other problems.

 

Pete

Link to comment
Share on other sites

Oh wow!

 

So clearly, the problem is the loose nut behind the keyboard!  :razz:

 

Never paid any mind to the version numbers.  Just installed it and went flying.  To be honest, other than the problem with the dynamic friction, I didn't notice any issues with Prepar3d v2.2 and FSUIPC 4.292.  Wind smoothing and controller calibrations seemed to work without a hitch.

 

At any rate, I'll standby for the update.

 

Thanks, Pete!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.