Jump to content
The simFlight Network Forums

Honeycomb Bravo Throttle Config.


Dreamflight767
 Share

Recommended Posts

10 hours ago, Dreamflight767 said:

Is there a tutorial on using FSUIPC to configure the Honeycomb Bravo Throttle?  I'm having a difficult time setting the (MCP/Autopilot) buttons.

No, sorry, there is no tutorial. And how you configure can also depend on the aircraft. Most MCP/Autopilot functions can be controlled using lvars or hvars (or MobiFlight events), if the standard controls don't work (or aren't available). You can try listing the available lvars/hvars (using the Add-ons->WASM-< List Lvars/Hvars menu entry), and then setting/changing (lvars) or activating (hvars) them, using the menu options under Add-ons->WASM. Once you have found the ones that work, you can assign them to your buttons using either macros, lua or the lvars-to-offsets functionality.

I can't really help with such a general request, but if you let me know what aircraft you are using (and which mod, if applicable), and which button & function you would like to assign, I can maybe help you with that, which would then give you an idea of how to set-up the remaining buttons.

John

Link to comment
Share on other sites

11 hours ago, John Dowson said:

No, sorry, there is no tutorial. And how you configure can also depend on the aircraft. Most MCP/Autopilot functions can be controlled using lvars or hvars (or MobiFlight events), if the standard controls don't work (or aren't available). You can try listing the available lvars/hvars (using the Add-ons->WASM-< List Lvars/Hvars menu entry), and then setting/changing (lvars) or activating (hvars) them, using the menu options under Add-ons->WASM. Once you have found the ones that work, you can assign them to your buttons using either macros, lua or the lvars-to-offsets functionality.

I can't really help with such a general request, but if you let me know what aircraft you are using (and which mod, if applicable), and which button & function you would like to assign, I can maybe help you with that, which would then give you an idea of how to set-up the remaining buttons.

John

Thanks John.  I was kinda hoping that one setting would apply to all aircraft.  For example, the "function knob" when I select HDG would allow me to make changes to the heading on the MCP of all airplanes.  PMDG, FSLABS, MD-80, Dash 8.

 

Link to comment
Share on other sites

On 7/3/2021 at 12:24 PM, John Dowson said:

Most MCP/Autopilot functions can be controlled using lvars or hvars (or MobiFlight events), if the standard controls don't work (or aren't available). You can try listing the available lvars/hvars (using the Add-ons->WASM-< List Lvars/Hvars menu entry), and then setting/changing (lvars) or activating (hvars) them, using the menu options under Add-ons->WASM. Once you have found the ones that work, you can assign them to your buttons using either macros, lua or the lvars-to-offsets functionality.

Sorry, this is not true - I was thinking of FSUIPC7/MSFS - please ignore this!

On 7/3/2021 at 11:49 PM, Dreamflight767 said:

I was kinda hoping that one setting would apply to all aircraft.  For example, the "function knob" when I select HDG would allow me to make changes to the heading on the MCP of all airplanes.  PMDG, FSLABS, MD-80, Dash 8.

Ok. You can try assigning to the standard P3D controls for this - they may work, but more complex add-ons can implement there own controls, either using custom controls or by repurposing other controls, usually the Rotor Brake control.

There are a few things you need to know to do this. The first is how the increment/decrement rotary works on the bravo. It is a one-button rotary type, which means it triggers one button in each direction when you turn this. By default, you can only assign one action to each button in each direction. To get around this, you can use a lua script to convert the physical button presses into virtual ones, to provide a fast and slow virtual button-click in each direction. If you do this, you can then assign large inc/dec controls to the fast virtual button, and as smaller inc/dec control to the slow virtual button press. There is an example lua script provided that you can use (adjust as needed) called Rotaries.lua, and there is also a specific lua script for the Bravo for this in the User Contributions section.

To change the heading, you can then assign the rotary buttons (or virtual buttons, if you decide to use that mechanism) to the either:
 - the heading bug controls, Heading Bug Inc/Dec, and Heading Bug Inc/Dec Fast
 - to the Offset SWord Increment/Decrement controls, using offset 0x07CC (Autopilot Heading Value), where you can specify the size of the inc/dec for each button or virtual button press

