John Dowson

Do you even have FSUIPC installed and running? What version? What FS are you using? This seems to be an issue with IFLY MAX or IflyToFsuipc - I have no idea what these are, so I think you need to try the support forum for this product. I only support FSUIPC and the other products that I provide, and not products that may use FSUIPC.

Ok, that makes sense.... However, I still can't locate that button - the only operative buttons I can see on the stick/yoke is for Paddle Switch (and a pitch/aileron trim control). Maybe you could take a screenshot to show me where this is? You can also try the general method of determining what event to use. Activate logging for Events (Log -> Events), open the logging console (Log -> Open Console) and then push the nose wheel steering switch and see if any event is logged in the console. If so, you can use that. If not, the next thing to try is lvars. Looking at the lvars for the FA-18, the following may be applicable: FA18_DDI_STEERING_SOURCE FA18_IS_STEERING_COUPLED See how the value of those lvars change when you push/toggle the nose wheel steering (using Add-ons -> WASM -> List Lvars). If one (or both) of those change, then you can try changing those to see if they can be used. First try using the Add-ons - WASM -> Set Lvar... function, and if that works, you can then use those either via a macro, a lua script or by adding them to FSUIPC offsets - I can help with this if needed. John

👍

Maybe it was the original wxstationlist.bin file that got corrupted somehow, and the repair fixed that. Anyway, glad its now working - and thanks for posting your solution. John

Ok, glad the console is now working. I will update you about the avionics stack once we have more information from PFC. ...and best wishes for the festive season to you as well! John

But what makes you think this has anything to do with FSUIPC? As I said, an unregistered copy of FSUIPC isn't doing much except populating offsets for use by 3rd part programs, such as GSX, and providing logging information. Furthermore, FSUIPC4 has been stable for many years, and also closed for further development for several years, so I really doubt that any of your issues are related to FSUIPC4.

Sorry but I still haven't had time to look into this.... I am on holiday now, until the 3rd January, but will try and look further into this issue next week, when time permits. I will report back again once I have investigated. John

Why do you think FSUIPC CTD'ed? The log file you attached (which has a lot of logging activated for some reason...) shows that FSUIPC exited normally. And as you are using an unregistered copy of FSUIPC4, it isn't doing much except providing support for 3rd party programs... It does sound like your issue is with GSX, so I would wait to see what they say about this. I am also now on holiday, back around the 3rd January. John

For your Radio Stack, this is a newer version and is not currently supported by the current PFChid64 driver. We have made enquiries to PFC about this device (or these devices) to see if the decoding is the same as for the original C2AVIONICS device. If so, we should be able to update the driver with support for this. If not, then you will have to contact PFC on how to use this device. I will keep you updated. John

This certainly sounds like an issue with a weather file.... I am an holiday now until the 3rd January but I will take a look at this further when I get a chance - probably next week sometime... John

Then you haven't found a way to assign a switch to "nose wheel steering"! What is your assignment? It would help if you attach your FSUIPC7.ini file as well as your FSYUPC7.log file showinf the assignment triggered (i.e. with logging for Events activated)... What exactly is your question? Is this about nose wheel steering (this axis is not available in FSUIPC7 for assignments at the moment as it has not been made available via the MSFS SDK) or about toggling the "HUD of NWS" on/off? Please clarify....and what is "NWS"? Note that I am on holiday from now until the 3rd January but I can look into this when I have some free time if you provide more information... John

There is another simvar available (see https://docs.flightsimulator.com/flighting/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_RadioNavigation_Variables.htm😞 This is not available in any offset, but can be added to a free user offset using the facilities described on page 34 of the Advanced User guide. You could try adding that to see if that holds the required value. Or check for any other simvar (or lvar) that may hold the CRS heading value that you are looking for and add that to a free/spare FSUIPC offset. John

Are you sure your console isn't working? Your FSUIPC7.log shows the correct offsets being updated, and the correct controls being sent, which should work in the C172. I haven't tested everything, but I have tested flaps inc/dec, pitot heat on/off, and panel, nav and beacon lights and they are all working... If you are sure that, for example, the pitot heat on/off isn't working, can you try assigning a key press to Pitot Heat On and one to Pitot Heat Off and test the key presses to see if they work. Btw, there is no offset monitoring in the log (but not really needed) - you probably forgot to check the box Display to Normal log file. You also started to operate the controls a bit earlier - please wait 4-5 seconds for everything to start/load after the aircraft is ready before you try and operate it. If you have the main FSUIPC window open, you can tell when everything is ready as a message is displayed indicating the number of lvars, hvars and presets available. John

A User Contribution is already available for the Loupedeck - see John

The Honeycomb Bravo (including trim wheel) should be relatively straightforward to set-up. See the following post which has details on the trim wheel configuration using a lua script to implement fast/slow trim: John

Then reverse them... You can do this in the calibration section/tab (in page 2 for toe brakes). Note that if you have assigned with 'Direct to FSUIPC Calibration' then you must calibrate anyway, so do that. If you have assigned with 'Send to FS as normal axis' then you can either calibrate and reverse in FSUIPC calibration, or scale the toe brake axis by -1 by adding ,*-1 to the end of the toe brake assignment lines in your FSUIPC7.ini (do this when FSUIPC7 is not running) - see the .section Additional parameters to scale input axis values in the Advanced User guide for further details on this method. John

I am sorry but I am still confused, and am not that familiar with the G3000/G5000. I don't understand the use of CRS in relation to the GPS. If you want to change way-points, wouldn't you need to do this by changing the flight plan in the FMS? The data held in the GPS offsets are read-only and are just populated from data received from the FS based upon your flight plan. You also say that it is logical that you cannot modify the CRS value but it seems that this is what you want to do....this doesn't make sense to me. I'm sorry but I don't think I can help you any further with this. John

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