Masterius

I haven't had a chance to test this out yet, but you may want to try this: 1) First, locate, then copy the fsuipc.ini file and save it somewhere on your drive as a backup, then open the original file. Look for the entry heading [LuaFiles]. If you do not see one, create one after the [Axes] and [Keys] entries. 2) Next, remove these two Lua names from the [LuaFiles] section if they are there:1) Alt_Inc, and 2) Alt_Dec 3) Next, place this file (save it as alt_var_custom.lua) in the FSUIPC folder that also holds your LINDA files: function alt_var_custom () function AltitudeSet_Up () a = ipc.readLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH") a = a + 1000 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) end function AltitudeSet_Down () a = ipc.readLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH") if a<=1000 then a=0 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) else a = a - 1000 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) end end event.control (65892,“AltitudeSet_Up”) AltitudeSet_Up (65892) event.control (65893,“AltitudeSet_Down”) AltitudeSet_Up (65893) end 4) Finally, add the Lua name alt_var_custom using the next sequential numeric value to the [LuaFiles] section. If this works correctly (no guarantees since I haven't been able to test it since I didn't have a multipanel until late last night) you shouldn't have to assign anything to get this to work; it'll load at initial start-up and run in the background. ~Masterius

The parameter needs to be blank.

I am now also seeing these when I never have before: 5731110 **** DevCom read/write threads still running - will exit anyway but could cause issues... 5731422 **** DevCom Read thread terminated 5731922 **** DevCom read/write threads still running - will exit anyway but could cause issues... 5732219 **** DevCom Read thread terminated 5732735 **** DevCom read/write threads still running - will exit anyway but could cause issues... 5733032 **** DevCom Read thread terminated 5733547 **** DevCom read/write threads still running - will exit anyway but could cause issues... 5733844 **** DevCom Read thread terminated 5734360 **** DevCom read/write threads still running - will exit anyway but could cause issues... 5734672 **** DevCom Read thread terminated

This is all predicated on FSUIPC being able to read your rotary, and do so as button presses: First, create two text files, one for each function. For instance, call one file Alt_Inc.lua and the other Alt_Dec.lua. Copy and paste the functions in their respective file. For instance, Alt_Inc.lua would be: function AltitudeSet_Up () a = ipc.readLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH") a = a + 1000 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) end Change Alt_Dec.lua to be: function AltitudeSet_Down () a = ipc.readLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH") if a<=1000 then a=0 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) else a = a - 1000 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) end end Second, place these files in the FSUIPC folder that also holds your LINDA files. You should see both LINDA.exe and FSUIPC(version).ini in that folder. Third, copy the fsuipc.ini file and save it somewhere on your drive as a backup, then open the original file. Look for the entry heading [LuaFiles]. If you do not see one, create one after the [Axes] and [Keys] entries. Next, add the Lua names to the [LuaFiles] section. If you had to create that (and using the above sample names) it would be this: 1=Alt_Inc 2=Alt_Dec If there are already entries there, add these using the next sequential numeric value. Once you have added these, save and close the file. Finally, start up your sim and load the Carenado CJ2. Open up FSUIPC. Select the "Buttons & Switches" tab. Tick the "ProfileSpecific" box, operate the rotary in the direction for altitude increase to that the "Press Button" box populates with the value for that rotary, then the "Select for FS Control" box. Next click the dropdown select arrow of the "Control sent when button pressed" menu, and scroll down until you find Lua Alt_Inc then select that. Repeat that for altitude decrease. Click [OK] to save and close FSUIPC. Your rotary should now work. ~Masterius

The only rotary switches I am familiar with are my Saitek radio panel and on my X52 HOTAS, and neither of those are readable by either LINDA or FSUIPC. Can LINDA or FSUIPC "read" your rotaries? If so, if they output readable signals, then there should be a way of doing what you want. ~Masterius

LINDA 3.3.5.1363 FSUIPC 6109 Prepar3D v5, 5.3.17.28160 I have two issues with LINDA locking up and freezing. One is something that's always happened as far back as I can recall, and the other is something that's only recently started. The first is when I try saving the current HID assignments. With an aircraft profile loaded, and SELECT JOYSTICK selected, clicking immediately locks up the program, with the window indicting (Not Responding) and the cursor a swirling blue "wait" circle. The second is more recent. For one, I've started seeing this message during initial loading/startup: "[ERROR] SetFaultDiagnosisMode - LogOptionProtect Access violation at address 007ADC70 in module 'LINDA.exe'. Read of address 7102C619 [5]" This does not appear to cause any noticeable issues that I'm aware of, but is is something I don't recall seeing before. However, if I reload LINDA for any reason, it gets stuck at the red-lettered warning of LINDA restarting, do not press any buttons. Checking the console, it appears to be stuck during loading at either 1) : [INIT] Initialising HID devices... or 2) : [EVNT] InitHID... In either case, I have to shut down LINDA and restart or, in some instances, reboot the computer entirely.

Glad it worked! ~Masterius

I'm not sure what you mean by this. Do you mean a hat switch or rotary encoder?

Check the "ident.lua" file, and change the simfolder location.

Franz, I am totally unfamiliar with the Carenado CJ2, nor have access to either the aircraft or its Lvars. However, this might work for you: function AltitudeSet_Up () a = ipc.readLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH") a = a + 1000 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) end function AltitudeSet_Down () a = ipc.readLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH") a = a - 1000 ipc.writeLvar ("L:CUSTOM_AP_ALT_VAR_SET_ENGLISH", a) end Assign the first function to one button press and the second to another. I'm not sure how/where you're putting your lua files, but I normally put them in the specific aircraft's user file, and assign the lua to a button from there. For instance, when LINDA first opens select the Carenado CJ2 from the aircraft drop-down box, then select [Joysticks]. Locate the button you wish to assign (easiest way is just press it) then right-click to bring up the assignment menu. Go down to the User functions and click the topmost Edit User Module. If you haven't added anything there yet it'll be blank except for the default messages. Add the two functions above after the line -- insert your code below here: and above the line -- Just a message in console and then click save then exit the window. Now you can assign the functions to your desired buttons.

For some reason the #2 engine of the Manfred B-50 (downloaded from rikoooo) will not start. It seems to be a magneto issue, which is strange because the aircraft has no controls for the magnetos. Does anyone have any suggestions as to how this might be fixed?

I don't think mine will work after all. I have to look closer into this.

I'm not sure how that would work, as both sim and radio panel show two-digit fractionals (i.e yyy.xx) and the 8.33 would require three (i.e yyy.xxx). Having said that, I would think that a script could be written to make that change, although you wouldn't be able to see that third digit. Something similar to this: function Radio_COM1 (RadioChannel1AFract, a) a = ipc.readLvar ("L:RadioChannel1AFract") n = (a*.3332) ipc.writeLvar ("L:RadioChannel1AFract", n) end event.Lvar ("L:RadioChannel1AFract", 100, Radio_COM1)

I've no idea what you mean by "spacing", sorry.

Dang. Well, thank you so much for the detailed explanation! That one I do know about: Under Windows/Sound/Communications selecting the radio button for "Do Nothing" for the "When Windows detects communications activity". Gotta love MS/Windows for their arrogant assumptions as to choosing options that are "best for us".