John Dowson

Please check for similar issues before posting - see There is a temporary fix there which I am pretty sure should work but nobody has yet posted back. I also have a patchd version ready-to-go for this issue, but I will not release this until someone has reported if the fix works or not and provides their log and ini files so that I can check. Please use that post for this issue - I am locking this one now. John

Are you running the installer from within the zip file? You need to extract the zip first, then run the installer.

No. Older versions are not supported or available. What exactly is your issue? Have you read this post?

If you want a key or button assignment to toggle an Input Event value, the best way to achieve this is to add the Input Event to an offset, using the new [InputEventOffsets] ini parameter section, and then assign to the offset byte togglebits control,. So, to add an input event to an offset in your C510.ini profile, add the following to your C510.ini file (below using offset A000): And then assign to the FSUIPC-added control Offset Byte Togglebits with an offset value of A000 (change as needed) and a parameter of x1 (i.e. toggle first bit, to toggle between 0 and 1). See new section Adding Input Events to Offsets on page 52 of the Advanced User guide. John John

Generally yes, as that is in an offset area designated as free for general use. But you can only add it there as either a byte or word (2-bytes), and not as a double-word (4-bytes) or double floating point number (8 bytes) due to offset boundaries (i.e. the address ends in a 6, so you cannot use it for 4 or 8 byte values). As this is an enum, you can add it as an unsigned byte. Yes, but that won't wok for buttons either as the format is wrong - you have an additional/unneeded comma after the offset condition., and you have comments but no comment designator. Please consult the Advanced User guide if you have issues like this - it should be obvious if you read this. For example, on P24 of the Advanced User guide: Is that not obvious? Please always at least consult the manuals before posting, and also check/search the support forums for similar questions or issues. If you get an ERROR logged, then check your syntax against the manuals. John

The preset code here is this: i.e. it uses and lvar, not a b-var. This code was given to show a hack that you can use to introduce a l-var to control a b-var. You then use this lvar in the calc code to control the b-var in the xml code. As I said, this is a hack. You cannot directly control b-vars via calculator code.l

I am pretty sure you have ask this several times already, and I have already responded... What files are you talking about? Different files are read at different times, and when it comes to the ini file, different sections are read at different times. BUT, why not just maje it easy for yourself, and assume that everything is read when FSUIPC6 is started. So, if you want tyo change anything, exit FSUIPC7, make the change, then restart FSUIPC7. There should never be a need to restart MSFS. You can restart FSUIPC7 at any time, and it should reload pretty quickly. This really depends on the section, as different sections are read at different times. I am NOT going to go into details with this. You can use the reload buttons in the ui panels for axis, button and key assignments to reload the assignment sections. If you are not sure (or it is not documented), assume that the parameter is read only at start-up. Loaded when an aircraft matching the profile aircraft names is loaded, or when the profile is loaded and you click on one of the reload buttons in the assignments panel. The events.txt, myevents.txt (and offsets.txt) files are only read at FSUIPC7 start-up. If you want to reload them, then exit and restart FSUIPC7. John

