John Dowson

Hi Achoriham, ok, was just checking how you were reloading, as there are currently know issues with FLT files saved via SimConnect (i.e. autosave files). I just checked a few times saving/loading flights via MSFS, and haven't experienced any issues. Can you download the latest release and try again please, just to make sure that you are up-to-date. Then, if you still have the issue, can you try disconnecting and re-connecting to see if that helps. You could also try activating axes logging and moving your controls to see if these are being logged/sent.

First, you posted in the FAQ sub-forum, where it explicitly states 'Answers to Frequently Asked Questions.. NOT for support requests.'. I have moved your post to the FSUIPC7 as you are asking about FS2020 (or MSFS). FSUIPC7 has an optional add-on WebSocket server component, integrated and included in the installer, provided by Paul Henty, which uses his client dll for .net to communicate to FSUIPC. Details can be found here: http://fsuipcwebsockets.paulhenty.com/ This component will also work with other versions of FSUIPC and so with other sims (P3D, FSX, FSX-SE).

The log is a continuation log and shows nothing. Please send me a full log, do not start a new one. You also seem to be getting a lot of FUEL SELECTOR events for whatever aircraft you loaded. These aren't of interest - you can add this line to the [General] section of your FSUIPC7.ini to prevent these being logged: DontLogThese=65962,66523 Press some keys when FSUIPC7 has the focus first, then switch focus to MSFS and press some other keys. Try standard letters initially, to see if you are getting anything at all.

