John Dowson

Then read this thread and you will see a version attached above that fixes this issue....

No limit that I am aware of (but I can check this tomorrow). If you change the order of starting the programs, it is always the last one that fails to connect? And this was fine until a dew months ago? Can you remember the last FSUIPC7 version number when they all connected?

Try this version - no need to wait until tomorrow.... FSUIPC7.exe

I think I know what the issue is - I will post and updated version for you to try tomorrow. John

It would also be useful if the first log showed the reduced climb rate, as is usual, the aircraft recovers the climb rate when FSUIPC is stopped, and the second log shows the climb rate reducing again. Try not to touch the controls after the restart. The second log would then show the elevator trim and spoiler positions on start-up, and if these change as the climb rate reduces, and we can then see the controls that are causing this and hopefully determine where they are coming from.... John

First, can you add DontLogThese=67030,67038,67039,67040,67227 to the [Profile.B737PMDG] section of your FSUIPC7.ini - this will prevent the LIGHT_POTENTIOMETER_SET and LIGHT_POTENTIOMETER__*_SET events from being logged, which are of no interest and are filling your log files. Okay, but this is strange as the controls logged are for spoilers down, not up... The offset logging shows that both offsets 6C3C (TRIM_StabTrimMainElecSw_NORMAL) and 6C3D (TRIM_StabTrimAutoPilotSw_NORMAL) held a value of 1 both before and after the restart, and the other two offsets never changed value from 0. Did you not get the STAB OUT OF YTIM warning on this flight? It seems not, so this was another red herring... Ok, so you think that it is the elevator trim that is causing this issue? We did monitor the elevator trim offsets in a previous test and the values, and therefore the elevator trim settings, were the same values just before you stopped FSUIPC and when you restarted, so it looked like the trim hadn't changed, so I am confused now... I cannot tell the trim setting (not logged!), but these are the control stand trim wheel controls (678), and show a 'mouse move' (03) action: The controls being sent before the restart were these: 984844 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 67803 (0x000108db) ROTOR_BRAKE These are also from the control stand wheel trim...also logged when you restart. 985672 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 200703 (0x00030fff) ROTOR_BRAKE This is a control to hide/show the captain's yoke. Not sure why there are so many of these... Spoiler/speed brake controls are here: So it looks like the speed brake is/was in the down position when you stopped FSUIPC.... So it looks like we are back to it being either the elevator trim or the spoilers/speed brake that is causing a decreased climb rate. Can you monito/check those settings both before you exit FSUIPC and again when you restart. Maybe also add offset logging back for these: 0BC0 as S16 (Elevator Trim Pct) 2EA0 as FLT64 (Elevator Trim Position) 0BD0 as U32 (Spoilers Handle Position) I will also ask Pete about this to see if he has any ideas... John

How is SmartCars3 recording these hours? i.e. what offsets is it using? I cannot hep with SmartCars3, only FSUIPC...

As I said, for any issues you need to use logging to determine what is happening. Log the offset as U8, and also activate logging for Events and Buttons & Keys, and show me/attach your FSUIPC .log and .ini files. Again, I would need to see your files with appropriate logging activated to see what is happening.

As you are using FSUIPC7, please use the FSUIPC7 / MSFS support sub-forum, not the main support sub-forum. I have moved your post. What exactly is your issue? What does 'UPSVAC issue logging hours' mean, and what is UPSVAC? The log file you attached looks fine and shows no issues. I have no idea what you mean by 'it never recorded hours even though all other data was corrected'. If it is UPSVAC that is doing this recording, you need to talk to them. If this is based on data in FSUIPC7 offsets and you think there is a problem with these offsets, then I need to know what offsets it is using, and you can add monitoring on those offsets using the logging facilities provided by FSUIPC. And what did they say about your issue? I cannot help with your problem as I have no idea what it is. Please explain, but I think you would be better going back to UPSVAC support... John

👍

The offset is 0B63, not 063B, and a parameter of 2 will only clear bit 1 (2 = 2^1). To clear all three bits (0, 1 and 2), you need a parameter of 2^0+2^1+2^2 which is 7. Any issues, try logging the contents of that offset to see the value before and after you send the command. John

Glad you found a solution. As you found, the COM offsets at 0x034E and 0x311A and do/can not support frequencies to 3 decimal places. and you need to use offsets 0x05C4 & 0x05CC instead for 8.33Khz spacing. I am not sure why offsets 0x05C4 - 0x05D00 are documented as not writeable though. These weren't working in earlier releases of MSFS but I am pretty sure they are working now, and are using the newer KEY_COM_RADIO_SET_HZ and similar controls. I will update the documentation. John

You log file shows that FSUIPC7 was running normally with no issues. Make sure that your client program is running at the same privilege level as FSUIPC7, otherwise it won't connect. If that is not your issue, then you will need support from the client vendor. I cannot really help you with client issues if FSUIPC7 is functioning correctly. John

Maybe the nvidia driver is grabbing this key combination, as it is a hot-key, and FSUIPC is not seeing it for this reason. Try assigning to another key with lalt, then edit your FSUIPC7.ini and change the key code of the assignment to an F1 (112). Do this with the button assignments panel open, and then press to reload all button. For example, if I assign a button to lalt+P I will see this in my button assignments section of my ini: Changing this to: changes the assignment to lalt+F1. Don't worry about the comment - that will get updated by FSUIPC. John

It is not there unless you manually check this option, or add it to the ini yourself. When FSUIPC7 detects a new version, it sets this flag (internally) and will always open on start-up until you update, but this is not saved to your ini, so once updated it will start-up iconized to your system tray as usual. John

available now...sorry about that! John

Then you are still using 7.4.4a, the beta. I released 7.4.4 a short time ago, so you should update to this version. Oops, sorry - forgot to update the string version - I will correct. You will need to download and install again in a few minutes....

Then you are still using 7.4.4a, the beta. I released 7.4.4 a short time ago, so you should update to this version.

As this issue seems to be affecting lots of people, I have now released 7.4.4 - please update to this version before posting for any issues. If downloading from the download links section of this forum and you still get the previous version, please clear your browser cache. Alternatively, download from http://fsuipc.com/ John

Then there was no point in your post as the issue was already reported, confirmed and fixed... It will be when released - the version above is 7.4.4a, i.e. the first beta for the 7.4.4 release. Thanks @bob34 for posting the files I asked for, and to @Crosswind59 for testing the update version.

Which "new" version? Did you try the fix for this in the updated version available in my post above?

There is an issue with 7.4.3 that is affecting a lot of people - I have already posted a fix for this in a new version available here:

You should be able to assign to lalt+F1 and/or ralt+F1, i.e. there is a distinction between left and right alt keys. Is this due to the alt (left or right) or the F1 key? i.e. if you just press F1 is that recognised? Are the alt keys recognised with any other key presses?

It wasn't you. This option is set automatically when a new version of FSUIPC7 is available. You need to update to prevent the window opening on start-up.

Please try this version: FSUIPC7.exe If that doesn't fix your issue, please show me/attach your FSUIPC7.log and FSUIPC7.ini files. John