Dynamic friction with FSUIPC 4.9.2.3

[microlight]

Hi Pete,

 

I'm new to the forum. Can you help me with the DynamicFriction.lua, please? I only today discovered (via a post in the Classic British Flight Sim forums) that FSUIPC can address the ground friction issue in FSX that was also present in FS9. I thought I'd followed the instructions there, which were:

 

- download the latest version of FSUIPC (I had 4.9.0 but have replaced it with 4.9.2.3)

- copied the DynamicFriction.lua file from the installer's 'example LUA plugins' zip archive into the modules folder

 

The CBFS instructions then say that when FSX is run, that an additional entry is automatically made to the INI file, which activates the LUA file:

 

[Auto]
1=Lua DynamicFriction

 

I've done all of this, but the automatic addition to the INI file doesn't happen. When I add it manually, there's no difference in the sim. What I did to confirm was to run the default Cessna up to 50kts at full power and then cut the power and let the plane run, noting where it stops. It stops in exactly the same place without the LUA file, and with it and the INI file addition.

 

There must be something that I'm not doing correctly - can you help, please?

 

Many thanks from the UK.

Martyn

[Pete Dowson]

The CBFS instructions then say that when FSX is run, that an additional entry is automatically made to the INI file, which activates the LUA file:

 

[Auto]

1=Lua DynamicFriction

 

No, there is no automatic addition. There's no way FSUIPC can know you are wanting to run that Lua file automatically. YOU have to edit the INI file and add the above section!

 

The use of [Auto] sections to run plug-ins and macros is covered in the Advanced User's guide for FSUIPC.

 

When I add it manually, there's no difference in the sim. What I did to confirm was to run the default Cessna up to 50kts at full power and then cut the power and let the plane run, noting where it stops. It stops in exactly the same place without the LUA file, and with it and the INI file addition.

 

I have no idea if that is a good measure of what it is supposed to do. I thought the changes made were all to do with grip, not rusty wheel bearings -- reducing the tendency to slide sideways in cross wind, for example. But I don't really know much about all this at all. I only provide access to the tables of coefficients. Perhaps you should ask someone over in one of the Forums (AVSIM) where all this was originally discussed?

 

Regards

Pete

[microlight]

Thanks for the feedback, Pete, I've left the Auto section in. Like you, I don't know if that test was meaningful (it was a repeat of what someone else did on Avsim) but It certainly does appear to make planes behave better on the ground. Thanks for all your efforts on behalf of the community.

[bjratchf]

So do we enter 

 

[Auto]
1=Lua DynamicFriction

 

into the fsuipc.ini or not, if we'd like to have dynamic friction enabled?

As well as putting the dynamicfriction.lua file in the modules folder of FSX

[Pete Dowson]

So do we enter 

 

[Auto]

1=Lua DynamicFriction

 

into the fsuipc.ini or not, if we'd like to have dynamic friction enabled?

As well as putting the dynamicfriction.lua file in the modules folder of FSX

 

Yes, that's probably the easiest way to use that plug-in. [Auto] sections are just ways of running macros and plug-ins automatically. You can have different [Auto.<profilename>] sections for different aircraft profiles too, for aircraft-ralted plugins and macros.

 

All macros and plugins are loaded from the Modules folder by default. You can have them elsewhere but you then need to specify the path.

 

Pete

[bjratchf]

Thanks Pete...

 

I somehow never remembered seeing that, and assumed just because the entry

 

[LuaFiles]

1=DynamicFriction

 

appeared in the fsuipc.ini after the lua module was extracted into the "modules" folder of FSX (and FSX was run once), that the lua module was in operation. I'll go ahead and add the [AUTO] section to my fsuipc.ini now.

 

It will look like this:

 

[LuaFiles]

1=DynamicFriction

[Auto]

1=Lua DynamicFriction

[Pete Dowson]

It will look like this:

 

[LuaFiles]

1=DynamicFriction

[Auto]

1=Lua DynamicFriction

 

Do NOT add your own [LuaFiles] section. That is generated by FSUIPC automatically based on the Lua files it finds in the Modules folder. It is nothing to do with the [Auto] section, it is only used when assigning buttons or keys to L:ua plug-ins.

 

Pete

[EasyEE]

Hello Pete. Not trying to beat a dead horse but have one quick question. Once the lua scripts have been added and the AUTO section added in the FSUIPC .ini file, should I leave the Patchsimfriction entry as = yes? Or change it to = No? Thanks.

[Pete Dowson]

Hello Pete. Not trying to beat a dead horse but have one quick question. Once the lua scripts have been added and the AUTO section added in the FSUIPC .ini file, should I leave the Patchsimfriction entry as = yes? Or change it to = No? Thanks.

 

Should really be No, otherwise the values which any Lua might restore will be the patch values not the originals.

 

Pete

[EasyEE]

Much appreciated. Thanks.

[bjratchf]

ok just to be absolutely "computers for dummies"clear... the only entries in fsuipc.ini necessary for dynamic friction to WORK

 

 

IS.... 

[LuaFiles]

1=DynamicFriction

[Auto]

1=Lua DynamicFriction

 

No spaces? Spaces? (1 = Lua DynamicFriction vs 1=LuaDynamicFriction) Doesn't matter?  AND....all WE need to do is add the [Auto] section, is this all correct? There is so much conflicting information out there and  I just want to be clear. Thanks!

[Pete Dowson]

ok just to be absolutely "computers for dummies"clear... the only entries in fsuipc.ini necessary for dynamic friction to WORK

 

 

IS.... 

[LuaFiles]

1=DynamicFriction

[Auto]

1=Lua DynamicFriction

 

No spaces? Spaces? (1 = Lua DynamicFriction vs 1=LuaDynamicFriction) Doesn't matter?  AND....all WE need to do is add the [Auto] section, is this all correct? There is so much conflicting information out there and  I just want to be clear. Thanks!

 

The "DynamnicFriction.lua" file must be present in the FS Modules folder.

 

Don't edit the [LuaFiles] section at all! That's simply where FSUIPC registers the Lua files present in the Modules folder. The numbers assigned MUST stay as they are for assignments to Lua plug-ins to work.

 

There is a space between "Lua" and the name of the plug-ib Lua is the command, the rest is the name. Everywhere this is published it contains that space so why question it now?

 

If you are still using FSUIPC version 4.923, as [er thos thread#s title,  then you must update as it hasn't been supported for a long time. current in 4.937.

 

Pete