pointy56

Hi John, Thank you for clarifying a number of things that are specific to FSUIPC7 - as you say this is necessarily different to previous versions, but I was basing my questions on the documentation. Specifically, both the latest offsets list and the Programmers guide still say: Byte 2 (bits 16-23): Flags from application. Bit 1 (2)= set if Hot Key should be passed through to FS, else it will be trapped. So my understanding was that not setting this bit, and PF3 does not, prevents the keystroke being passed through to the FS - clearly this is not relevant with FSUIPC7. I'm sorry if I missed this specific hotkey handling difference with FSUIPC7 somewhere else in the documentation. But the log entry also made me think that the old action was still the case: 4454609 - no pass through (not checking FSUIPC assignments) I have spent days trying to identify why C/S/Y causes a view change, when I couldn't find the binding. Someone in the MSFS support forum suggested that it was incorrectly taking C/S/Y as plain 'Y' and I've just found that removing that binding (Slew) fixes the problem. So I'll be logging this issue as a bug with Asobo. Thanks again for your patience and explanation of the differences with FSUIPC7. Martin

I am using FSUIPC7 with MSFS to support PF3, and am finding that some hotkeys seem to be being passed through to the FS although they are configured to not do so. The specific key combinations are Ctrl/Shift/N and Ctrl/Shift/Y - I have managed to disable C/S/N in the FS, but cannot 'find' the binding for C/S/Y to disable it (really helpful!). I cannot be sure, but I don't think I was seeing this until fairly recently; over the past few weeks I have updated several times and am now on 7.4.8. The attached log shows a series of C/S/N hotkeys followed by two C/S/Y hotkeys (the second is solely to toggle the effect of the first one in the FS!) - timestamp 4454609 onwards. Is the behaviour that I am seeing expected or a known issue? One other minor thing: The hotkey table near the start of the log doesn't seem to show the 'Shifts' byte correctly; this may be because of the way PF3 loads the entries. (The second attached file shows a dump that I took from the hotkey area after PF3 was loaded, and shows the Shifts byte that has been set for each entry) Thanks, Martin FSUIPC7-log.zip PF3-Hotkeys.txt

Ok, thanks John. Yes, that registry entry was incorrect, although everything else seems to be working as expected! (Most of the 'similar' values in the registry are associated with One Drive, which I don't even use, so seems like another Microsoft special!)

I have just updated to FSUIPC 7.3.24 and noticed in the install log that it placed the documentation in a documents folder for another user. Somehow on my PC I have ended up with 2 user accounts 'Martin' and 'marti' - I can't remember how this happened, but I only log-in and use 'Martin'. From the install log: Updating EXE.XML for Steam install C:\Users\Martin\AppData\Roaming\Microsoft Flight Simulator\EXE.xml has been updated. ... Create folder: C:\Users\marti\Documents\FSUIPC7 Documents directory created: C:\Users\marti\Documents\FSUIPC7 Output folder: C:\Users\marti\Documents\FSUIPC7 I have manually copied the FSUIPC7 folder into my Documents so that I can find the user manuals - interestingly there was an existing FSUIPC7 folder there which contained older versions. I've attached the full install log - I assume this isn't the expected behaviour. InstallFSUIPC7.log

Hi Pete, It seems that from a Windows 10 command line the parameter needs to be enclosed in double quotes to work, e.g. MakeRwys.exe "/>500" , otherwise it creates an empty file for redirected output (called 500 in this case). Regards, Martin