Once you have set-up the rotary assignment, you then need to edit the FSUIPC6.ini to add a 'compound button condition'. This is explained in the Advanced User Guide, (P22). You basically add a condition to that assignment which will make it fire/activate only when the function knob is set to the Hdg value, which is when button 18 is set.

Once you have the heading function set-up, you then comment out the assignment lines that were added, by placing a semi-colon after the index number of the assignment. This will temporarily remove that assignment to allow you to set-up the next function (e.g. VS), which you do in a similar manner. Once all the functions have been set-up like this, and you have added compound button conditions for all the function button positions,  you then remove the semi-colon to re-activate all your assignments.


Note also, that you can use the 'Reload all buttons' button in the assignments panel to reload your FSUIPC6.ini once you have manually changes it.

John

Link to comment
Share on other sites

@Dreamflight767 Did you manage to configure your Bravo AP?

I have just configured mine, for MSFS, but it should be the same for P3D.
This is how I did it.

First, you need the following lua file: Rotaries.lua

Save that file to your FSUIPC6 installation folder. This will give the two rotaries on the Bravo fast/slow support. To use this, you need to have it auto-ran. To do this, add it to your [Auto] section of your FSUIPC6.ini, or create if not there, e.g.

[Auto] 
1=Lua Rotaries

This will convert the rotaries physical buttons to virtual buttons. With this, you don't want to see the physical button presses registered in the assignments UI. To prevent this, add the following line to your [Buttons] section of your FSUIPC6.ini file:

IgnoreThese=B.12, B.13, B.21, B.22

NB. My Bravo is assigned the letter B. If yours is different, change the letter to the one you are using.

Next, you need to add the assignments. You can use the following i.e. copy and paste to your [Buttons] section. When you have done this, you will need to adjust the index numbers (i.e. first number on each line) to make sure that they are all unique (and better consecutive). Also, you again need to change the B in the (+B,??) bit to the letter you are using.

58=CP(+B,18)64,0,C65879,0 	-{HEADING_BUG_INC}-
59=CU(+B,18)64,0,C65879,0 	-{HEADING_BUG_INC}-
60=CP(+B,18)64,1,C1025,0 	-{heading bug inc fast}-
61=CP(+B,18)64,2,C65880,0 	-{HEADING_BUG_DEC}-
62=CU(+B,18)64,2,C65880,0 	-{HEADING_BUG_DEC}-
63=CP(+B,18)64,3,C1024,0 	-{heading bug dec fast}-
64=CP(+B,16)64,0,C65897,0 	-{AP_SPD_VAR_DEC}-
65=CU(+B,16)64,0,C65897,0 	-{AP_SPD_VAR_DEC}-
66=CP(+B,16)64,1,C1020,0 	-{ap spd var dec fast}-
67=CP(+B,16)64,2,C65896,0 	-{AP_SPD_VAR_INC}-
68=CU(+B,16)64,2,C65896,0 	-{AP_SPD_VAR_INC}-
69=CP(+B,16)64,3,C1021,0 	-{ap spd var inc fast}-
70=CP(+B,17)64,0,C65662,0 	-{VOR1_OBI_DEC}-
71=CU(+B,17)64,0,C65662,0 	-{VOR1_OBI_DEC}-
72=CP(+B,17)64,1,C1026,0 	-{vor1 obi dec fast}-
73=CP(+B,17)64,2,C65663,0 	-{VOR1_OBI_INC}-
74=CU(+B,17)64,2,C65663,0 	-{VOR1_OBI_INC}-
75=CP(+B,17)64,3,C1027,0 	-{vor1 obi inc fast}-
76=CP(+B,19)64,0,C65895,0 	-{AP_VS_VAR_DEC}-
77=CU(+B,19)64,0,C65895,0 	-{AP_VS_VAR_DEC}-
78=CP(+B,19)64,1,C1022,0 	-{ap vs var dec fast}-
79=CP(+B,19)64,2,C65894,0 	-{AP_VS_VAR_INC}-
80=CU(+B,19)64,2,C65894,0 	-{AP_VS_VAR_INC}-
81=CP(+B,19)64,3,C1023,0 	-{ap vs var inc fast}-
82=CP(+B,20)64,0,C65893,0 	-{AP_ALT_VAR_DEC}-
83=CU(+B,20)64,0,C65893,0 	-{AP_ALT_VAR_DEC}-
84=CP(+B,20)64,1,C1016,0 	-{ap alt var dec fast}-
85=CP(+B,20)64,2,C65892,0 	-{AP_ALT_VAR_INC}-
86=CU(+B,20)64,2,C65892,0 	-{AP_ALT_VAR_INC}-
87=CP(+B,20)64,3,C1017,0 	-{ap alt var inc fast}-