Please also attach your FSUI{C7.log file when attaching your FFSUIPC7.ini file, as I need to see basic information, such as which aircraft you are using... Your FSUIPC7.ini file is pretty empty, and shows that you only have a few axis assigned, and only for use with one specific aircraft ('Black Square B60 Duke N43DH'): You have also assigned using 'send direct to FSUIPC calibration' but have not calibrated your assignments. If assigning with this, you should also calibrate your assignments. Please also check your MSFS assignments. If assigning in FSUIPC, you need to make sure that the same axis/button is not assigned in MSFS. Best to create an empty profile for your controllers in MSFS if assigning in FSUIPC. Any further questions/issues, please attached both your .ini and .log files, and activate logging in FSUIPC to show your issue (i.e. for problems with axis assignments, you should activate logging for Axes Controls). John

It would help if you could activate logging for Buttons & Keys, as asked for. I think you just need to give FSUIPC more time to load and initialise things. You should not attempt to do anything until MSFS and FSUIPC are fully initialised, which in your prev log is here: i.e. over 4 minutes after FSUIPC is started. The next time you think things are not loaded/not working, take a look at the log and see if those lines are logged, and if not just wait until they are. You need to be more patient. You can possibly reduce the DetectToConnectDelayAuto ini parameter so that FSUIPC tries to connect earlier, but this value has probably been arrived at via auto-tuning. You can also try activating auto-tuning again, as this parameter can be set too high if auto-tuning was performed when MSFS was updating. See the section on Auto-tuning in the Advanced User guide. Your files also show some device confusion, with devixe with id of 0 being acquired three times: This can be due to phantom xbox controller entries: Are you using such a controller? If not, then please try the attached ini file where I have corrected for this and shortened your aircraft names to use substrings. So please try this, and if any issues please explain and re-attach both your FSUIPC7.ini and FSUIPC7.log files. John FSUIPC7.ini

The community-driven effort for determining presets is let by MobiFlight, and all presets are available here: https://hubhop.mobiflight.com/presets/. I just provide the MF presets (via the events.txt file). You should use the HubHop site for all discussions/requests/ets for presets, not here.

You should have received an email with your license details, If you did not, you can raise this with SimMarket via their support service - see https://secure.simmarket.com/customerservice.php Your license details will also be available from your SimMarket account, so you can get them from there, and register them at the end of the installation process. You will not see the Assignments menu if you have not registered your license.

How do you know this? Can you please attach a log if you have issues, with logging for Buttons & Keys activated, and maybe also Events.

You either haven't given FSUIPC enough time, or the aircraft name does not match the one(s) you have in the [Profike.xxx] section of your profile. Are you using aircraft name substrings? Check your ini, and ALWAYS check your logs before posting. Note that when you first run v7.4.12 it should auto-tune the start-up parameters, but these will not take effect until the next time FSUIPC7 is auto-started. Please see the section on auto-tuning in the Advanced User guide. John

Your ini file is confusing me more... You only have ome assignment, and that is to the S axis of your HOTAS throttle. Is that the sweep lever? I thought this was a separate device.. The flaps settings make no sense: First, determine what the flap position values of the flap detents are. To do this, activate logging for Axis Events and send these to the console window. then move the flaps lever in the VC and take a note of the parameter for the Flaps Set event, or note the event being used. Then assign that lever by removing the assignment to the axis itself (you can select '(unused)'), and then set three ranges for your axis, and on entering/leaving set the values determined for the last three detents using the Flaps Set control, or use the controls logged for each detent.

Yes, as explained in my previous comment. No it cannot - that will not work. You cannot set B:vars via calculator code. That is a question for Asobo/MSFS, but I very much doubt it. SU15 is the last sim update this year. John

Why have you installed FSUIPC7 under your Documents folder: start "" "C:\Users\Al\Documents\Al's Flight Simulation\AddOns\FSUIPC7\modules\FSUIPC7.exe" "-auto2" ? Re-install in a non-windows protected folder. If using the MSFS.bat method does not work for you (and I have no idea why this would be), then switch to using the EXE.xml method in the installation process. I have no idea what this means... As I have said many times now, if FSUIPC7 does not auto-start using the MSFS.bat auto-start method, re-install and select the EXE.xml method instead. John

What do you mean by this - what is the issue? Can you please show me your FSUIPC7.log file and explain the problem. I do not provide or support earlier versions. John

I am still waiting to see a FSUIPC7.log and FSUIPC7.ini file showing this issue, when you have added IgnoreDevice=0xFFFF,0xFFFF to the [JoyNames] section of your FSUIPC7.ini file. That should be a temporary fix for this issue, and if that does not work then I need to see those files to determine why. John

What do you mean by this? If there is no Assignments menu, then you are running an unregistered version. You need to re-run the installer and enter and register your license details to generate a key file. There is no latest beta - download and install the latest version, which is 7.4.12. John

Can you show me your ini and log files for this please? That should certainly work, and something else must be going on if not...

You can be back in business now by adding that ini parameter, as suggested. I have no idea when the next release will be, but hopefully not for quite a while... John

Your log shows that FSUIPC7 attempted to reconnect many times during MSFS start-up, and that auto-tuning was active. Can you please test again next time you restart, and if you get the same issue, try restarting FSUIPC7 (i.e. exit FSUIPC7 and re-start by double-clicking the FSUIPC7.exe file in windows explorer). Also, please activate logging for Buttons & Keys, and re-attach a new log if still having issues. John

Aggh, : I added a new facility to allow a device to be ignored, and when this is not used it defaults to using a device with product and vendor ids of 0000, which is what your Fulcrum One Yoke has registered with (for some reason...!). I am not sure why your device hasn't given a non-null vendor/product id, but FSUIPC still should not ignore this. I will correct this in the next update, but for now please add IgnoreDevice=0xFFFF,0xFFFF to the [JoyNames] section of your FSUIPC7.ini file. This will then ignore that device rather than defaulting to the vendor/product values of your Yoke. Sorry about that. John

If there is no icon in the system tray or task bar, then it will not be running. Does Alt+F open the FSUIPC7 main window? If not, then it is not running. Note that you need to use the MSFS.bat file or the Desktop MSFS link (created by the FSUIPC7 installer) to start MSFS if using the MSFS.bat auto-start method. If this is not working, I have no idea why - the bat file simply starts MSFS, waits for 95 seconds, and then starts FSUIPC7. If this is not working, I do not know why. Re-install and go back to the EXE.xml auto-start method - in the components installation page, open the auto-start options, de-select or uncheck the MSFS.bat method (first option) and select / check the EXE.xml method. John

No, it is not broken. Have you read the above? Are you using the Desktop MSFS icon installed by the FSUIPC7 installer to start MSFS? If not, that is why FSUIPC7 is not being auto-started. If you are using that, and you are leaving the bat file running (i.e. not closing/killing it by closing the console window that is created) then FSUIPC7 will be started. If you are not using the Desktop MSFS link, then FSUIPC7 will NOT be started. Re-install and when you get to the components screen, open the auto-start options, deselect the MSFS.bat auto-start method and select the EXE.xml auto-start method. There is no problem to solve. You should update and decide which auto-start method you want to use and then use that. John