John Dowson

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

Sorry about this - this version was extensively tested by me and other users, and I am not sure why there is an issue with so many users for this relatively minor change. I have rolled back this now, so can you please all try this version: FSUIPC7.exe You can change this to the value that suits your needs - those are just the defaults. Note however that this will affect all button assignments. John

Can you please refrain from adding screenshots, especially from 3rd party apps. These are useless to me. I am only interested in seeing your FSUIPC7.log file for this issue, nothing else. Also please attach this file, not screenshots, and do this AFTER exiting FSUIPC7. Can someone/anyone add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x800 And then show me/attach an FSYUPC7.ini file showing this issue. Can you also indicate if you are using a registered/licensed copy of FSUIPC7 or not (although if you attached your log file, this would tell me). I must admit that I did not test this version with the unregistered version before release, but I have just tested this here and all seems fine. If you get this issue with an unregistered/unlicensed version, can you please download the trial license (available from a post at the top of this sub-forum) and try with that to see if you get the same issue - and let me know the results please. John P.S. Also please select/load and aircraft and get ready-to-fly and wait a minute or so before exiting FSUIPC7 and attaching your log file. And also attach your FSUIPC7.ini file.

What trouble? The image you attached is nothing to do with FSUIPC7 - that just shows that vaMSYS cannot connect - whatever that is.... Is FSUIPC7 running? How was it started - via auto-start or manually? Did you see the FSUIPC7 splash screen? Try manually starting FSUIPC7 and see if it runs - you will see am FSUIPC7 splash screen and then there will be an icon in your system tray. If not, show me/attach your InstallFSUIPC7.log file. If it is running you can attach your FSUIPC7.log file and I can check for errors there., but the issue will be with your FSUIPC7 client and you need support from them.

The offsets were monitored in the FSUIPC7.log file, but not in the FSUIPC7_prev.log file. And although these offsets were monitored in the 2nd log file, the values never changed from 0. This is because you have not activated the additional FSUIPC offsets for PMDG - can you do this please. Instructions are in the Offset Mapping for PMDG 737-700.pdf document. The only suspicious event I can see in both log files is this: This is a "Spoilers down" control. Do you know where this is coming from? Can you repeat again with the PMDG offsets enabled, and also check the spoilers position as well as the state of the stab controls in the VC.

Ok, but I don't know much about SIOC (never used it), and nothing about .ssi files. They are certainly not anything that FSUIPC would recognise - I suspect they are specific to SIOC. And yes, it is my understanding thar SIOC uses FSUIPC offsets. With such cards, you would usually assign in SIOC to FSUIPC offsets. FSUIPC only recognises HID joystick type cintrollers natively, and you can maybe use lua for other non-joystick type HID conytollers. This is not related to the flight model you are using or how that is configured. There have already been several support requests in using usbkey cards with FSUIPC. Check these posts to see if they help - search this forum for usbkeys. John

Clear your browser cache, or download from http://fsuipc.com/ - both places download the same installer file, and it is 7.4.3.... John