John Dowson

@Chad P Btw, when you create a profile (not based on an existing profile) you are asked id you want to import the general axis assignments. If you say yes, then the general axis assignments are copied to a profile-specific one. If you say no, an empty profile axes section is created. Your ini shows the profile but no profile axes section, which is why you are having these issues. I cannot see how this can happen unless you manually deleted this section from the ini. If you didn't do this, have you any idea how this happened? I have tried to reproduce but can't... John

This should certainly not happen...but your FSUIPC7.ini file is rather strange. You are using an FBW profile, but have no axis section for that profile. They are probably 'disappearing' as you have the profile-specific checkbox checked and there are no axis defined for that profile. You also have your LeftBrake assigned, but not the RightBrake. Can you please try the attached FSUIPC7.ini. In this version, I have duplicated your axis assignments to your profile, as well as simplifying your profile aircraft names to a simple substring 'Airbus A320neo'. Try this ini, and add your RightBrake. You should also load another aircraft and add the RightBrake assignment to your nin0profile axis assignments, so that when you create other profiles it will get imported. I see you are also using the A320ParkBrake.lua - is that working for you? I ask as I have had reports that this is no linger working, but have not had time to look into this yet... John FSUIPC7.ini

They really shouldn't... can you show me your FSUIPC7.ini file and an FSUIPC7.log generated with logging for Buttons & Keys and Events activated - load your aircraft, press an assigned button/switch or two, then exit.

You will find that in the Utils folder of your FSUIPC7 installation. What do you mean by this? Your assignments are stored in the FSUIPC7.ini file, and possibly another .ini file under the Profiles sub-folder if using 'profiles in separate files'. If you change the installation location, you will need to copy across from your original installation folder. Bur these files are not touched when you re-install,

Also I see you are still using 7.3.8 - you need to use the latest FSUIPC7 beta, currently 7.3.9h, with SU10 - available here: John

Try the development version then... I will look at this, when I have time (i.e. maybe in a couple of days), but as FBW does not even support the development version. I doubt there is much I can do... John

If you want/need to calibrate, try assigning with 'send direct to FSUIPC7 calibration'. 7.3.9h mainly contains fixes relating to lvar/hvar discovery and loading and shouldn't affect any axes assignments (i.e. no changes there). John

Did they work in the previous version (and what was that version)? Can you try 7.3.9h (latest beta) and if you still have issues, show me your FSUIPC7.ini and FSUIPC7.log files, the latter generated with Axes Controls logging activated, load your aircraft, release the parking brake and push each toe brake through its full range, then exit FSUIPC7. As for the A320 parking brake script, I will look into that. Could it be that the toe brakes weren't working as the parking brake was set due to this issue? John

Yes, I know - it is the SU10 release / SDK 0.9.3 release that has broken certain things, and you need to review your axes assignments accordingly for the moment... What does thus mean? I need to see your FSUIPC7.log file as well as your FSUIPC7.ini to start with.... John

You are posting in a topic that is over 11 years old, and in a forum that is not for FSUIPC7. For ALL FSUIPC7 issues, please use the FSUIPC7 sub-forum. There are quite a few issues since the SU10 release, some have been fixed and others are under investigation still. I suggest you download the latest beta, available here: Is FSUIPC7 running? I am locking this topic now - for further assistance, please use the FSUIPC7 syb-forum. John

There are a few issues at the moment since the SU10 release.... How are your buttons assigned? If using lvars/hvars, then these are currently not working in 7.3.8 with SU10. There is a beta available that fixes thiis alonf with a few other issues, available here: Axis assignments don't drop, so there must be something else going on...there are various issues with axes assignments since SU10, which I am still investigating. For the time being, make sure that you have either assigned with 'send Direct to FSUIPC calibration' and have calibrated, or have assigned to 'send to FS as normal axis' but with no calibration (remove/delete if you have calibrated with this option, as that is known to cause issues). It WAS working...the SU10 release has broken many things in the SDK, especially with SimConnect. There are issues after every major SDK update. A full trial license is ALWAYS available, and I recomend that you try the software BEFORE you buy, as it says on the SimMarket sales page: As it is a digital downloaded product (with no on-line license verification), once a license is issued it cannot be revoked. This is why there are no refunds, and you are expected to try the product before purchasing to see if it is suitable for your needs. FSUIPC7 is very powerful, and essential for many home cockpit builders but it is certainly not suitable for everyone, John

Strange, but that is a problem with MSFS...you could try setting the FSUIPC7.exe compatibility property setting 'Run this program as administrator' if you are always going to run with admin privileges, Regards, John

