John Dowson

Have you looked at the Log menu? There is an Offsets... option. and it should be obvious...and, if not, please consult the User Guide....as I said.....

Could you also activate logging for IPC Writes, and with this and Event logging activated, as well as the offset monitoring I mentioned, and repeat the tests. The resulting FSUIPC7.log file may be quite large and need compressing/zipping before being attached. Note also that it is now the festive period, and as well as having other support requests that I need to look into, I am also planning on taking time off over the next 2 weeks, so please be patient. If you can provide the required logs I will get back to you once I have had time to go through them. It would also be useful to see the output from the HidScanner program if you could run that, available from John

Try looking under the Log menu of the FSUIPC7 main window - it should be obvious but if not please consult the User Guide - they are provided so I don't have to continually respond to such questions... That is fine - I just need to check if the offsets/events that the PFC driver macros are using are valid for that aircraft...You can also try another maybe simpler aircraft for comparison (e.g. the C172). Presumably you are referring to the PFC console window, not the FSUIPC one... But could you open the FSUIPC main window from the system tray? If you close the FSUIPC console window if open (using Log -> Close Console), then as well as showing/hiding the FSUIPC7 main window, you should also see the FSUIPC icon move from the system tray to the task bar and back again on alternate presses of Alt + F. If the console window (FSUIPC) is open, there will always be an FSUIPC icon in the task bar, but if you hover over it it will also show the FSUIPC7 main window if it is not in the system tray, and if it is in the system tray then Alt + F should display the main window and you will see this when you hover over the task bar icon. It could be that the main window is being displayed but outside of your displays coordinates. Your log file shows that the Alt+F hot-key is registered ok with windows, which is why this is confusing and I need to know more about what is actually happening.

Still not sure why your radio stack isn't being recognised - I will talk to Pete and get back to you on this. For the Console, some of the offsets being used are no longer writeable, but others should be - but I am not sure if they are working for the aircraft you are using (G58) - again, I will check this and get back to you. However, the FSUIPC7.log file you provided is cut-short, ending after 66 seconds and attached when either FSUIPC7 was still running or had crashed. You also did not activate logging for Events in FSUIPC. Can you please do this and repeat the tests with the console for the following buttons (those tied to events): Landing Gear Pitot Heat on/off Flaps inc/dec Can you also add offset monitoring for offset 0D0C as U16 in hex and repeat the testing of the lights (Nav/Bcn/Strobe/Taxi/Landing). Once done, exit FSUIPC and show me the FSUIPC7.log and PFChid64.log files. Are you sure FSUIPC was still running? I can't see how that can stop working.... Could you still open the main window from the system task bar icon, or see FSUIPC in the task bar?

I was not aware of ShowText (before my time!), but it does look interesting and a possible to solution to the problems with message display in MSFS / FSUIPC7....if it does indeed function correctly with FSUIPC7. I will look into this further when I get time over the festive period, but please report back if you try it. Note, however, that the FSUIPC Display Options, available in previous versions of FSUIPC, are no longer available in FSUIPC7. John

For any issues with auto-start of FSUIPC7, please see the following FAQ entry: John

I am not familiar with ShowText and so cannot advise on this. I can look into this when time permits, but maybe you can just try it and report back.... John

I am not familiar with ShowText - that is user contributed by Rob van der Wiele. I am not sure how that works and so don't know if it is compatible with FSUIPC7 / MSFS. I will look into this when time permits. John

If using FSUIPC for the assignment, you can use event.button (if the rotary uses buttons) and in the handling function, read the lvar value, increment/decrement it, an then write back/update the lvar to the new value. Not sure how you would do this if assigning in MobiFlight. John

That version is quite old - only the latest version is supported, which is 6.1.9 - please update when you get a chance. Also, please attach your FSUIPC6.ini if you need further assistance, rather than pasting extracts. John

Note that the SimConnect_Text function is now documented as: The SimConnect_Text function is deprecated and cannot be used in Microsoft Flight Simulator. There also doesn't seem to be any replacement or other method to display text or menus in MSFS. I will at some point (when time permits) look into providing another method to display text, such as that provided by the lua Wnd library, but this would be for text display only and not for interactive menus. John

The issue with RC with MSFS is the use of the SimConnect_Text function that is used to display multi-line text and menus. This is now documented as "deprecated and cannot be used in Microsoft Flight Simulator", so unfortunately it cannot be used. See the following post for more info: John

Well, attaching your FSUIPC7.ini file would help me understand....but a slope of -15 would make your elevators/ailerons extremely sensitive around the centre - this is the response curve for a -15 slope: Try a positive response curve instead.... There are also other methods to reduce sensitivity, but first try changing the slope value to a positive one.... If you need further assistance, please attach your FSUIPC7.ini and FSUIPC7.log files so that I can see the settings as well as details on the aircraft you are using, etc. You also posted in the User Contributions sub-forum where it explicitly states NOT for support requests. I have moved your post to the sub-forum for FSUIPC7 / MSFS. And if you search this forum, I have responded to the same issues on axes sensitivity many times....for example, see John

