Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Ground Friction and P3D v4.5

Featured Replies

Are folks still tweaking the sim1.dll file in order to gain "realistic" ground friction in P3D v4, or are any alleged issues now largely resolved in the latest releases (P3D v4.5 HF2)? I note that Pete Dowson's lua files for friction do not work in P3D v4 and he may not wish to modIfy anything accordingly.

Pete Dowson has written about this before on his support forum...the previous FSUIPC versions for FSX and 32-bit P3D had to hack into the dll at runtime to change the data in the tables, and the lua used that facility.  Starting with FSUIPC v5 (for P3D v4.x) he's no longer hacking the internals of the sim with FSUIPC; instead he's using LM's expanded Simconnect interface...which is the big reason why FSUIPC doesn't break with every minor P3D update like it used to.  To-date, LM has not exposed the friction table data structures for user access via Simconnect.  So if you want to modify the friction tables in P3D v4.x (which are essentially still the same as those in FSX and all previous versions of P3D) then you will need to alter the tables encoded in sim1.dll yourself. 

 

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

I'm feeling no need for this anymore. At least the addon aircraft I use currently are properly configured in this regard "from factory".

Best regards,

Wanthuyr Filho

Instagram: AeroTacto

  • Author

Just loaded the latest sim1.dll file (P3D v4.5 HF2)into Hex Editor Neo and I am getting gobbledygook. I cannot locate where the friction values start. Has anyone actually successfully fixed sim1.dll for the latest LM release?

2 hours ago, LecLightning56 said:

Just loaded the latest sim1.dll file (P3D v4.5 HF2)into Hex Editor Neo and I am getting gobbledygook. I cannot locate where the friction values start. Has anyone actually successfully fixed sim1.dll for the latest LM release?

Good luck. Here's a thread at FSDeveloper about this topic in P3d4:

https://www.fsdeveloper.com/forum/threads/ground-friction.440265/

There's a bunch of other ground friction threads there also:

https://www.fsdeveloper.com/forum/search/352230/?q=sim1.dll&o=date

Herve Sors used to keep track of the ground friction offset location in sim1.dll for use in his utility AFSD, but I'm not sure whether it's been kept up to date for P3d 4.5 HF2. You might want to check with him.

I think the offset in HF2 is at 00159d24, at least that's what I get in Hex editor Neo.

  • Commercial Member
5 hours ago, Wanthuyr Filho said:

I'm feeling no need for this anymore. At least the addon aircraft I use currently are properly configured in this regard "from factory".

L-M argues that they adjusted them properly in any case and should need no further messing. They say if you find you need to it is to do with some poorly specified aspects of your add-on aircraft.

Personally I've never found any need to make adjustments, but then i've only used a 738 (originally the default from FSX but since I started using ProSim, just its 738), and the JustFlight Piper Arrow III. These are the aircraft suiting my two hardware cockpits.

Pete

 

Win10: 22H2 19045.2728
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3800 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 25Hz onto 200 FOV curved screen

  • Author
2 hours ago, jabloomf1230 said:

I think the offset in HF2 is at 00159d24, at least that's what I get in Hex editor Neo.

Thanks for the information. I shall have a look later.

 

1 hour ago, Pete Dowson said:

L-M argues that they adjusted them properly in any case and should need no further messing. They say if you find you need to it is to do with some poorly specified aspects of your add-on aircraft.

Personally I've never found any need to make adjustments, but then i've only used a 738 (originally the default from FSX but since I started using ProSim, just its 738), and the JustFlight Piper Arrow III. These are the aircraft suiting my two hardware cockpits.

Pete

 

As always, Sir, thank for your excellent information and advice on the subject.

7 hours ago, Pete Dowson said:

L-M argues that they adjusted them properly in any case and should need no further messing. They say if you find you need to it is to do with some poorly specified aspects of your add-on aircraft.

Which P3D version does this adjustment go back to?  I still use v3.4, so I wonder if it was already adjusted for that version.

  • Commercial Member
2 hours ago, Afterburner said:

Which P3D version does this adjustment go back to?  I still use v3.4, so I wonder if it was already adjusted for that version.

I don't know.  It may have been part of the movement from 32- to 64- bit code (so fixed in P3Dv4). And that may have been because proper programmable access to the friction tables was part of the list of requirements I prepared for them when I was planning FSUIPC5 -- the request may have prompted them to look at the values.

OR it may just be that L-M believe they were okay in the first place.

Sorry, I've no way of telling which it might be. I only know that I have never found them to be wrong with the aircraft models I've used.

Pete

 

Win10: 22H2 19045.2728
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3800 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 25Hz onto 200 FOV curved screen

  • Author

I have now managed to tweak the sim1.dll file successfully for P3D v4.5 HF2 and the results look good for the Aerosoft DHC-6-300. As a number of people have discovered, this can be an awkward customer taxying (particularly if you have Lukla airport selected), and the tweaks made do render the control of this aircraft on the ground much easier. I believe I am correct in saying that Aerosoft do not intend to develop this product any further, including considerations of the ground friction issues with this aircraft.

Thank you all for your inputs and for the benefit of your knowledge and advice. I do hope that LM address any outstanding issues on this subject at some stage if the user community believe that issues do still exist (although the future course of P3D is uncertain).

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.