John Dowson

👍

Note when using this script, the virtual buttons will not be seen in the button assignments panel. This is because the event.offset and event.button functions are not called when the buttons assignment panel is open. Therefore, to assign to the virtual buttons, you should first assign to the physical buttons and then edit your FSUIPC7.ini to manually change the assignments to the virtual buttons (including duplicating the physical button assignment to create two virtual button assignments and changing the control for the fast/slow movement). For an alternative solution that uses polling and so the virtual buttons can be seen on the assignments panel, together with examples on how to assign to the virtual buttons for the different functions of the selector knob, see John

@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 FSUIPC7.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

As well as what Blake has said, before you fo that, check that the gear control offset at 0BE8 is showing the correct value (again, by logging). If it is, you can do as Blake says, with the dowsides of this approach. If offset 0BE8 is not showing the correct gear position, you are out of luck.

You don't need to make any changes any more as Blake has already updated the scripts so this is not necessary (and that is also why the line numbers have changed). Check that offset 060C is populated correctly for the aircraft that you are using, i.e. shows 1 (for retractable). You can do this using the offset logging facilities (as UB).

Glad you got it working (even if that is using P3D assignments and not FSUIPC!). One thing: It is included, if you selected to install the documentation when you installed FSUIPC6. The FSUIPC6 documentation should be in a sub-folder of your Windows Documents folder, called FSUIPC6. If they are not there, you should check your InstallFSUIPC6.log file to see if they were installed and where. John

For the cutoff/idle levers, you can try assigning to the Mixture Lean (or Mixrure1 Lean) and Mixture Rich (or Mixture1 Rich) controls for cutoff and idle respectively.

Not surprising as there is only one assignment in that ini file: 0=1S,256,F,66818,0,0,0 -{ TO SIM: STEERING_SET }- You have nothing else assigned/ Have you tried actually assigning anything to your devices?

This is not correct - the installer will never replace or remove your ini file - this would cause chaos/sever problems....! As I said, you either installed into a different folder, or you manually deleted your ini or your assignments. If you didn't manually remove or delete the ini, you must have installed in a different folder. Try searching your system (e.g. try with Everything or something similar) for your old/original FSUIPC6.ini file.

As Pete says, you don't have any assignments in FSUIPC apart from those 2 that Pete mentioned. You do have controllers activated in P3D, so are you sure your assignments aren't there (you should de-activate controllers in P3D if assigning in FSUIPC). Could you possibly have installed 6.1.2 in a different location to 6.1.1? Of so, your original 6.1.1 ini should still be in the old folder. Ifthats the case, copy ot toyour new installation folder and try again (and post your new FSUIPC6.ini and updated FSUIPC67.log file if you have any issues). John

Not on our side. Maybe @cellular55could comment if he has heard anything from VRInsight....

Ir looks like your Joy ids have changed. Can you please also attach your FSUIPC6.ini file.

Sounds like some hidden characters have made its way into the script. Try downloading it again. or looking at the file in an editor that can show hidden characters/symbols (e.g. Notepad++) and remove them. 341 does refer to the line number. It is strange that it reports the error for multiple lines - maybe there are multiple hidden characters. Line 341 is also just a comment - you could try just removing that line....

@yvesb It looks like the LvarScanDelay WASM ini parameter had no effect, regardless of what this was set to. I have now corrected this in the attached (beta) release. Could you please try this as I think if this is working then there should be no need to have a regular automatic re-scanning of lvars. The lvarScanDelay parameter is also now in seconds (rather than milliseconds), with a max value of 120. There are also some other corrections for when using lvars, such as not auto-starting luas or macros until the lvars have been loaded. Install_FSUIPC7.2.2c.zip John NB. If you have problems downloading from that link, try right-clicking and selecting 'Save as...'.

It is strange that this issue started after a P3D update, but I really can't see how that can affect something like event.button, which is completely independent of P3D (i.e. P3D is not involved at all). Anyway, try activating the suggested logging, as this may show you something when this happens again - i.e. if the button presses are received, and if anything is picked up by your lua scripts. Cheers, Joihn

It is recognised but did you add it to the [Auto] section of your FSUIPC7.ini file so that it is automatically started? See the Advanced User Guide if you don't know how to do this. I'm also not familiar with FSUIPC3 (and it is no longer supported!). You can add logging, and maybe check the offsets being used are compatible, as @Blake Buhlig suggests,

This information is in the offset status spreadsheet (included in the downloadable zip file for FSUIPC7), which should be used in conhunction with the older FSUIPC Offset status document (which contains the descriptive text). I have heard of some folks using MSFS for the visuals only, but I have no idea how this is done, sorry.

Hi Reinhard. this seems rather strange. I don't understand how a P3D or windows update could affect the lua event handling. There was no change in the FSUIPC6 version you were using, no? Its also strange that is affecting both event.offset and event.button functions. Are you sure that you luas are actually still running when this occurs? Maybe you can activate logging for buttons and keys, as well as lua plugins (but not Lua plugins separately), and show me the log file produced when your issue occurs. John

Sorry, this is not true - I was thinking of FSUIPC7/MSFS - please ignore this! 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

@Tom87 Done.

If/when MSFS crashes, it usually generates faults like this in FSUIPC7 as the simconnect connection is no longer available. In such cases, FSUIPC7 will also exit, as the option 'Exit with FS' is set (and always set if FSUIPC7 is auto-started by MSFS). Check your FSUIPC7.log file, it should show that FSUIPC7 closed down gracefully as MSFS was no longer detected. If this is the case, then you should report the CTD to Asobo, including the crash event log. If/when FSUIPC7 does actually crash, the FSUIPC7.log will be cut short, i.e. no close-down messages logged. However, if this happens it should not affect MSFS as that is in a separate process.

This is usually due to having the document already open somewhere - the installer can't replace the document as its being used. Make sure that the document is closed, and then re-run the installer. If that is not the issue, then please show me your InstallFSUIPC7.log file, if there is one. John

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

Hi Mario, could you try the attached version please, v7.2.2b: FSUIPC7.exe Thanks, John

Could you please attach your FSUIPC7.log file created after the CTD. Also check the event log to see if there was an MSFS crash reported before the FSUIPC one. Thanks, John