For the trim wheel, you can also use these:

52=P64,6,Cx32000BC0,x3FFF0018 	-{offset sword increment, offset 0BC0 (Incr=24, Limit=16383)}-
53=P64,7,Cx32000BC0,x3FFF0032 	-{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}-
54=P64,4,Cx42000BC0,xC0010018 	-{offset sword decrement, offset 0BC0 (Decr=24, Limit=-16383)}-
55=P64,5,Cx42000BC0,xC0010032 	-{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}-
56=U64,7,Cx32000BC0,x3FFF0032 	-{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}-
57=U64,5,Cx42000BC0,xC0010032 	-{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}-

Hope that helps.

John

Link to comment
Share on other sites

  • 3 months later...
  • 3 months later...

Sorry to bother you but this is not working for me.  I'm a newbie to MSFS and to MSUIPC but I think I followed the instructions carefully:

1) downloaded the attached rotaries.lua file and put it in the C:\FSUIPC7 folder

2) Added this to the INI file:

[Auto]
1=Lua Rotaries

3) Made the other recommended changes to FSUIPC7.INI file.  e.g. The "assignments" monitor shows my yoke has the letter "C" so I edited the code accordingly.

4) Exited and restarted FSUIPC with monitoring enabled, including Lua monitoring, and MSFS is also running.

However looking at the log I don't see the rotaries.lua file being loaded.  Also when I operate controls on the Bravo no events are logged and when I look at controllers in available in MSFS the Bravo itself is still shown and I don't see FSUIPC listed as a controller.  I assumed that the Bravo would not appear and it's events should be being routed through FSUIPC.

What did I do wrong?

One thing I notice is that [Auto] contains the name "Lua Rotaries", as recommended, but the auto detected name in [LuaFiles] is "Rotaries"  i.e. different.

[Auto]
1=Lua Rotaries

[LuaFiles]
1=Rotaries

I tried changing "Lua Rotaries" to Rotaries in [Auto] to match the file name but this did not help.

What am I overlooking?

FSUIPC7.ini

Edited by chrisgr99
Punctuation
Link to comment
Share on other sites

5 minutes ago, chrisgr99 said:

Sorry to bother you but this is not working for me.

What isn't working - all the assignments or just the trim wheel ones?

6 minutes ago, chrisgr99 said:

One thing I notice is that [Auto] contains the name "Lua Rotaries", as recommended, but the auto detected name in [LuaFiles] is "Rotaries"  i.e. different.

[Auto]
1=Lua Rotaries

[LuaFiles]
1=Rotaries

This is correct, as documented. 

7 minutes ago, chrisgr99 said:

What am I overlooking?

I don't know. What aircraft are you using? Maybe the trim control doesn't work for that aircraft? Have you tried in a different aircraft?

For any issues, logging is your friend. Try activating logging for Buttons & Keys, Events and also Lua Plugins. You can see what is being logged as it happens by opening the log console (Log->Open Console). You can post/attach  your log here and I can take a look.

John

Link to comment
Share on other sites

