John Dowson

I don't know, why don't you try it? The beta license is still valid - until tomorrow! However, if its recognised as a mouse I don't think so, but see how it is recognised by FSUIPC (especially in the Joyscan.csv file).

Yes, so its a sticky button. Its in one state on one press (on_, and a different state on another press (off), so its sends a press event on first press, then a release on second (although the other way around in your log as it was already depressed). Knowing how the button works, you should program it how you want to use it, with the control sent on the press for to change to the state you want when it is depressed/on, and a control sent when it is released to change the state to the state you want when it is off.

They must be exactly as specified in your SimMarket order. Please check and try again, and if you still have an issue let me know your order number and email address and I will check it here. Sorry, but when you 'skip' don't you see a 'Completing FSUIPC7 v7.0.0 Setup' screen, with the option to create a shortcut. That message is displayed when you start the installer, in the case that you already have FSUIPC7 installed. Did you see the README.txt, and the Installation and Registration guide (in the same folder as the installer)? The documentation (including User guide) is installed under your windows Documents folder, in an FSUIPC7 sub-folder.

Sounds like you are trying to program to a "sticky button", i.e. one that sends a key press when you first press, then a release when you press it again (i.e. like an on/off.. You can test what it seeing and sending by activating logging for events and buttons & keypresses. See what that looks like and compare the events to when you control on screen using the mouse.

Ok, thanks for reporting back.

Have you tried also sending the command on the button release (2nd lower dropdown in the assignments panel) as well?

If the key file is missing, you did not click the 'Register' button. You need to do this to generate the key file, and you will get a pop-up message telling you if the license is valid or not. The offset status spreadsheet is not installed by the installer as this is a temporary document. You should manually copy it from the extracted zip folder if you want to keep it. The installer installs fsuipc in the folder you selected, which is C:\FSUIPC7 (the default location). Your install log shows that all documents were correctly installed in the right location: Are you saying the documentation isn't there? I don't know why are complaining so much. Try reading the installation and registration guide for installation and registration instructions, everything is explained there. John

Hi Gary, that was the post for the beta releases. It makes no mention of transferring licenses from P3D, and only contains license information on the time-limited licenses I provided for FSUIPC7 during the beta test phase. The last beta license I provided (available on that page) is valid until today, so will expire tomorrow.

Could you please elaborate? What do you mean by 'no longer operational'? What has this got to do with key presses?

Those controls do work on the Boing 787 - for a discussion on the use of the _SLOT_INDEX_ control, see this old post: Maybe its just not working in the A320Neo?

I have explained this so many times now - please read my previous post. Every version of FSUIPC requires a different license. Any discount for holders of other versions is clearly explained on the product sales page. @bjratchf Please let me know your order number and email address. You can PM me them if you don't want to post them publicly. Do NOT post your key.

What details are those? Licenses for FSUIPC7 only went on sale on 6th November. If you purchased a license , make sure the details are exactly as you specified. Please remember that - licenses for any other FSUIPC version (i.e. FSUIPC4, FSUIPC5, FSUIPC6) are NOT valid for FSUIPC7 - the license validator in the installer for FSUIPC7 does not validate time-limited licenses - instructions on how to add a widefs license to a time-limited license have been given many times. If you have purchased a license and have re-tried and still have issues, please let me know your order number and email address and I will check it for you. John

@speedbird144 You have three devices recognised. but two now seem to have the same id: Also one device seems to have an issue: Something else must have changed on your system. There were only a few minor cosmetic changes between the beta and the released version. Have you had a windows or driver update maybe? Can you attach your FSUIPC7.Joyscan.csv file as well as your FSUIPC7.ini. And try not to start a new log. Think I'll remove that feature! @katoema Hmm, strange. Glad its now working!

Just leave it enabled/running when you exit. The next time you start it will automatically start. Note that it starts quit late, once you've loaded an aircraft.

Strange, I don't know what would cause this. Were you trying to run directly from the zip file without extracting? You should be able to install FSUIPC7 anywhere. The registry keys it adds are just to let the installer know where to uninstall from the next time it is ran. Running the uninstaller will clear any registry keys. However, if the uninstaller is ran by the installer, it will still rememebr the previous installation locations. Not sure about that...it should do uninstall all files previously installed + the reg keys. I'm really at a loss as to why the reg checker didn't work correctly.

I'm pretty sure the latest installer is ok. However, there was an earlier version of the beta installer that did not correctly insert a registry entry with the documents location. Could you try the following please: - uninstall FSUIPC7 by double-clicking the uninstallFSUIPC7.exe (located in your installation folder). Also manually remove any documents or document folders for FSUIPC7 if any are left behind - re-install using the latest installer Then check everything is installed in the correct place. If not, post me your InstallFSUIPC7.log John

Yes of course, sorry. I don't understand why the installer is finding this file under C:\Users\David\AppData\Roaming\Microsoft Flight Simulator\UserCfg..opt - this check is returning true for you for some reason: IfFileExists "$APPDATA\Microsoft Flight Simulator\UserCfg.opt" steamInstall So its installing a steam-install bat. Very strange....

You could try Everything - its a very useful little utility for finding files. I'd like to know what's happening so I could maybe improve the installer. For the time being, if you re-install you will have to edit the .bat file each time as it will be removed and re-written.

Ok. But what is the location of your UserOpt.cfg file? Do you have them in both locations?

All versions should do that! Are you saying that the latest installer puts them directly in your C drive, rather than in the documents folder? It shouldn't....if thats the case, can you show me you InstallFSUIPC7.log file please? John

Hi Martin, No, sorry - you need to contact SimMarket. They handle all sales. John

As Pete identified, the installer thinks you are running a steam version. However, FSUIPC7 itself knows you are using an MS Store version (that's why I needed your FSUIPC7.log file!). The installer determine the installation type by the location of your MSFS UserOpt.cfg file. It first checks in the steam location, which is (for you) C:\Users\David\AppData\Roaming\Microsoft Flight Simulator\UserOpt.cfg Do you have such a file? For MSFS installs, it should be (for you): C:\Users\David\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt The latter is the one FSUIPC7 uses, so I don't understand why the installer finds the first (or what it is doing there). Did you maybe buy the steam version, return it, then buy the MS Store version instead?

No problem if you want to manually move the documentation. However, they won't be removed when you run the uninstaller so you'll have to remove them manually. And when you install an update it will re-install the documents in the Documents folder again (in a folder labeled FSUIPC7) unless you uncheck that option.

Did you read the section on 'Limitations' in the provided README.txt. If not, please do so. Key press commands do work when MSFS has the focus, but the keys received by FSUIPC7 are limited due to issues with the MSFS SDK. Hopefully things will improve in subsequent releases - current release is still 0.7.0.0. Not sure I understand what you are saying here (I'm not familiar with USBKEYS opencockpit) - how is FSUIPC involved? What is the issue with FSUIPC. If the "commands generated by USBKEYS opencockpit are not recognized" (by MSFS I presume), then isn't that an issue with USBKEYS opencockpit? Note also that there are known issues with many controls/events currently not working, again due to issues with the SDK.

Sorry, what does this mean? What do you actually see when you click the Register button?