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.

Aircraft idle roll aircraft.cfg

Featured Replies

Who can point to what to change in aircraft.cfg for the Aircraft to roll on idle? As lowcost do, taxi on one engine.

Or maybe it is in the air file?
THNX

airfile, 1506 static thrust sea level. You will have to raise fN at the N1 level you want more thrust, which will also skew your idle fuel burn to burn more fuel 

Alternatively you could modify sim1.dll and reduce the rolling coefficient of friction, I have a few posts at fsdeveloper which explain what to do.

Edited by kand

  • Author

-

Edited by vl1

  • Author
19 hours ago, kand said:

airfile, 1506 static thrust sea level. You will have to raise fN at the N1 level you want more thrust, which will also skew your idle fuel burn to burn more fuel 

Alternatively you could modify sim1.dll and reduce the rolling coefficient of friction, I have a few posts at fsdeveloper which explain what to do.

Much appreciated, Ken

It says Turbine Corrected Thrust Factor
Correct?

Will give it a try

4 hours ago, vl1 said:

Much appreciated, Ken

It says Turbine Corrected Thrust Factor
Correct?

Will give it a try

Yes, one axis is the scalar for thrust at sea level, the other is the N1. You want to increase the number at the corresponding N1 . Bear in mind this table is for corrected which means ISA values, 15c, sea level, 1013mb etc. The scalar represents to the static thrust value in the aircraft.cfg

I always used to hack sim1.dll for each point release on p3d because lowering the friction coefficient actually corrects the error, unfortunately LM have never fixed this.... 

38 minutes ago, kand said:

I always used to hack sim1.dll

Do you have instructions on how to do this?

Best regards, Dimitrios

9950X3D - 64 GB - RX 7900 XTX - TrackIR - Power-LC M39 WQHD - Honeycomb Alpha yoke, Saitek pedals & throttles in a crummy home-cockpit - MSFS for props, P3D for jets

  • Author
3 hours ago, kand said:

Yes, one axis is the scalar for thrust at sea level, the other is the N1. You want to increase the number at the corresponding N1 . Bear in mind this table is for corrected which means ISA values, 15c, sea level, 1013mb etc. The scalar represents to the static thrust value in the aircraft.cfg

I always used to hack sim1.dll for each point release on p3d because lowering the friction coefficient actually corrects the error, unfortunately LM have never fixed this.... 

Therefore I am supporting the question above. How we do that?

Thanks!

Best regards, Dimitrios

9950X3D - 64 GB - RX 7900 XTX - TrackIR - Power-LC M39 WQHD - Honeycomb Alpha yoke, Saitek pedals & throttles in a crummy home-cockpit - MSFS for props, P3D for jets

There are a couple downsides to doing this, either with a sim1.dll hack, or with a table 1506 mod in the .air file.

The sim1.dll hack works, but some of the better add-ons already take the faulty friction coefficients into account in their FDE, and changing them in the dll will screw up TOLD performance with those add-ons.  So a one-size-fits-all change to the dll is problematic.  You could create several versions of the dll and swap them depending on the plane to be flown...a bit tedious, but possible.

To do things right in table 1506 usually requires adding one or two curves...the idea is to bump up the thrust at very low mach numbers associated with ground ops (e.g. <0.1) while preserving the thrust curves at higher mach numbers associated with flight.  The default acft and many/most add-ons use two curves, one at mach 0, one at mach 0.9--simply bumping up the values there will result in excessive thrust at idle inflight, affecting descent and landing performance.  The best way is to add another curve at ~M 0.1 and set the Mach 0 curve to thrust values that better represent performance at idle on the ground and will overcome the excessive ground friction  The curve at M0.1 facilitates smoothly returning the thrust values to the flight regime at higher speeds.  It may be better still to add another curve at ~M0.2 to allow for a more gradual transition.  You'll still see high fuel flow during ground ops.  The only way to cure this is programmatically within the panel gauges, as fuel flow in the sim engine is a function of thrust--higher thrust -> higher fuel flow.

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

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.