Jump to content
The simFlight Network Forums

little help with dynamic friction script


Recommended Posts

Hi everyone,

 

 

If possible I'd like a little help from someone who knows how to "bypass" this lua script for a determined aircraft.

 

I just recently recently find this dynamicfriction.lua when looking for the older (I guess) modified sim1.dll so the taxi can be more real when using the AXE.

 

Added the script with no problems and taxiing the AXE feels nice and smooth, even using only one engine.

 

My "problem" is when I fly with the PMDG B737NGX... As this plane taxis a lot better than the AXE with the default settings, with the dynamic friction values, it seems like the tire friction should be the default one. It just accelerates with no problems with idle throttle and 100% payload.

 

Is there a way that when flying the B737, the lua module is not applied?

 

Cheers!

 

Daniel

 

 

Link to comment
Share on other sites

Is there a way that when flying the B737, the lua module is not applied?

 

 

Just not running the Lua won't help, because it patches the tables in FS. You'd need a different Lua which just does the Restore action (I think there's one in the first line of dynamicfrinction.lua, isn't there?).

 

You'd need an [Auto ...] section specific to the NGX profile to load a Lua which restored the default frictions.

 

Pete

Link to comment
Share on other sites

Thank you Pete for replying so quickly!

if I understand what you're saying, not running lua with the ngx won't revert to default grip values because the table is changed as soon fsx loads fsuipc. correct?

I opened the script and indeed it contains two sets of values.

using the entrie [Auto "ngx profile"] how do I tell fsuipc to apply the the default friction values?

Link to comment
Share on other sites

using the entrie [Auto "ngx profile"] how do I tell fsuipc to apply the the default friction values?

 

The Auto section will be called [Auto.<name>] where you must replace <name> with the name of the Profile you are using for the NGX.

 

In there place just one line:

 

1=Lua ResetFriction

 

Then create the file "ResetFriction.lua" with just the following line in it:

 

ipc.RestoreFriction()

 

Save it in the Modules folder.

 

Pete

Link to comment
Share on other sites

Hey!

 

So, I did what Pete told me to do and obviously, it works! :)

 

I just have one doubt about FSUIPC profiles handling...

As I wrote here, I wanted to use the default friction values with the NGX and created a profile for the NGX with the livery I use more often. I also read here, that FSUIPC "looks" at the profiles' name and all the others aircraft that share a part of the name are also included in that same profile, automatically removing the hard work of creating one profile for each livery. It also worked fine.

I created the profile for the B737-800 Ryanair..., and all the B737s from 600 to 900 series are using the default friction values.

 

So, after that, it was time to do a test with the LSH "MadDog" MD-80. It also taxis with idle thrust, which I believe doesn't happen with this type of aircraft. If I'm completely wrong about this believe, please feel free to correct me! 

I added LSH MD-82 McDonnell Douglas profile and in this case only that particular one is affected by the ResetFriction LUA. All the other liveries, which also share the "LSH MD.82..." are using the DynamicFriction LUA

 

Shouldn't the all the MD-80s I have be using the default friction table? What am I missing here?

[Auto.Boeing 737-8ASNGX Ryanair Winglets]
1=Lua ResetFriction

[Auto.LSH MD-82 McDonnell Douglas]
1=Lua ResetFriction

[Auto]
1 = LUA DynamicFriction

[LuaFiles]
1=DynamicFriction
2=ResetFriction

[Profile.Boeing 737-8ASNGX Ryanair Winglets]
1=Boeing 737-8ASNGX Ryanair Winglets

[Profile.LSH MD-82 McDonnell Douglas]
1=LSH MD-82 McDonnell Douglas
Regards,
Daniel
Link to comment
Share on other sites

So, after that, it was time to do a test with the LSH "MadDog" MD-80. It also taxis with idle thrust, which I believe doesn't happen with this type of aircraft. If I'm completely wrong about this believe, please feel free to correct me! 

I added LSH MD-82 McDonnell Douglas profile and in this case only that particular one is affected by the ResetFriction LUA. All the other liveries, which also share the "LSH MD.82..." are using the DynamicFriction LUA

 

Shouldn't the all the MD-80s I have be using the default friction table? What am I missing here?

 

Is the "ShortAircraftNameOK" parameter in the FSUIPC INI file set to "substring"?

 

If so, do they all have the name you have definedfor that profile somewhere in their full name? i.e. "LSH MD-82 McDonnell Douglas"?

 

If you want all starting with "LSH MD-82" then make the Profile definition say so, i.e.

 

[Profile.LSH MD-82 McDonnell Douglas]

1=LSH MD-82

 

Otherwise each time you load a new aircraft, assign it to the "LSH MD-82 McDonnell Douglas" profile.

 

Really you'd have been better off choosing a more snappy name for the Profile.

 

Same regarding the Boeings. Instead of

 

[Profile.Boeing 737-8ASNGX Ryanair Winglets]

1=Boeing 737-8ASNGX Ryanair Winglets

 