I didn't realize an aircraft needed be be active for events to be generated by the controller.  I activated the Cessna 152 and the Bravo is controlling it.  However the simulated trim wheel moves very slowly - takes about 40 turns of the physical wheel to move the sim wheel a full rotation - from stop to stop.  Is it possible to speed it up more?

Link to comment
Share on other sites

First apologies for the late reply - missed your post, sorry.

On 2/11/2022 at 12:34 AM, chrisgr99 said:

However the simulated trim wheel moves very slowly - takes about 40 turns of the physical wheel to move the sim wheel a full rotation - from stop to stop.  Is it possible to speed it up more?

Of course. If you look at your ini, you can see that you currently have a delta of 24 set for the slow inc/dec buttons (on press only), and 50 on fast inc/dec buttons (on press and release):

Quote

52=P64,6,Cx32000BC0,x3FFF0018     -{offset sword increment, offset 0BC0 (Incr=24, Limit=16383)}-
53=P64,7,Cx32000BC0,x3FFF0032     -{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}-
54=P64,4,Cx42000BC0,xC0010018     -{offset sword decrement, offset 0BC0 (Decr=24, Limit=-16383)}-
55=P64,5,Cx42000BC0,xC0010032     -{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}-
56=U64,7,Cx32000BC0,x3FFF0032     -{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}-
57=U64,5,Cx42000BC0,xC0010032     -{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}-
 

