John Dowson

That and anything else - did you install ANYTHING from honeycomb with your Alpha/Bravo? If so, remove for the time being. Have you looked at the User guide? We provide extensive documentation so that we don't have to answer such questions. Please read the documentation, try things out, and report back IF you have issues. And I have already told you where to start: Yes, but you aren't using profiles. Why don't you actually try to create a profile and start assigning to it? But if they are working in P3D and you havbe no assignments in FSUIPC (except for throttle 1-4) then you must have them assigned elsewhere, either in P3D or in the Honeycomb config tool. You really need to decide where you want to assign. If you want to assign in FSUIPC, we recommend disabling controllers in P3D, and you should not use the Honeycomb configurator or any other software from honeycomb, at least initially when wetting things up. And, as I have already said, if you have any issues, I need to also see your FSUIPC6.log file, with relevant logging added showing your issue. But I would advise you to start by at least reviewing the User Guide.

You are using an old (unsupported) version of FSUIPC6. Please update to the latest (supported) version, v6.1.1. And try the attached FSUIPC6.ini file: fsuipc6.ini You have multiple devices of the same name and I am not sure which is which. If they are the wrong way around, try swapping the assigned letters (in your [JoyNames] section. section) - with FSUIPC closed.

I'll take a look in detail tomorrow, but why are you reading the offset? Your function and event call are wrong: Try with: Well, that shouldn't happen! You should try again and if you get issues report them. Best to set logging for the WAPI and WASM to Debug and attach your FSUIPC7.log and FSUIPC_WASM.log files of/when reporting issues. Where is this from? Its not in the log you attached. Maybe try monitoring 0x0818 as both a U32 and a FLT32. It would be helpful if I can see that in the full log, together with your updated ini. That really shouldn't be necessary. Your log shows the script start ok the first time: Anyway, there has been a couple of changes in management oif lua events in 7.2, so please download and try that and report back first, and I'll take a look in more detail over the weekend.

You should monitor as a FLT32, not U32. ipc.readFLT is correct. I don't know why you are getting that value, it does seem strange. I will take a look (probably tomorrow now though), but would be useful if you could attach your FSUIPC7.log file showing the issue, together with your FSUIPC7.ini file and your lua script. You should maybe also try the latest FSUIPC7 beta, available here: John

The installation of the MSFS.bat file is not logged in the installer. Do you not have an MSFS link (to the batch file) on your desktop?

First, you should have made sure that you are using the "Joyletters" facility before doing this....Did you? Also, you still need to install FSUIPC6 on the new system, not just copy across. After it is installed, you can then copy across the contents of your old FSUIPC6 folder. It is usual for joy ids and GUIDs to change when moving to a new PC (and sometimes with windows upgrades), but these things are easily handled if using JoyLetters. If not, still possible but it will be more work. But I cannot advise without seeing your files - I need to see at least a current FSUIPC6.ini and FSUIPC6.log file to advise further.

If you manually changed the bat file to start other add-ons and want to get back your specific copy, then check your windows Recycle Bin. It should be there (unless you have configured to empty automatically). But its really not a good idea to start programs from the .bat file. You should either use the MSFS EXE.xml, to have programs started by MSFS, or use the FSUIPC facility for starting external programs - see section 'Programs: facilities to load and run additional programs' in the Advanced user guide, P40.

If you re-install it should be there - unless you unchecked the box in the final page of the installation process that installs this. Note that the batch file is a template and is created with your specific installation details, so its not something you can copy unless you also update. But, if the installation process succeeded, it should be there. Try re-installing and make sure you install the desktop icon. If it isn't installing, I need to see yout InstallFSUIPC7.log file.

The old MSFS.bat file started MSFS, showed a splash screen for 30 seconds or so while MSFS was loading, and then started FSUIPC7. For many months/releases now, the way FSUIPC7 is started has changed. It is now started automatically by MSFS using the EXE.xml. If it is not starting automatically for you, there can be various reasons for this. I am not going to explain this again (as I have already done this hundreds of times....) - I suggest you take a look at the included README.txt and Installation manual. Then, if your answers are not there, check the this support forum for similar posts on auto-starting FSUIPC7 with MSFS, there are many.... Then, if you are still stuck, post details of your issue and include your InstallFSUIPC7.log file. Note that if you still want to use the old method of starting FSUIPC7, from the MSFS.bat file, you can still do this. Open the MSFS.bat file in an editor and find these lines: (the folder, highlighted in bold, may be different for you) To re-enable that method, just remove the comments, i.e. for me it would be: But you really shouldn't be doing this. It is far better to have FSUIPC7 auto-started by MSFS using the EXE.xml, which is now the default install option.

Before anything else, please download and try the latest (and only) supported version, v4.976: http://fsuipc.simflight.com/beta/FSUIPC4.zip Also make sure, if not using a steam version, that your FSX is up-to-date with the SP! and SP2 patches (SP! available from https://flyawaysimulation.com/downloads/files/1950/microsoft-flight-simulator-x-service-pack-1/, SP2 from https://www.microsoft.com/en-us/download/details.aspx?id=8986).

