John Dowson

You can still use the letters and assign to that flag. Did you try? You can disable joyletters completely but I wouldn't recommend it, especially if you have assignments to those letters. Could you maybe explain in a bit more detail what you are trying to achieve, What are you assigning the button to? Or are you doing something in lua?

Did you try unchecking the 'Exclude THROTTLEn_SET' on page 3 of the calibration page, and then reverse the axis there for Throttle 1 and Throtttle2? You can still calibrate in FSUIPC when sending to the FS, but this may result in multiple values being received by the sim (due to priority levels). I don't have the FSLA320, you you need to check this. You could also try assigning direct to FSUIPC calibration and to Throttle 1 and Throttle 2 and calibrate in FSUIPC. Otherwise, check that you have 'No reverse zone' checked in the individual throttle calibration screen as this would reduce the available range if unchecked. Also maybe try assigning to the Axis Throttle n Set controls (under 'Send to FS as normal axis) instead.

Your log is very strange: This shows: - letter 'A' (65) pressed, followed by - letter 'S' (83), followed by - '2' key (50) There is no log of a ctrl+shift+ e key combination. Could you tell me what you pressed to produce this log? If it wasn't those keys, then something is seriously wrong.... You do have a TOGGLE_AIRCRAFT_EXIT being sent. This must come from P3D (not FSUIPC7) - did you send this from the UI, or do you have an assignment to the 'A' or 'S' key in P3D? Could you produce another log file for me. Change the TimeForSelect back to 4 before you test please. Attach you log and ini files after the test, and also provide a brief description if what you did (i.e. keys pressed). If you did press ctrl+shift+e in your original test, there may be some memory corruption somewhere. This can be caused by a corrupt weather file - you could try adding NoWeatherAtAll=Yes to the [General] section of your ini file to disable weather for the time being. Could you also try a default aircraft (e.g. Lockheed Martin HC-130H), and test the doors in that. Thanks, John

The problem with the Alpha turned out to be a missing cable, but this doesn't apply to the Bravo. Can you see any buttons/switches at all on the Bravo, i.e. those with numbers < 32? If you run the windows game controller panel, can you see any buttons highlighted there? What are the button numbers shown in the MSFS controllers description dialog (where it shows a picture of your device and the button numbers for each switch) - that should show the button numbers for those < 32. Also check that you don't have power management enabled for that device - and maybe try a different USB port.

Ah, found the problem! You need to connect the short curled ethernet cable (included) from the yoke to the base: see https://forums.x-plane.org/index.php?/forums/topic/205495-switches-not-working-on-the-honeycomb-yoke/ After connecting this, everything works as it should. Do you have that cable connected? John

You shouldn't need the Alpha software installed.... I also cannot see those buttons in the Windows game controller panel. They should show as buttons 1-12 but aren't. I am not sure why. I am going to ask on Honeycomb support. John

I've just plugged in my Alpha and get the same. However I don't think this is to do with buttons in the >32 range. I can see the virtual buttons for those when I switch the starter rotary to Left, Both or Start, and get virtual device 64 with buttons 0,1 & 2 respectively. So the script is working for the buttons > 32. The issues seems to be that the buttons/switches on the yoke, with button numbers 1-12 (according to MSFS) aren't recognised. They are also not recognised in the default Alpha profile for MSFS. I didn't install any Alpha drivers or software yet. Did you? I am going to try that now..... John

Your log does show some button state changes for those buttons: Are those not shown in the button assignments panel? I as only suggesting going back to the default MSFS profile temporarily for the Alpha to see if MSFS recognised the buttons > 32. You should really create a new empty profile for this device if/when assigning in FSUIPC. So you are using the MSFS default settings now for the Alpha? Don't you get issues with the 'always on' switches, as reported by many alpha users?

It shouldn't matter where MSFS is installed. I have had reports that for some users, the auto-start via the EXE.xml only works when installed a maximum of one folder deep from the drive letter, but his is only one level deep and doesn't work, whereas your is several folders deep and does. Strange.... I am really at a loss as to why this isn't working for some users. Do you have different install types (MS Store vs Steam), or the same? Maybe try changing the order of the <Launch.Addon> entries in his EXE.xml file, to see if that makes a difference. Otherwise, I don't know what else to advise. They can try going back to the old method of starting FSUIPC7 from the MSFS.bat file. Instructions on using this method are explained earlier in this topic.

Can you show me your FSUIPC5.ini file as well please. Also, activate logging for buttons & keys as well as events (non-axis controls) and produce another log file showing you trying the various open door controls. And also close down P3D before attaching the log so I can see the complete log file. Did this value stay as 0 when you set it, or did it revert back? I ask as a user with the same issue in this thread said that this change got reverted.

Please use the attached key file. Just place it in your FSUIPC7 installation folder. Note that time-limited licenses do not validate in the installer registration page, but there is no need to register once you have a key file. The license is valid until 18th March 2021. John FSUIPC7.key