Just increase that delta. You do this in the buttons assignment panel - open that and turn your trim wheel and you will see the details of the assignment (you may need to Ignore the slow buttons to see the fast buttons). Otherwise, you can change the hex values of those inc/dec values durectly in the ini (I have highlighted them above0. Best to do this without FSUIPC7 running - if it is running, make sure the Button assignment panel is open and click the Reload button after making changes.

John

Link to comment
Share on other sites

Hey John,

Sorry to tagalong in this post, but I'm also having issues with the rotary knobs on my honeycomb bravo TQ. I've followed your directions from you 7/8 post, and my increase/decrease rotary knob is only recognized in one direction (decrease). I'm unable to get it to increase the hdg/IAS/ALT values. Any idea what I might be doing wrong?

I cant include my log file as its ~3 megabytes and the post wont allow that size attachment. 

(FSUIPC 7.2.15, registered, trying to use MSFS2020 default a320n)

Link to comment
Share on other sites

43 minutes ago, Mugg21B said:

I've followed your directions from you 7/8 post, and my increase/decrease rotary knob is only recognized in one direction (decrease).

What exactly do you mean by this? If you open the Button & Switches assignment panel, do you only see the buttons registered on one direction and not the other? What button numbers do you see in the Btn# field when you rotate fast/slow in each direction?

48 minutes ago, Mugg21B said:

I cant include my log file as its ~3 megabytes and the post wont allow that size attachment. 

Why is it so large? You can generate a smaller one, and it also zips up pretty well, so try that. Make sure that you only have logging enabled for Buttons & Keys and Lua Plugins. Also, please change set the LogActivity variable in the Rotaries.lua to true.

Then generate a log file, zip it and attach it here, together with your FSUIPC ini file.

John

Link to comment
Share on other sites

22 hours ago, John Dowson said:

What exactly do you mean by this? If you open the Button & Switches assignment panel, do you only see the buttons registered on one direction and not the other? What button numbers do you see in the Btn# field when you rotate fast/slow in each direction?

Why is it so large? You can generate a smaller one, and it also zips up pretty well, so try that. Make sure that you only have logging enabled for Buttons & Keys and Lua Plugins. Also, please change set the LogActivity variable in the Rotaries.lua to true.

Then generate a log file, zip it and attach it here, together with your FSUIPC ini file.

John

Not sure what was going on that increased my log file size yesterday, i dont seem to have that issue today. edit: nevermind, its back - maybe something to do when I run FSUIPC while the game is running?

So my left rotary seems to be registering in the buttons & switches panel, in both directions. The right rotary briefly popped up as joy #64 and in the box where it says "choose the action for this button..." it told me something about it being a compound button and needed to be edited in fsuipc.ini. However that was only one time out of 10 that it even showed up - most up the time, the right rotary is not registering in buttons & switches assignment panel. 

Quote

 815250 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
   815250 LUA.4: Local: time = 167643234
   815250 LUA.6: Local: Time = 167643234
   815265 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815265 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:54
   815265 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:73
   815281 LUA.4: Global: CurrentData = 
   815281 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815296 LUA.5: Waiting for an event in "C:\FSUIPC7\hidBravoButtons.lua"
   815296 LUA.5: Timer event: calling "Poll" in "C:\FSUIPC7\hidBravoButtons.lua"
   815296 LUA.4: Global: n = 0
   815296 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:46
   815312 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815312 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815312 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815312 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:69
   815312 LUA.5: Local: time = 167643296
   815328 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:54
   815328 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:73
   815328 LUA.6: Local: Time = 167643312
   815343 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815343 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
   815359 LUA.4: Waiting for an event in "C:\FSUIPC7\hidAlphaButtons.lua"
   815359 LUA.4: Timer event: calling "Poll" in "C:\FSUIPC7\hidAlphaButtons.lua"
   815359 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:46
   815359 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:73
   815359 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815375 LUA.4: Local: time = 167643359
   815390 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815390 LUA.5: Waiting for an event in "C:\FSUIPC7\hidBravoButtons.lua"
   815390 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:54
   815390 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815390 LUA.5: Timer event: calling "Poll" in "C:\FSUIPC7\hidBravoButtons.lua"
   815390 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815390 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:46
   815406 LUA.6: Local: Time = 167643390
   815406 LUA.5: Local: time = 167643390
   815406 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:69
   815421 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:54
   815421 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815421 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:73
   815437 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815437 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
   815453 LUA.4: Waiting for an event in "C:\FSUIPC7\hidAlphaButtons.lua"
   815453 LUA.4: Timer event: calling "Poll" in "C:\FSUIPC7\hidAlphaButtons.lua"
   815453 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:46
   815453 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:73
   815468 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815468 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815468 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815468 LUA.4: Local: time = 167643453
   815484 LUA.5: Waiting for an event in "C:\FSUIPC7\hidBravoButtons.lua"
   815484 LUA.5: Timer event: calling "Poll" in "C:\FSUIPC7\hidBravoButtons.lua"
   815484 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:54
   815484 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:46
   815484 LUA.6: Local: Time = 167643468
   815500 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815500 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:69
   815500 LUA.5: Local: time = 167643484
   815515 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:54
   815515 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:73
   815515 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815531 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
   815531 LUA.4: Waiting for an event in "C:\FSUIPC7\hidAlphaButtons.lua"
   815531 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815531 LUA.4: Timer event: calling "Poll" in "C:\FSUIPC7\hidAlphaButtons.lua"
   815531 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815531 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:46
   815531 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815531 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:73
   815546 LUA.6: Local: Time = 167643531
   815546 LUA.4: Local: time = 167643531
   815562 LUA.5: Waiting for an event in "C:\FSUIPC7\hidBravoButtons.lua"
   815562 LUA.5: Timer event: calling "Poll" in "C:\FSUIPC7\hidBravoButtons.lua"
   815562 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:54
   815562 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815562 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:46
   815578 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:69
   815578 LUA.5: Local: time = 167643562
   815578 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815593 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:54
   815593 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:73
   815609 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815609 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815609 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815609 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
   815625 LUA.4: Waiting for an event in "C:\FSUIPC7\hidAlphaButtons.lua"
   815625 LUA.4: Timer event: calling "Poll" in "C:\FSUIPC7\hidAlphaButtons.lua"
   815625 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:46
   815625 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:73
   815625 LUA.6: Local: Time = 167643609
   815640 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815640 LUA.4: Local: time = 167643625
   815656 LUA.5: Waiting for an event in "C:\FSUIPC7\hidBravoButtons.lua"
   815656 LUA.5: Timer event: calling "Poll" in "C:\FSUIPC7\hidBravoButtons.lua"
   815656 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:54
   815656 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:46
   815656 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815671 LUA.5: Local: time = 167643656
   815671 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:69
   815687 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815687 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815687 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:54
   815687 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815687 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:73
   815703 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
   815703 LUA.6: Local: Time = 167643687
   815718 LUA.4: Waiting for an event in "C:\FSUIPC7\hidAlphaButtons.lua"
   815718 LUA.4: Timer event: calling "Poll" in "C:\FSUIPC7\hidAlphaButtons.lua"
   815718 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815718 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:46
   815718 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:73
   815734 LUA.4: Local: time = 167643718
   815734 LUA.6: C:\FSUIPC7\Rotaries.lua:133
   815750 LUA.5: Waiting for an event in "C:\FSUIPC7\hidBravoButtons.lua"
   815750 LUA.5: Timer event: calling "Poll" in "C:\FSUIPC7\hidBravoButtons.lua"
   815750 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:54
   815750 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:46
   815765 LUA.6: Waiting for an event in "C:\FSUIPC7\Rotaries.lua"
   815765 LUA.6: Timer event: calling "poll" in "C:\FSUIPC7\Rotaries.lua"
   815765 LUA.6: C:\FSUIPC7\Rotaries.lua:49
   815765 LUA.5: Local: time = 167643750
   815765 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:69
   815781 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:54
   815781 LUA.6: Local: Time = 167643765
   815781 LUA.4: C:\FSUIPC7\hidAlphaButtons.lua:73
   815796 LUA.6: C:\FSUIPC7\Rotaries.lua:51
   815796 LUA.5: C:\FSUIPC7\hidBravoButtons.lua:69
 

This is a bit from my log file that gets too large to share, maybe there's something helpful there? 

FSUIPC7_prev.log FSUIPC7.ini

Edited by Mugg21B
added portion of log file
Link to comment
Share on other sites

Why are you using the hidAlphaButtons and hidBravoButtons lua scripts? These were initially useful to access the buttons with numbers > 31, but have not been needed since FSUIPC was updated to recognise up to 128 buttons, in v7.1.0 back in May 2021. I think you should remove those luas, and update the assignments you were using (on the virtual flags used by those scripts) to assignments to the actual button number.

If you do that, you should be ok, as it seems like the issue is that both the Alpha lua script and the rotaries script are using the same offset/virtual flags (at offset 0x3340).
If you want to continue using the Alpha/Bravo luas (although I recommend not to), you need to update the Rotaries.lua to use the next virtual device, which will be at offset 0x3348 (the alpha script uses 0x3340 and the Bravo 0x3344), i.e. change line 61 to:
                 offset = 0x3348
That will be virtual joystick 66, so you would also need to change all your rotary assignments from virtual device 64 to use 66 instead.

John

 

Link to comment
Share on other sites

23 hours ago, John Dowson said:

Why are you using the hidAlphaButtons and hidBravoButtons lua scripts? These were initially useful to access the buttons with numbers > 31, but have not been needed since FSUIPC was updated to recognise up to 128 buttons, in v7.1.0 back in May 2021. I think you should remove those luas, and update the assignments you were using (on the virtual flags used by those scripts) to assignments to the actual button number.

If you do that, you should be ok, as it seems like the issue is that both the Alpha lua script and the rotaries script are using the same offset/virtual flags (at offset 0x3340).
If you want to continue using the Alpha/Bravo luas (although I recommend not to), you need to update the Rotaries.lua to use the next virtual device, which will be at offset 0x3348 (the alpha script uses 0x3340 and the Bravo 0x3344), i.e. change line 61 to:
                 offset = 0x3348
That will be virtual joystick 66, so you would also need to change all your rotary assignments from virtual device 64 to use 66 instead.

John

 

I thought I had to, but that was based on information from another post that I now understand was outdated. I reset my .ini and removed all the luas except for the rotaries. The ALT/VS/HDG/CRS/IAS rotary now is logged when I switch between the settings, however the INC/DEC rotary does not log any presses and does not affect the values in MSFS2020. Any thoughts? 

FSUIPC7.log FSUIPC7.ini

Link to comment
Share on other sites

30 minutes ago, Mugg21B said:

I reset my .ini and removed all the luas except for the rotaries.

You still have some assignments to the virtual buttons used by the Bravo lua script:

Quote

20=P65,4,C67225,0     -{WINDSHIELD_DEICE_ON}-
21=P65,3,C67226,0     -{WINDSHIELD_DEICE_OFF}-
22=P65,5,C66073,0     -{PITOT_HEAT_OFF}-
23=P65,6,C66072,0     -{PITOT_HEAT_ON}-
24=P65,7,C66976,0     -{CABIN_LIGHTS_OFF}-
25=P65,8,C66975,0     -{CABIN_LIGHTS_ON}-

You should delete this and re-assign to the actual button numbers if you want to use them.

34 minutes ago, Mugg21B said:

The ALT/VS/HDG/CRS/IAS rotary now is logged when I switch between the settings, however the INC/DEC rotary does not log any presses and does not affect the values in MSFS2020. Any thoughts? 

Did you have an aircraft loaded and ready-to-fly? Luas are only started once in this state (well, 5 seconds after, or longer, depending upon the value WASM ini parameter LvarScanDelay which has a default value of 5 seconds). I can't really tell what is happening from the log you attached as it is a continuation log file (i.e. you selected 'New Log' from the logging menu). Always attach a full log when you need support - there is information at the beginning (and end) that I need to see to diagnose issues correctly.

Also, did you activate logging in the Rotaries.lua as I advised if you have issues?
 

On 2/14/2022 at 12:57 PM, John Dowson said:

Also, please change set the LogActivity variable in the Rotaries.lua to true.

If not, and you still have issues, please do that and show me your full log file. The log file you attached has no lua logging so I can only assume it wasn't running for some reason.

John

Link to comment
Share on other sites

22 hours ago, John Dowson said:

You still have some assignments to the virtual buttons used by the Bravo lua script:

You should delete this and re-assign to the actual button numbers if you want to use them.

Did you have an aircraft loaded and ready-to-fly? Luas are only started once in this state (well, 5 seconds after, or longer, depending upon the value WASM ini parameter LvarScanDelay which has a default value of 5 seconds). I can't really tell what is happening from the log you attached as it is a continuation log file (i.e. you selected 'New Log' from the logging menu). Always attach a full log when you need support - there is information at the beginning (and end) that I need to see to diagnose issues correctly.

Also, did you activate logging in the Rotaries.lua as I advised if you have issues?
 

If not, and you still have issues, please do that and show me your full log file. The log file you attached has no lua logging so I can only assume it wasn't running for some reason.

John

Keys reassigned. I was using a rotaries.lua provided in the fsuipc7 documents folder and it didnt have the logactivity variable, so I downloaded the one you provided in this thread. It's set to true now.

Still having issues even after being loaded in an aircraft and powered up. Left rotary appears to work as it's logged, right rotary is MIA in the log file and has no affect on values of the left rotary. 

The forum is telling me I am limited to a 1.8 kB file to attach and the log is 94 kB so here is a google drive link to it - i think this is the full log https://drive.google.com/file/d/1Pyw5rQ2DCfLQgxFzfhF5qEAsJrv3ulOp/view?usp=sharing

Link to comment
Share on other sites

4 hours ago, Mugg21B said:

The forum is telling me I am limited to a 1.8 kB file to attach and the log is 94 kB so here is a google drive link to it - i think this is the full log https://drive.google.com/file/d/1Pyw5rQ2DCfLQgxFzfhF5qEAsJrv3ulOp/view?usp=sharing

Try zipping the file and attaching. I cannot access from that link.

John

Link to comment
Share on other sites

4 hours ago, Mugg21B said:

I was using a rotaries.lua provided in the fsuipc7 documents folder and it didnt have the logactivity variable, so I downloaded the one you provided in this thread. It's set to true now.

The one in the documents folder is an older general one. I customised this specifically for the Bravo rotary, which is the one in this thread. I should have renamed it to BravoRotary.lua really, I guess...sorry about that.

John

Link to comment
Share on other sites

Can you also temporarily remove the lua (just rename it to Rotaries.lua.off) and see what button numbers you see in the button assignments window when you turn your rotary in both directions. You should see 12 in one direction, 13 in the other.  If you don't see those, your rotary button isn't working.
 

Link to comment
Share on other sites

17 hours ago, John Dowson said:

Can you also temporarily remove the lua (just rename it to Rotaries.lua.off) and see what button numbers you see in the button assignments window when you turn your rotary in both directions. You should see 12 in one direction, 13 in the other.  If you don't see those, your rotary button isn't working.

You also need to (temporarily) remove this line from the [Buttons] section of your FSUIPC7.ini file to see those buttons:
    IgnoreThese=C.12, C.13, C.21, C.22
Sorry for not mentioning that earlier.

Link to comment
Share on other sites

I can see 12 and 13 with the rotary button turning. I still can't get the file small enough to upload here. However, I found that even though I shared the link with you I didn't change the permissions to allow others to view the file. It's fixed now so you should be able to view it. https://drive.google.com/file/d/1Pyw5rQ2DCfLQgxFzfhF5qEAsJrv3ulOp/view?usp=sharing If that doesn't work, I also zipped it and you can get it here - https://drive.google.com/file/d/1WF1DnD1gp6XcWnO5x-s8_EzXi5lxRI2i/view?usp=sharing

Link to comment
Share on other sites

That log file is pretty small, I am surprised that you cannot attach a zipped copy!

Looking at that log, there are no messages logged for buttons C.12 and C.13. Are you sure you pressed them (i.e. turned the rotary)?
Also, did you have an aircraft loaded and ready-to -fly? Your log indicates that the Rotaries.lua was killed about 22 seconds after it was started, most probably as you were still  in the main menu:

Quote
    54500 Lua threads being terminated:
    54500       1 = "C:\FSUIPC7\Rotaries.lua"
    54687 LUA: "C:\FSUIPC7\Rotaries.lua": killed
    54937 **** DevCom read/write threads still running - will exit anyway but could cause issues...
    70187 Sim stopped: average frame rate for last 38 secs = 44.4 fps
    70187    Max AI traffic was 0 aircraft
    70187 -------------------------------------------------------------------

Try running with the logging console open (Log-> Open Console) so you can see what is happening in real-time. Always make sure that you have an aircraft loaded and ready-to-fly when using luas, as they are only started when in this state (they can be started on MSFS start-up, but will be killed when the main menu state is detected).
For the first test, rename/disable the lua and verify that turning the rotary logs button presses for your C.12 and C.13 buttons. If these are not logged/detected, the rotaries.lua will not work. You did day you saw these in the assignments window, so I cannot see how there activation is not logged.
If they are logged, activate the lua again, turn the script logging off (set LogActivity variable to false in the script and turn off lua logging in FSUIPC) and then monitor your console again to see what happens when you turn the rotary knob.
You can also post/share the two logs and I will take a look. But please also describe what you see in the logging console, if anything, during these tests.

John

Link to comment
Share on other sites

I have found an issue that prevents lua Autos from running if the WASM is not installed and enabled. I will fix this in the next release, but for the time being please make sure that you have the WASM module installed and enabled (using the Add-ons->WASM->Enable menu item), or you can manually start your luas (e.g. on a button or key  press).

John

Link to comment
Share on other sites

35 minutes ago, John Dowson said:

I have found an issue that prevents lua Autos from running if the WASM is not installed and enabled. I will fix this in the next release, but for the time being please make sure that you have the WASM module installed and enabled (using the Add-ons->WASM->Enable menu item), or you can manually start your luas (e.g. on a button or key  press).

I have fixed this issue in the attached beta release, v7.2.17a: FSUIPC7.exe

Please download and use to replace your existing FSUIPC7.exe and test with this version.

John

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.