That is correct - it is grayed-out once assigned unless you click the Clear button. Same here - most axes I have tried are working ok when assigned to 'Send direct to FSUIPC calibration' and calibrating, and also when assigning with 'Send to FS as normal axis' and removing any calibration. The only axis I have so far (haven't checked all!) found that is not working is Axis Mixture Set which always gives errors regardless. However, this is an undocumented axis in MSFS so there is not much I can do - I will probably remove this. I have been mainly working on WASM/lvar loading issues today, and have just released an updated beta 7.3.9h, so can all users with issues please update to that (see Announcements sub-forum). I will come back to looking at the axes issues tomorrow, and will review the comments again and do more testing. If you post on issues, PLEASE state which aircraft you are using, how you have assigned - either direct to calibration or send to FS as normal axis, and if using the latter please double check that you have no calibration settings as doing this no longer works. As I have mentioned before, best to check the the calibration section in the FSUIPC7.ini (either general or your profile specific section) and check that there are no entries for the axes you are using - for example, I have noticed that removing toe brake calibration can still leave zero calibration entries which currently need to be manually removed. Also maybe post your ini (and profile ini, if using) so I can check your assignments. I can test in all default aircraft and several add-ons (but by no means all!). For example, I have the JF PA28 and the throttle axis is working ok in that for me, so @Cloud8.5 must be assigning or calibrating incorrectly (show me your FSUIPC7.ini!). Until tomorrow... John

The SU10 beta has been updated with several improvements, although there are still issues with some axes controls. See the announcements for the latest betam and the following thread for SU10 axis issues: John

The latest beta release contains several improvements in the loading and availability of lvars. See John

The desktop icon is an optional feature that just displays a splash screen while MSFS is starting, nothing more. If you don't use that to start MSFS, delete it and when you run the installer, uncheck the checkbox on the final page. If you want a shortcut for starting FSUIPC, just create one. There should be no issues starting WideClient while MSFS is in the main menu, but it will/may not connect (it may sometimes though). Always wait until you have an aircraft loaded and are ready-to-fly before reporting any connection issues. As I keep telling you, you can tell when WideServer is running by the MSFS title bar. But there is really no point in starting WideClient until you have an aircraft loaded. John

Another update: FSUIPC_WAPID.dll I am also now going to release 7.3.9h....done - see Announcements.

I have not updated the WASM zip file yet as I have still not released this. Currently its available in the latest beta download, in the SDK folder, so you will need to download this to get it for now - or use the attached: FSUIPC_WAPID.dll FSUIPC_WAPID.h

There is an issue with lvars not being loaded when you restart the same flight that I am looking in at the moment...for now, you could try setting StopWAPIInMenu=No in the [General] section of your FSUIPC7.ini - but I think this also has issues in certain situations... I will post a new release once this is resolved. John

Ok, then specific to the Fenix... That is what I thought, but thanks for confirming...I tend to forget these things.... Good - should be better in the next release, without the need (or much need...I will still keep it for a while...) of the LvarScanDelay ini parameter.

Maybe Paul's dll needs to be rebuilt with the latest WAPI libs (not sure if you need to do this or just drop in the update WAPI lib or dll - ask Paul), or you need to rebuild your software using these. There have been some major changes in how the WAPi works in this release...anything that uses the WAPI will need to be recompiled with the latest libs. John

Great! That depends if I update again before release...best to wait and recompile on release just in case.

Ah, great...including the toe brakes fully functional? What about with the latest beta I posted above - can you check with that to see if that makes a difference please. John

But there is no desktop icon to start FSUIPC7 - there is only one to start MSFS...so that will be why it doesn't start. That is the connection to MSFS, not WideClient/WideServer. WideServer status is reported in the MSFS title bar when running, not in the FSUIPC7 title bar. Do you have an aircraft loaded and ready-to-fly? Sometimes WideClient is started earlier, but other times only once you have a plane loaded and ready-to-fly, so check that you are in this state - and the MSFS title bar should indicate that WideServer is running and waiting for connections, as well as your FSUIPC7.log file with the following line: The log file you posted earlier shows that WideServer was not started as you never loaded an aircraft, and you exited after 23 seconds. Please load an aircraft before you try to do anything with WideServer/WideClient, and check that WideServer is running, either from the MSFS title bar or the log.

The Axis Left/Right Brake set controls are no longer working in SU10, and as that is what the offsets use, that will be the issue. There is nothing I can do about this at the moment ecept report to Asobo/MSFS. Sorry about that. @AgniparvataThis is not quite correct....I had the parking brake set when I was testing...duh! I now do see some movement. However, it seems like the Brake Right/Left Position now go from 0-32767 and not 0-16383. I have updated for this in the attached version if you would like to try it. If you still have issues with this version, could you add FSUIPC monitoring of those offsets (0x0BC4 and 0x0BC6) and show me an FSUIPC7.log file where you apply the toe brakes. Also, please let me know what/if you are using those ini parameters, AxisCalibration set to Yes, or DirectAxesCalibs set to Yes or All? Also, check you FSUIPC7.ini and if you see any LeftBrake or RightBrake entries under your [JoystickCalibration] (or profile equivalent, if using) section then please remove those and try again - it seems that these are sometimes left even if the calibration is removed (I will look into this). John FSUIPC7.exe