As well as what Pete has said, if you want to try the registered facilities, then you need a separate license for FSUIPC7 which can be purchased from SimMarket. You should try it before purchasing to make sure that it is still something you need. I am just about to post a time-limited license in the topic, which you can download and try: John

It is - I really don't understand why those button state changes aren't being recognised. You could try the HIDScanner program - see If you leave it running and activate your buttons, it should log what it sees. Do you see any button state changes for the buttons > 32 using that? You could maybe also try using vjoyoffsets with vjoy, and mapping the buttons to the virtual button offsets using that, to see if that helps (available from same link above).

Joyletters are active by default in FSUIPC7. To identify the joy number from the letter, just take a look at the [JoyNames] section in your FSUIPC7.INI which holds the letter to joy id mapping. John

No, this is not possible I'm afraid. They are not. There is a lua interface for those who want to try lua programming, but that is just one of the features that registration provides. Buy why start with that? Start with the User manual. And I have alrteady told you what to try for the transponder - assign to 'Offset Byte Set' (right hand side of button assignments, after selecting to send an FS control) and enter offset 0x0B46 and the parameter for the mode that you want to set. I'm sorry, but you should have reviewed the documentation before purchase. I also provide time-limited licenses for people to try the registered features before purchasing. I see Pete has also replied....

No. Why hijack this thread for an un-related product? Please post in the FeelThere support forums: https://forum.simflight.com/forum/171-airplanes/ This forum is for FSUIPC support only.

...and I have 3 or 4 similar threads on the go at the moment, and I do get confused as I am saying the same thing, so sorry if I confused your thread. I do not have the time to re-read each thread with each post unfortunately, I do what I can.....

I'm sorry you feel that way, but I cannot help if you do not provide me with the information I need. I really don't know what I said to upset you, I am only trying to help. There are obviously issues with your install. But you can still run and use FSUIPC. And download documentation for the time being. And we can sort out your installation issues, if you have the patience and provide me with the information I need to help you, and follow my advice. Please re-run the installer, but de-select the auto-start component and see if that works. And then send me your installation log, or tell me what the installer did. ...and let me know what install type you have - steam vs MS Store vs Boxed?

First thing tomorrow now....

You can get into issue using other peoples ini files if you don\t know what you are doing, i.e. an expert in the format and functionality of the various ini sections and how they are related. And the set-up of a throttle is very dependent on the aircraft you are using, which you don't even mention. There are also sections in the FSUIPC user manuals on how to set-up and calibrate devices for default aircraft. Have you tried following these? What FS and version of FSUIPC are you using? Do you really expect any help with such a general question and without any relevant information?

You are hijacking a topic not related to your issue, so I doubt you will get a response. If you think this is an FSUIPC issue, please create another topic, but also please supply more information and show us your files (log and ini to start with). But, as you issue seems more related to a specific add-on, so best to try the support forums for that aircraft first. John

Not 100% sure what you mean, but I'm happy when a user solves their own problem 🙂👍

Ok, thanks. It was just a test to see if they were actually registering somewhere else as a button press, which it seems they are. Yes, but the device is recognised (in the lua), but the issue is that it is not picking up the button state changes for some reason. There is also another current topic open for the exact same issue but for the Alpha. Presumably you can see the buttons < 32 and assign to them as usual, no? And Axes assignments are ok? The log file you attached is interesting. There is a discarded state change for each subsequent update, so it looks like it may have flagged momentarily and then rest, and the changes discarded. Maybe try increasing the poll rate to see if this is the case.

That's an FSUIPC7 log file which just tells me that you ran FSUIPC7 once (and was still running or had crashed when you pasted that log fragment). In the zip file you downloaded, as well as the installer there were two documents, a README.txt and and Installation and Registration pdf. Please read (or at least take a look) at those documents. Also, the install log file will be in the folder with those documents, where you extracted and ran the installer. Please check that. The install log is also copied to your FSUIPC7 installation folder. If its not there, I can only think that it is a permissions issue. However, as it can put other files there, this is very strange. Also, if you are installing in a windows protected folder, please try installing somewhere else. Or is 'C:\FSUIPC7\' your actual install location? If so, that is good and shouldn't cause issues. Also, when you run FSUIPC7, you do know that it sits in your system icon folder? If you run it and can't see anything, look there - or use the default hot-key (ALT + F) to show the FSUIPC main window. This is all explained in the documentation. If, for some reason the documentation hasn't been installed, download it from the download secrion of this forum (for the time being) and I'll check your installation log file once posted. John

One small thing...you don't need to, and shouldn't, edit or change the [LuaFiles] section in the FSUIPC ini file. This is auto-generated and managed by FSUIPC. You can get into issues if you manually change this section, so best not to. If you drop in a new lua, better to restart FSUIPC to get this added, or maybe one of the reload functions (from button/axes assignments dialog) will do this, not sure without checking.