why not use the "Boeing 737" part. Or if PMDG is in there somewhere, the PMDG part?

 

Profile names are intended to be chosen to represent a class of aircraft you want treated all the same. They don't need to have anything in common with actual aircraft names. The names listed in the Profile sections can be shortened versions of the real names, or with the "substring" setting (usually defaulted these days), and part of the aircraft names. Each profile can list many aircraft.

 

Regards

Pete

Link to comment
Share on other sites

Hi once again!

 

First, let me say how grateful I am with the support given here. Top class! A big thanks...

 

Second, I'm feeling really dumb, because I just can't get the logic about the profiles and assigning them to the aircrafts!  :oops:

 

After testing some of my aircraft, I decide to change what I wanted in the beginning and now, I just want to use the DynamicFriction with the AXE. Basically it's the same, but with opposite logic! 

So, I deleted everything previously added concerning the friction and inserted:

 

[Auto.Airbus A320]

1 = LUA DynamicFriction

 

 

then FSUIPC automatically inserted:

 

[Profile.Airbus A320]
1=Airbus A320
 
But it just doesn't work... I have the default friction with all my A320 Airbuses.
 
I was thinking that FSUIPC links the profiles to the aircrafts names and if there was a part of the name common to all of them, as tell me above about the "Boeing 737" part, or if there was a PMDG part anywhere, the profile would be applied to all of them. Am I understanding what you've been trying to explain to me?
 
 
I leave here the start of the cfg file from the AXE A320 and, if possible, I'd like to learn what I'm doing wrong... All the titles have Airbus A320 and I inserted a profile called Airbus A320. Why doesn't the LUA script gets assigned to the AXE?
[FLTSIM.0]
title = Airbus A320 Aer Lingus EI-DEK
sim = A320
model =
panel =
sound =
texture = AerLingusEIDEK
kb_checklists = AirbusA321_check
kb_reference = AirbusA321_ref
atc_id = EI-DEK
atc_airline = SHAMROCK
atc_flight_number =
ui_manufacturer = Airbus
ui_type = A320-214 CFM
ui_variation = Aer Lingus - Irish International Airlines
ui_typerole = Commercial Airliner
ui_createdby = Aerosoft
atc_parking_types = GATE 
description = Airbus X Extended - A320 CFM / Aer Lingus EI-DEK\nwww.aerosoft.com\nRepaint by Holgi (simtexture.de)


[FLTSIM.1]
title = Airbus A320 Aeroflot VP-BWH
sim = A320
model =
panel =
sound =
texture = AeroflotVPBWH
kb_checklists = AirbusA321_check
kb_reference = AirbusA321_ref
atc_id = VP-BWH
atc_airline = AEROFLOT
atc_flight_number =
ui_manufacturer = Airbus
ui_type = A320-214 CFM
ui_variation = Aeroflot
ui_typerole = Commercial Airliner
ui_createdby = Aerosoft
atc_parking_types = GATE 
description = Airbus X Extended - A320 CFM / Aeroflot VP-BWH\nwww.aerosoft.com\nRepaint by Holgi (simtexture.de)

Regards,

Daniel

Link to comment
Share on other sites

I was thinking that FSUIPC links the profiles to the aircrafts names and if there was a part of the name common to all of them, as tell me above about the "Boeing 737" part, or if there was a PMDG part anywhere, the profile would be applied to all of them. Am I understanding what you've been trying to explain to me?

 

 

Yes, but please look again.  I also asked you to check the setting of the ShortAircraftNameOk parameter in the [general] section of the INI file. That needs to be either 'Yes' or, better, 'Substring'. Yes will allow short names but they must start at the beginning, whereas Substring will select based on the partial name matching anywhere in the actual name.

 

If it is set 'No' you can only use full names.

 

BTW unless you have a general [Auto] section to restore the normal frictions, if you fly an A320 but then change to, say the NGX, the frictions will still be the modified ones.  So you still need the original stuff but loading the "ResetFriction" lua instead.

 

Pete

Link to comment
Share on other sites

Yes, but please look again.  I also asked you to check the setting of the ShortAircraftNameOk parameter in the [general] section of the INI file. That needs to be either 'Yes' or, better, 'Substring'. Yes will allow short names but they must start at the beginning, whereas Substring will select based on the partial name matching anywhere in the actual name.

 

If it is set 'No' you can only use full names.

 

It was indeed set to "No". I misinterpreted what you meant with the line ShortAircraftNameOk parameter the first time you ask...  I changed it to Substring, added the profile that will change for both A320 and A321 and as you wisely reminded me, also add the resetfriction lua to always come back to the original parameters!

 

Now this is what I have in my ini and it is working well! :)

 

[Auto.Airbus A32]
1 = LUA DynamicFriction


[Auto]
1 = LUA ResetFriction


[LuaFiles]
1=DynamicFriction
2=ResetFriction




[Profile.Airbus A32]
1=Airbus A32

Thank you very much Pete.

 

Regards,

Daniel

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.