Hi Dave, no, not seen anything as of yet from Asobo regarding the weather, other than what has been said previously (they're looking into it). John

Different aircraft seem to continually log various events like this. This used to be a problem with add-on aircraft in P3D, where unused events are re-purposed for internal use. With MSFS, they seem to do this with many of the included aircraft. Those events are being used, but I do not know what the aircraft is using them for! If you don't want to see such events, you can use the DontLogThese ini parameter (in the [General] section) - please see the Advanced User guide for details. I think I need to allow this parameter to also be profile specific. I'll look into this. Well, that's because you can't see the events! Its not FSUIPC that's sending these, its only logging them. John

Can you go to Log -> Custom, and enter x400. Then generate a short log file where you reload and have your issue. Also try manually disconnecting and re-connecting after the reload. Attach you logs and I'll take a look when I have time, but even if there is an issue it is very minor with a simple workaround (ie. restarting FSUIPC7). John Later: Ah, sorry - misread your post. The problem is now with reloading a flight, not when you resync. What do you mean by 'reloading a flight' - how are you doing this?

You can use the offset directly. as Thomas has suggested, or you can use the Parking Brakes control, and then add an offset condition for offset 0x0BC8. Offset conditions are described in the Advanced User guide. John

I've just checked these and they should be fine. Are these assignments working for you when MSFS has the focus? They should work when both MSFS has the focus, and when FSUIPC7 has the focus (but not when neither have the focus). If not, enable logging for Buttons & Keys, then press those keys when MSFS has the focus and send me the log and I'll take a look. John

Ok Al, I'll keep in on my 'todo' list and let you know when I get a chance to look at this in detail. John

There are various issues with receiving keys via SimConnect when MSFS has the focus. Please check the MSFS SDK documentation if you want to see what keys are working (although even in this, the numpad keys don't work!). Looking at your assignments, the ones you have to normal keys (D, E, Z, Q, T) should work - have you tried these when MSFS has the focus? For numpad keys, MSFS only sends these when numlock is off (when it should send them when numlock is on). Please see this thread for this: I'm not sure why your F1-F7 aren't working - these should be ok according to the documentation. I'll take a look (when time permits), and look into it or raise with Asobo if this is an issue with MSFS. FYI, this is the current MSFS documentation on key inputs, upon which FSUIPC7 relies to receive these from MSFS:

But what exactly is your issue? If you can explain it rather than saying "FSUIPC works only when he has the focus" then maybe I can help. What exactly are you trying to do/achieve? No, this is not possible and if it was it would cause many issues!

Sorry, what do you mean? FSUIPC "works" without focus. The only functionality that may be different when FSUIPC7 has focus compared to when MSFS has focus is in the key assignments area, and this is due to lack of support (in the MFS SDK) for various keys, and a bug in the numpad keys where they are only sent when numlock is off (when it should be when numlock is on). If thats your issue, then there are already various support requests on this issue (and this has been reported to Asobo). For all other functionality, the focus is not important. Why do you think it is? What is your actual issue? John

Thinking about this further, I'm not sure if this is needed or helpful as it only applies when on the ground (if you were thinking that this could be used for a 2nd calibration when flying at slow speeds). Also, the MaxSteerSpeed is already configurable for different profiles, and you can probably achieve the calibration you require by playing around with this parameter - from the Advanced User Guide: Given this, do you still think that this would be a useful addition?

@HeLord You have posted in a topic (and forum) for FSUIPC7 for MSFS, not for FSUIPC6 and P3Dv5. Can you please post in the main forum for FSUIPC6 support, and attach your FSUIPC6.ini and .log files please. I will delete your post in this topic shortly. John Later: may also be worth reading this (even though its a bit old nbow): https://forums.flightsimlabs.com/index.php?/topic/8145-tuning-the-brakes/ If I understand the gist of that discussion, it seems that FSUIPC calibration doesn't play well with the FSLabs for toe brakes, and you should try 'direct to FS' and calibrate yuor brakes in the FSLabs config files....It may be worth asking over on the FSLabs forums.

Don't the active/standby frequencies swap in the offsets when you do a Com Stnby Radio Swap? What do you see in the BCD offset 0x034E for COM1 /VHF1 active frequency? This is a well used offset and I doubt very much that there is an issue with this in FSUIPC, so I think it must be due to either your PMDG or mobiflight config, neither of which I am familiar with unfortunately. I know PMDG like to do there own thing, but if the COM2 offsets and the COM1 standby are all ok, it is surprising that the COM! active is faulty. I did read somewhere that the comms can be disabled in the FMC when using PMDG - maybe you can check if you have SIM COMMS DISABLED in the FMC? Not sure if this is relevant: https://www.avsim.com/forums/topic/460188-activate-atc/ John

@Terry Kulp Sorry, but I have no idea what you are talking about or asking. FSUIPC does not read or write "spreadsheets". There is a spreadsheet provided, which is a temporary document giving the status of the FSUIPC offsets for MSFS, in lieu of the FSUIPC offset document being updated for this FS. Please also note that you have posted in a thread that has been dead for over 17 years! And if you have questions relating to FSUIPC7-beta/MSFS, then you should use the specific sub-forum for that. John

Ok, I'll look into this when I have time. Note however, the steering tiller axis only takes affect when the aircraft is on the ground.

Can you check the main support forum to see if a similar issue has been reported there. If not, please raise a new post there, in the main forum (this is a sub-forum for FSUIPC7 only), with an appropriate title and both you installation log and fsuipc4.log file, if there is one.

If I read this from a user-specified offset, then you could have a simple lua to write the max steer speed needed to that offset. The lua could then also read whatever offset it likes to base this value on, and also take a fraction or apply any other type of calibration, also updating when the aircraft changes.

Possibly. But what do you mean by "fraction"? I could determine the speed from one of the "stall speed" offsets, 0x0538 or 0x0540, or maybe from a user-defined offset? How would you like this determined? I'm pretty busy at the moment but will take a look when I get a chance.

Hi Charles, FSUIPC7 is for MSFS, the latest FS from Microsoft, not for FSX. For FSX, you need FSUIPC4. See the downloads section, or over on www.fsuipc.com. Note that I think you need to have at least applied the service packs to your FSX otherwise the installer may bail. John

Did you calibrate? Steering tiller calibration is on screen 9 of the calibration screens. Then click 'Set' and calibrate! No, I wouldn't do that. I'm not actually sure what that is....! I'll check the code for that. John

Hi Al, you can assign your rudder axis to the steering tiller in the FSUIPC assignments panel (together with the rudder) - you can assign up to 4 axes controls to any one axis. The steering tiller is actually am FSUIPC-added axis that uses the rudder control, but allows a separate calibration in FSUIPC's calibration page. It won't have any affect above the MaxSteerSpeed, where your standard rudder calibration will kick-in. Please see the box on P34 of the FSUIPC6 User Guide. I would also try just using the steering tiller calibration initially, if thats not good enough then yes, by all means extend the range to de-sensitize around the centre. John

I'm sorry Nick but I really can't help you with this. You really need support from PM or CPFlight, or from @Thomas Richter for TSR. John

I have added two new (undocumented) controls for the master avionics: Avionics Master 1 Set Avionics Master 2 Set Tested these in the C172 and they seem to operate in the reverse manner than usual, with a parameter of 1 turning the avionics off, and a parameter of 0 turning them on. These new controls are available in the attached version: FSUIPC7.exe