FSUIPC- selective dynamic friction...

[bjratchf]

I'm happy with the way the dynamicfriction lua works- makes taxiing and maintaining a respectable and stable speed more on par with what I experience in the real world.

 

In any case, it's not that compatible with certain aircraft- is there a way to make the dynamicfriction.lua active with certain aircraft, and use FSX default friction for other aircraft?

 

[spokes2112]

You could assign 2 keystrokes - one to kill dynamicfriction.lua & one start it. IMO that would be the easiest way. One could also write a LUA to control how dynamicfriction.lua is run or stopped but that would require editing as your hangar changes. 

[ark1320]

If you are using a/c profiles, you can activate the Dynamic Friction script just for those profiles or aircraft you want to use it with. The below is from the FSUIPC Advanced User manual:

 

Automatic running of Macros and Lua plugins
By some editing in the INI file, you can arrange for one or more Macros or Lua plugins to be executed, in order,
automatically whenever the current aircraft is changed (or, indeed, first loaded), or a specific named aircraft (or
Profile) is loaded.
This allows switches, offsets, and other things to be set specifically for an aircraft (or aircraft type, for Profiles) when
it is first loaded.
This is done by adding new sections to the INI file with the title{
[Auto]
or
[Auto.xxxx...]
where the xxxx part is the aircraft name, or part-name (as in Aircraft Specific sections), or a profile name when
profiles are being used.
These Auto sections thus parallel the Keys and Buttons sections -- the naming and selection follows the same system.
The generic [Auto] section is carried out for all aircraft changes whilst the specific ones are only applied to matching
aircraft or profile..
Each Auto section contains a series of numbered lines (1=..., 2=... etc) each of which is either a Lua command, or a
Macro call. For example:
[Auto.737]
1=Lua SetMyOffsets
2=737 OHD:Air Allbleeds
When Lua calls run a plug-in which doesn't self-terminate, the plug-in thread still running is killed automatically on
an aircraft/profile change.

 

Note the last line above means if you switch from a plane using Dynamic Friction to one the doesn't, the script is automatically stopped as you would want.

 

If you use Dynamic Friction most of the time, instead of turning it on in selected profiles, it may be more convenient to turn it on in general as you do now ( I assume ), and then use a command in specific profiles to turn it off. Exactly what command to use to do that I don't know (maybe something like Dynamic Friction =0), but if it is possible to do Pete will certainly be able to tell you how to it.

Al

[bjratchf]

Ok thanks for your help...

 

I ended up creating profiles like this for aircraft I want to use dynamic friction with. Funny enough, the maddog MD80 by leonardo doesn't need it- it seems they have their own working. If I use the dynamic friction with this aircraft, it'll start accelerating at idle power and cause brake overheat problems.

 

Here's what the ini looks like.

 

[LuaFiles]

1=DynamicFriction

 

[Auto.PMDG MD11]

1=Lua DynamicFriction

 

[Auto.Milviz King Air]

1=Lua Dynamic Friction

 

..and so on... for aircraft I want to activate the script for.

 

I haven't tested with the MD80, but my hope is that it "shuts off" when loading that aircraft, since it has no auto/dynamicfriction entry in fsuipc.ini

[bjratchf]

Yep, looks like I'd need a restore function for if I load up the MD80 after an aircraft that uses the dynamic friction lua script.

[ark1320]

Yep, looks like I'd need a restore function for if I load up the MD80 after an aircraft that uses the dynamic friction lua script.

I don't know what you mean by a restore function. According to the FSUIPC manual, once you switch a/c, the Dynamic Friction Lua script should terminate.  So if you load the MD80 after, say the King Air, the Dynamic Friction script should not be a factor. If that is not happening, maybe you need to put the MD80 into its own profile that does not call the Dynamic Friction script.

Al

[bjratchf]

Ok so what I had to do to fix this...

 

I opened up the dynamicfricions.lua script and edited the friction values back to default, and saved it as defaultfrictions.lua. Then I assigned this script to the maddog's own profile.

 

It seems that when the dynamicfrictions.lua is loaded, it overwrites the friction settings for that simulator session, even if you load another aircraft that does not call on the script. However, loading another lua that restores the friction, overrides the previous script of course, and restores the default settings.

[ark1320]

 

I opened up the dynamicfricions.lua script and edited the friction values back to default, and saved it as defaultfrictions.lua. Then I assigned this script to the maddog's own profile.

 

It seems that when the dynamicfrictions.lua is loaded, it overwrites the friction settings for that simulator session, even if you load another aircraft that does not call on the script. However, loading another lua that restores the friction, overrides the previous script of course, and restores the default settings.

OK, I understand now what you are saying. I didn't realize the Dynamic Friction script made a "permanent" change to the FSX friction values.  Nice clever solution on your part to overcome that problem.

 

Glad you got it all figured out.

Al