Lua Files

[gfd]

Greetings,

 

I know Peter is away until the 4th. However, I have an issue that I would appreciate some help with.

 

I reinstalled my system, upgrading to Windows 10. I did a clean install. I did save all of my flight data, including the Modules folder. I have just upgraded to the latest version of FSUIPC. I did a comparison on WinMerge and was able to merge the old and new FSUIPC ini file. There were few differences; mainly had to move the profile references into the new ini file. FSUIPC loads without issue. The controllers are recognized by FSUIPC correctly. The profiles (in folders) are recognized.

 

I have setup WideFS button screens on a networked machine. Just an excellent feature! Saves a bundle on hardware costs. I digress.

 

I have LUA files setup with custom scripts for button assignments. I loaded a flight with an aircraft that had a profile (in this case the A2A 172). The axes were setup as expected in the FSUIPC GUI. However when I pressed buttons on the controllers, the lua file did not show up. Only the parameter numbers. It seems FSUIPC forgot the lua file.

 

I looked in the profile and noticed entries like CL19, CL20, etc. Is that the code for the lua file(s)? Sample button entry in the profile:

 

21=R68,12,CL19:R,51

 

Is CL19 the reference to the lua file? If so, can re-train FSUIPC to recognize the files? If not, I suppose I'll have to reprogram FSUIPC for each of the profiles; at least the file reference. Not a big deal. Just curious.

 

Many thanks in advance for your assistance,

 

Graham

 

 

[Gypsy Baron]

"CL19, CL20, etc. Is that the code for the lua file(s)?:

 

Yes. The number is assigned by FSUIPC4 when it reads the Lua files in initially or when it sees a new one.

 

Does the list of Lua files in the INI file compare exactly to your previous file....#19 is <some lua file name>, #20 is <another file name>?

 

If you did not have the INI file setting set to:

 

[JoyNames]
AutoAssignLetters=Yes

 

but instead have "AutoAssignLetters=No" then it is quite possible that Windows assigned NEW JoyNumbers

when it scanned your controllers and FSUIPC4 still has the 'old' JoyNumbers and buttons.

 

Similar issues can occur if you unplug a controller then reinstall it later, perhaps after adding another controller.

If you have the AutoAssignLetters=Yes, then FSUIPC4 convers all Joy#'s to letters associated with the GUID of

]the controllers. These do not change  The first time you run FSUIPC4 after setting "Yes" all Joy#'s in each INI file line

will be converted to a letter that it assigned to each controller.

 

If this is what is causing your issues you MAY be able to save the day IF you still have a copy of your 'old' INI file

that shows the Number assigned to each controller and the GUID.

 

You would then go into the new INI after letters have been assigned and change the letter assignments to match

the old numbers GUIDs.

 

Here is what my letter vs number vs GUID list looks like.

[JoyNames]
AutoAssignLetters=Yes

0=Logitech Dual Action
0.GUID={6B5A2B40-5A5C-11E4-8002-444553540000}
1=Saitek X45
1.GUID={6B5A2B40-5A5C-11E4-8003-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={6B5A2B40-5A5C-11E4-8004-444553540000}
3=Saitek Pro Flight Throttle Quadrant
3.GUID={6B5A2B40-5A5C-11E4-8005-444553540000}
4=CH PRO PEDALS USB
4.GUID={E0590200-6113-11E4-8001-444553540000}


A=Saitek Pro Flight Throttle Quadrant
A.GUID={6B5A2B40-5A5C-11E4-8005-444553540000}
B=CH PRO PEDALS USB
B.GUID={E0590200-6113-11E4-8001-444553540000}
C=Saitek X45
C.GUID={6B5A2B40-5A5C-11E4-8003-444553540000}
D=Saitek Pro Flight Yoke
D.GUID={6B5A2B40-5A5C-11E4-8004-444553540000}
E=Logitech Dual Action
E.GUID={6B5A2B40-5A5C-11E4-8002-444553540000}

As for Lua files, here is what my list looks like:

 

!2=//----------------- LUA FILE LIST ----------------

[LuaFiles]
1=B377_exit_revers
2=B377_reverse
3=display vals
4=liar
5=freeze
6=init pos
7=ipcDebug
8=landing
9=record to csv
10=log lvars
11=RUN_VBS
12=Payload737
13=MasterClient
14=SlaveServer
15=testclnt
16=testsrvr
17=DispB17CS
18=A2A_B377_icflap
19=DispP47CS
20=gfdDisplay
21=DispP40
22=B17G_Turbo
23=Flak_Wind
24=DispSPIT
25=B17G_Gear
26=DispP51CS
27=DispF4U
28=DispC47CS
29=DispP51ASCS
30=DispP40_test
31=DispP51CIV
32=Calc_Track
33=DispB25J
34=DispLanc
35=DispC172
36=DispP180
37=DispB29CS
38=DispC182
39=DispP51H
40=Gear_Switch
41=B17_Mechanic
42=pucker
43=DispPA24
44=DispB24


Hope this helps you track down your issues.

 

 Paul

[gfd]

Thanks Paul. You've given me a start at getting this solved.

 

Graham

 

EDIT: Just as a follow up, I compared the ini and profile files. You were bang on. I had gotten rid of a number of lua files and what was once CL19 is now CL5. This is in addition to the fact that perhaps FSUIPC gave the lua files different reference numbers in the new installation.

 

It is all so very elegant and simple. Too bad I didn't figure it out for myself. Thank you again Paul, for turning me in the right direction.

[Gypsy Baron]

Glad you got it sorted out. And fortunately you had a reference point. I tend to keep a copy of my INI file, updated periodically, just in case some unforseen event changes the dependancies.

 

   Paul