You posted in the User Contributions section, where it explicitly states NOT for support requests. I have moved your post to the correct support forum. You are also using an old unsupported version of FSUIPC6. Please update to the latest supported version, v6.1.1. This will also give you firect access to the buttons on the Alpha and Bravo that are outside of the 32 button limit. Also, please activate the "Joyletters" facility. This will assign letters to your devices and make your assignments more resilient to device id changes. Yo do this, just change the following ini parameter in your [JoyNames] section from No to Yes, and then run FSUIPC6/P3d at least once: This is described in the User Guide, P22. Also check that you have no assignments in P3D (or better, disable controllers in P3D), and if assigning in FSUIPC6, make sure that you haven't installed any of the Honeycomb drivers or software. One you have done that, try calibrating your throttles. The FSUIPC6.ini you posted shows only 4 throttle axis assignments, assigned 'Direct to FSUIPC calibration', but you haven't calibrated. If you assign to FSUIPC calibration then you MUST calibrate. Please see the FSUIPC User manual, the section entitled 'The Easy Step-by-Step Way to Calibrate Your Controls' on P42. Yes - change to use JoyLetters, as advised. Note that you can also continue to use your Saitek X52 if you like, it shouldn't be a problem. I currently have my Alpha/Bravo connected to my development machine, where I also have an X-55 throttle and stick ()as well as quite a few other devices, used for development/testing). After doing all that, if you still have issues, please show me your latest FSUIPC6.ini file as well as your FSUIPC6.log file - it helps to see them both together. Also, if it is axis that you are having problems with, you should activate logging for Axes Controls before you generate a log to attach, so I can see what is going on.

Ok, but if using lua, just use lua (i.e. send your controls from lua) rather than lua to flag virtual buttons. And for "fast" press/releases, it is better to send the desired control on both, as well as increasing the delta. You can also temporarily increase the FastTimeLimit (as well as the delta) as you receive fast presses, to prevent the odd 'slow' press being registered. Anyway, it would be interesting to see what you eventually come up with, if you could share it. It may be useful for others. I'll also be looking into this further, to configure my Bravo at some point. Still got to figure out how to mount it on my flight rig though, as its pretty bulky compared to my old saitek one. Would be interesting to know how you get along with that, but sounds like quite a major undertaking.... I've also heard that they are in short supply, with no more available until October at the earliest. Good luck! Please post again to let me know how you get on, and the solution you end up with.

Sorry, I don't understand this. Please show me your InstallFSUIPC6.log file. Are you using the same installation folder for both v4 and v5, or separate folders? If you use the same folder, both v4 and v5v will use the same configuration (i.e. only one FSUIPC6.ini) and therefore cannot be any different. If you use different folders, you will have two InstallFSUIPC6.log files - attach them both please. Also, please confirm that you are looking at the correct 'installation' folder. If you don't know where this is, the best way to verify is to go to the FSUIPC logging tab and click the 'Open Folder' button. Do this on both v4b and v5.

The link should be fine, but quite a few people have reported the links on SimMarket not woeking for some reason. Try a righ-click and select 'Save as...'.

@Blake Buhlig Just took a look at this. Seems each 'click' on the bravo rotary is a press and release, but even the timings between these near simultaneous events seems to be a minimum of 60-80ms, so I don't think its possible to get more than 8-10 presses per second (even when PollInterval is set to 1, which is what I used for testing). Of course, you can use releases as well. Attached is a short lua script that will log fast/slow for the Bravo trim wheel and adjustment rotary, which gives logs the following: Here's the script if interested: RotariesEvent.lua It also requires socket.lua: socket.lua I'll take a look at using the com library at some point, but I don't think it will be any faster... John Later: one other thing you can try is to increase the increment/decrement (delta) value on successive 'fast' clicks, so the delta increases the more fast clicks received, and reset the (fast) delta on the next slow button press

Sorry, ignore that - it was in the package downloaded from that link provided. And yes, it does seem to just work by adding the socket.lua to your FSUIPC installation folder. I will update the FAQ entry accordingly. Thanks, John

Hi Emile, first, sorry for the delay with this, but I would like to clarify this now.... Do you have a link to the socket.lua you refer to (or attach if allowed)? I can only find this and there is no socket.lua: http://files.luaforge.net/releases/luasocket/luasocket/luasocket-2.0.2 Thanks, John Later: the LuaSocket project page at LuaForge seems to be down or gone...

@Nenad Bogojevic Looks like a problem with the build of the last version I posted. Here's one I tested - max characters allowed is 255 (or 256 with terminating \0):FSUIPC7.exe Also contains a minor update to change the value parameter when creating an lvar from a dword to a double. There's also a corresponding update to the WASM for this, but the latest published one will still work Ok.

The transponder setting is held in offset 0354, in 2-byte BCD format. So you can assign a button or key press to the FSUIPC added control Offset Word Set, giving 0354 as the offset value and 0x1200 as the parameter. John

Ok, very strange, but glad its now working.

Are you sure its not running? The installer performs a simple check to find the process FSUIPC7.exe, and if found will display a message and abort. I can't see how this check can fail - and it hasn't changed or been an issue since release....Sis you check in the windows Task manager?

@Nenad BogojevicCould you try the attached build please. Not sure why its crashing when using more than 255 characters, but I've added a check for this now. Sorry, still now working, looking into it...

It does kill and re-run the script. However, the size and position information is only used the first time the script is ran, then on subsequent runs the size & position is taken from your FSUIPC7.ini file, from your [ExtWindow] section. So, to get the new size/position, you must delete the entry for that window in that section first. Alternatively, Ext windows can be moved and re-sized manually, using the arrow keys to move and the same keys but with either the alt or ctrl modifier to resize, and the updated size/position will also be recorded in your ini file. Or you can modify the size / position directly in the ini file.

Ok, good to know it works, but it shouldn't crash when the limit is exceeded - I'll fix that and log a message when the limit is exceeded. Do you think 256 chars (well, 255 + a terminator) is enough? I could easily extend further (up to 8k, the max size held in a Client Data Area).

Have you actually tested with a calc code string > 64 characters? The limit I have currently set for this is 256 characters (and this can be increased relatively easily, but would require an update of the WASM module to handle), so maybe I was mistaken with the lua limit. I will check this - tomorrow though....