John Dowson

You are probably triggering the same virtual buttons in each script - each DWORD (32 bits) from offset 0x3340 represents one "joystick". So, for a second joystick, start at offset 0x3344. John

@Juxpax Glad you figured it out. Yes, the information is spread about a bit and difficult to find. It would be good to create a FAQ entry for the Honeycomb Alpha I think, as well as the Bravo. I'll look into this in the new year, when time permits. John

Once the window has been created, it saves its size and position in the FSUIPC7.ini file - look for the following line in the [ExtWindow] section and remove it: Asking for inout: test=[444,146,346,102] Note that you can manually move and resize the display window by selecting it and then using the arrow keys, with Ctrl switching between move and resize. They can be be anywhere. Yes, this is a bug that was picked-up recently. I will correct this in the next release so that a single evemt.cancel() call will cancel all events registered on that function. Yes, thats a typo (as well as 'inout' in the name of the window created). I will correct and replace the uploaded file. John

That, of course, shouldn't happen. Most probably a problem in the lua script. I will look into this, but I'm afraid it will have to wait for the new year now. One question, did you change this line: If not, try that first. Yes, the lua can support up to 256 buttons. Maybe take a look at the original lua (HidDemo.lua, in the lua examples zip in your FSUIPC documents folder). If you compare that to 32-39 lua file you are using, you should be able to see what changes I made to restrict to those numbers and then change to handle the button numbers you need. John

Have you installed any Saitek software or drivers for your device? If so, uninstall them and try again. If you still have issues, please post again and attach you FSUIPC4.log and FSUIPC4.ini files - as well as the FSUIPC4.Joyscan.csv file if its there (although I'm not sure this is created with FSUIPC4). However, I don't know what you mean by 'Mouse Button' - is this a button on your X52? What does this have to do with a 'mouse'? John

Ok - good to know. Thanks for reporting back, John

Could you please add the following to the [General] section of your FSUIPC4.ini file please: Debug=Please LogExtras=x200000 This will add extra details to the registry/joystick scan. Start FSX and then exit and post your new log. Could you also let me know the exact version of Windows you are using please - i.e. also attach the output of the winver command. Thanks, John

I see you have now created a specific topic for this question: I will respond there, once I have taken a look to see what is happening. This may take a few days though as I am supposed to be on holiday (until the 4th).... John

Please see the Advanced User Guide as this is explained there at the bottom of page 22: Please try for yourself, and if you then have any problems, post again with what you have tried. John

This shouldn't be the case. If you have correctly added the ProvideAIdata=No to the correct place, you should see the following informational message logged near the beginning of your FSUIPC7.log file, after the device scan log: 641 ### Note: AI Traffic related facilities and data are inhibited! and there should be no other log messages relating to the number of AI traffic. Can you check again please, and if you see such a message can you post your FSUIPC7.log and .,ini files and I'll take a look. John

@ark1320 You can try the attached lua script and adjust as needed. It pops up a window asking for a number, terminated by an enter/return key. It just logs the number entered. John askTest.lua

Yes, the easiest way to do this is to just create a new profile for each of your controllers as new profiles are empty. It all depends on how you want to set things up, and can also depend upon which aircraft you are using, but generally its something in between. Currently there are quite a few controls/events that aren't working via the SDK (e.g. to control views), and there are also quite a lot of controls available in MSFS that have not been exposed via SimConnect, and so are currently not available directly via FSUIPC. There is no problem mixing-and-matching assignments between MSFS and FSUIPC7, but just make sure that you are only assigning each axis and/or button/switch in only one place. For controls that are available in MSFS but not exposed via the SDK, you can assign a key press to this in MSFS and then assign a button/switch to that key press in FSUIPC7. This is how I control my views, for example. So, my advice would be to create empty profiles for your controllers initially and try to assign using FSUIPC7, but where you need to either assign to a key press in MSFS and then to that key press in FSUIPC, or assign directly in MSFS. John

Which products did you update? It may help others that are also affected by this issue. John

Hi Gary, no, sorry - the discount is only for holders of FSUIPC5/6. John

Hi Emilio, Sorry, I have no idea. Is the 'OnFSUIPCChange' function from the the SC-Pascal SDK? If that is the function that isn't working as expected, you need to contact the author of that for assistance. John

To recognise buttons outside of the 0-31 range, you have to use lua. There is a lua script provided called HidDemo.lua (in the lua examples zip in your documentation folder). Add that to your FSUIPC7 installation folder, and edit to provide your devices vendor and product ids. Also, auto-start the lua by adding it to the [Auto] section of your FSUIPC7.ini file. There are many posts on how to do this - try checking the forums if you require further help before posting again. John

What version of FSUIPC7 are you using? Current version is v7.0.3. The Alt modifier was reenabled in v7.0.2 so should be available. Key combinations are only possible in FSUIPC key assignments with the modifier keys Alt, Shift & Ctrl. Ok, thanks. Just register with your new key details during the installation process. This will re-write your FSUIPC7.key file. John

If its not there, add it, if its there with 'Yes', change to 'No'. It goes in the [General] section. John

There is already the option ProvideAIdata=No Maybe you can try with that to see if it makes a difference? John

Can you check your FSUIPC7.log file. You should see these lines near the beginning: If you don't see that, you are either using the wrong file or have placed it in the wrong place. Under the Assignments menu. this will not be available if your FSUIPC7 is unregistered. Yes, there is a know issue with both the Honeycomb Alpha yoke and the Bravo throttle, with certain switches always sending state.... There are quite a few honeycomb users using FSUIPC7 to get around this, so should be possible. Just see you have responded again and now have it working....good lucjk with setting it up! Still waiting for my Honeycomb Alpha.... John

These errors have been known to be caused by the number of SimConnect clients being exceeded. Its a known problem in all ESP based sims since FSX. To verify if this is the cause, you could activate server-side SimConnect logging (via a SimConnect.ini file) to see if the number of clients/connections is being exceeded, and if so increase the maximum number of clients available via your SimConnect.xml file. John

As Pete says, just use the same FSUIPC7.key file. However, if its failing validation it could be due to your VC++ redistributables. Can you try to see if you can actually run FSUIPC7 on your 2nd PC (registered or not)?

Maybe that could work, although you would have to terminate the event.key function on an enter or return key press. Are there any standard lua library functions that can get keyboard input? I tried with io.read but this doesn't seem to get any input. I'll take a look using event.key for this in the next few days. John

No problem - sorry for the late reply as I took a few days off over christmas... Would be useful to other users who have the same issue if you could also post your solution to your problem... Thank, John

The saitek mode switch on the X52 uses three buttons which you can check with offset conditions. See this post: John