The latest, and only supported version, is 4.977. I don't think there are any functional changes between these versions, just built using a later windows toolkit. This is just writing the value of the lvar L:CUSTOM_AP_ALT_VAR_SET_ENGLISH to offset 0x66C0 each time the lvar value changes, as you are incrementing the value after writing it. If you just want to increment/decrement the lvar value by 1000, you don't want an event on the lvar... A rotary encoder normally uses either one or two buttons (one slow, one fast) in each direction, so is programmed the same as when using buttons. Or does it use an axis? But I cannot help if assigning using MobiFlight - try the MobiFlight Discord channel for MobiFlight support. John

Those offsets are related to the GPS settings - I think you are looking for the OBS settings which are held in 0x0C4E and 0x0C5E. John

What FS and version of FSUIPC are you using? How have you assigned your toe brakes? Please show me your ini file. Also, if your issue is that the toe brakes are either fully on or off it could be a registry issue - please see the following FAQ entry: John

Your ini shows that you only have one assignment, which is the throttle assigned with 'Direct to FSUIPC Calibration' but you have not calibrated your throttle assignment. Please do this and try again - you must calibrate in FSUIPC if assigned in this way. Your calibration section is also empty apart from a RudderBlendLowest parameter - did you manually remove the other parameters? Please calibrate and try again. If you still get issues, please show me your updated FSUIPC7.ini and your FSUIPC7.log file, generated with logging for Axes Controls activated, load an aircraft and move the throttlle through its full range and back again and then exit FSUIPC before attaching your files. John

It does say this but it should be fine...no change in this offset from FSUIPC5 and onwards, so I wouldn't expect a problem... This is the test you need to do, and with the FSUIPC7 button assignment window open, to see if it is registered. I am away this weekend, and when I get back it will take me a while to catch-up on support requests, but once that is done I can check this further here. John

Then install without the add-on.xml component. This should be fine - it just uses a different method to link FSUIPC6 to P3D. I suspect this is due to an issue with your registry in determining the location of your Documents folder. These entries in your log look suspicious: Does that exist? That is taken from your registry, from HKCU: SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders You could try correcting that, otherwise just use the DLL.xml method to start FSUIPC6, whuch us what is used if the add-on.xml component isn't checked. John

I don't know...those offsets have been around for quite a while now, so I don't think it is an FSUIPC issue but I can check. However, I am away from this afternoon, back next week, so it will take me a while before I can take a look at this in detail. Keep me updated if you find anything, otherwise I will report back once I have checked that offset area (mid to end of next week), John

So the installer is crashing rather than completing? Can you re-run the installer, and uncheck (i.e. not install) the add-on.xml component to see if that makes a difference. If it still crashes, try unchecking the the other checkboxes so that only the FSUIPC6.dll is installed. Are you installing for P3Dv5 only? Do you have P3Dv4 installed? If you manage to get a successful installation, please show me the InstallFSUIPC6.log file. John

Every variable type is a sequence of bits, whether it is a string, an integer, a floating point number or any other type. You just have to read it as a string. Each letter is one byte / 8 bits: O = 0x4F (Virtual Key Code) = 01001111 S = 0x53 = 01010011 T = 0x54 = 01010100 And so the string OST in binary is (in reverse order - how strings are stored) : 010101000101001101001111 which is what your picture shows. And 010101000101001101001111 as an integer is 5526351, also as your picture shows. As I said, to read it as a string in lua you would use n = ipc.readSTR(offset, length) John

Ok, but note I am on holiday from tomorrow afternoon until Monday afternoon.

For any installation issues, you should ALWAYS attach your InstallFSUIPC6.log file... Did you run P3Dv5 at least once after installation and before installing FSUIPC6? This needs to be done as the P3D registry entries, needed by the FSUIPC6 installer, are not present until you run P3D for the first time after installation. I suggest you try uninstalling FSUIPC6 by either running the uninstaller that is created in your FSUIPC6 installation folder, or using the Windows App management panel. Then install again. Any issues, show me your InstallFSUIPC6.log file. You don't need to do this - just run the installer and it will prompt for elevated privileges when needed. John

The first thing you need to check is if the aircraft is using the new fuel system or the legacy one, which will determine which offsets or simvars will be used. This is held in offset 0x07A8. For what simvars are available for each fuel system, you will need to consult the MSFS documentation here: https://docs.flightsimulator.com/flighting/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Fuel_Variables.htm I should really add this information to the offset status documentation, i.e. if an offset is holding a simvar from the legacy or the new fuel system. I will make a note and do this for the next release, but for the time being you will have to consult the MSFS documentation to know if a simvar (or offset that holds that simvar) is available for the aircraft being used. Note also that there are many fuel system simvars not currently held in offsets. They can be added to free offsets if needed, for both reading and writing (if writing to them is possible) - see the Advanced User guide section Adding Simulator variables (simvars) to FSUIPC offsets on page 34 for details, John