John Dowson

Ok, some progress... But did you see anything registered in the button assignments window? I don't think so, as the button state reported is always empty: So no virtual flag would be triggered. However, it does look like something is changing, as the actual 'data read' is different, so you could perhaps do something with this, but that could/would be quite complicated - especially for a non-programmer, or someone who doesn't have the device...

Ok, thanks for the update - good to know. I believe DX12 with nvidia is still not that stable. If you have a driver version that seems stable I would stick with that, but try the new releases anyway to see if they are ok, otherwise revert back to the version that is working for you. I have issues with DX12 when I have tried that (although I haven't tried for a while now) so I am sticking to DX11 for the time being. But, as I said, such issues are not related to FSUIPC.

For the lua script test. the lua file is not being started as this is your [Auto] section: whereas it should be As I said: So please try that. Also, with this lua test, open the button assignments dialog to see if any (virtual) button is recognised. However, this is the test I asked for in my last post, so you can ignore that one now. Your log shows that only button presses on device 19 were detected, which I presume is one of your PFC com devices. Also note it is also a good idea to wait for a short period after aircraft load for everything to be initialised and started, especially when trying to track down issues. If you have the console window open, wait until the following lines are logged before doing anything: Please try the lua test, but it does seem that this device requires some sort of "tickle" to be sent by the/a driver before it becomes active...Have you asked PFC about using this device with MSFS2020? Do you have any technical documentation for this device? Try the lua test but after this I am out of ideas. I will ask Pete, who has more experience with PFC devices (and wrote the drivers) next week, but I think it will be PFC you need to contact for this device... John

Ok, thanks. I will look into this after Easter and post a version here for you to test.

Then why are you posting in this thread/topic? Please do not hijack unrelated topics - if you cannot find a topic for your issue, create a new one, And you should try the trial license before purchasing.... What does this mean? You need to explain what your issue actually is - I cannot help if you just say it isn't working. That is not an error, just an informational message. WideFS is a separate product and requires an additional license. If you don't know what it is, you don't need it. Again, this means nothing. What are you trying to get to work - a button or axis assignment maybe? Do not respond here. Create a new topic, appropriately titled, and specify what your actual issue is, and include/attach your FSUIPC7.log and FSUIPC7.ini files. Please at least read/peruse the provided documentation first - start with the User guide... John

The first log you posted shows: which should indicate that the device is detected as a standard HID device and should be assignable without the need for any other driver. Did you try without using the PFChid64.dll and without the PFC Test GUI running? If not, can you try that please, and set logging for Buttons & Keys (Log -> Buttons & Keys), open the logging console (Log -> Open console) and see if you get anything logged when you press a button. Also, please attach your FSUIPC7.ini file.

FSUIPC doesn't have anything to do with this issue - it doesn't do anything at all with graphics cards/devices. First check if there is an update for your graphics card drivers - they tend to get updated quite regularly. If you continue to get the same error, check the Asobo forums - I am pretty sure there are plenty of reports on such issues. Also, if using DX12, maybe try switching back to DX11. Not sure how stable DX12 currently is.

The available presets are from a community-driven effort led by MobiFlight. I provide the mechanism to use these presets, not the presets themselves, which are from the MF HubHop server (https://hubhop.mobiflight.com/presets/). For any issues with presets, first check the MF HubHop site (the source of the presets) for any additional information - the preset may be for a specific variant (for PMDG, this would be stable, development or experimental) and additional information is sometimes available in the description. For any questions on individual presets, please use the MobiFlight discord server, in the HubHop channel, and it is recommended to tag the preset author (using the @username notation).

No problem - glad its now working... PMDG offsets were enabled in v7.3.8 - as you were using 7.2.11 (I had read this as 7.3.11!), that was why they weren't working. That version was from October 2021, so very old! You should check for updates more regularly, and always before requesting support. I tend to release a new version every month or so, mainly with minor changes, but worth checking occasionally. MSFS is a bit more stable now, but still work is needed after every MSFS update, so you should always check a day or two after any MSFS update. John

Just don't use the New Log feature - that starts a new log file, as the name suggests, You don't need, and I am not expecting you, to be an IT specialist or software engineer...

👍

No other installation components can cause the issues you describe, and the only other component that actually runs with MSFS is the WASM module. You only need that if using lvars, hvars, presets or calculator code - or if using other add-ons that use the FSUIPC WASM module. The other components are documentation and SDK related (i.e. for developers). John

Just checked in the PMDG 737 and all seems ok, apart from the (expected) hang/pause I get for a few (5-20) seconds when the auto-save kicks-in. You can also try in devmode with the debug console open - see what messages you get there as they might give an indication as to what the problem is. But certainly first try without the MaddogX if your issue only started after installing the latest HFs for this aircraft... John

Are you using FSUIPC (registered) for your assignments? It sounds like you aren't from your description, so I'm not sure I can help - the P3D forums should be the place for such issues, so I am surprised that they referred you hear... You can also try posting on avsim.com for such issues. It may already be auto-assigned to your yoke - check the yoke button assignment in the P3D options and remove or change the assignment. With which aircraft does it work, and which not? But again, difficult to advise if you are not using FSUIPC. If you are using FSUIPC, you can activate logging for Events (non-axis controls) and Buttons & Switches for the first issue, and for the rudder issue you will need logging for Axes controls activated. You can open the logging console and see the events logged in real-time, which may help you diagnose the issue, or you can attach your log files here, as well as yout FSUIPC ini file. John

A couple of other points: Two entries under [LuaFiles] are the same - remove one of them: Did you add these manually? That section is written and maintained by FSUIPC - you should not modify this manually unless you really understand what you are doing... This is an invalid entry - if you want that lua started, it should be: I'm also not 100% sure that having an '&' symbol in a lua (or any) file is a good idea, so maybe rename that.... Also disable all logging - I will ask you to set any logging when needed. John

If you get a CTD, check the event viewer in windows application events to see if any crash events are reported. You can also activate SimConnect logging and show me the simconnect.log file - see the following in how to activate simconnect logging: It will be large and so will need compressing/zipping. Drop the files to attach from Windows Explorer to the bottom of the comment field, where it says 'Drag files here to attach, or choose files...' - or use the choose files option. If you are just using FSUIPC to support 3rd party add-ins, you don't need a registered version, so you can install without registering, or - maybe better, register but after installation rename your FSUIPC4.key file to something like FSUIPC4.key.unused. This way you can enable the additional facilities provided by using a licensed version by renaming the file back, when you need to. Probably a good idea to try and sort out your issue with the unregistered version first if you are not using these additional features.

First, your ini file is a bit of a mess....for comments in ini files, you need to use either ';' or '#', not '//' or '!' characters - see https://www.w3schools.io/file/ini-comments-syntax/. From the Advanced User guide: Try removing it from your Community folder to see if that makes a difference. I don't have the 738 (or the MaddogX), but can check with the PMDG 737 later... John

float - a double would be 64-bits. FLT32 is what is used in FSUIPC's offset monitoring facilities and is not a language data type. I don't use C#, but maybe try: public Offset<float> Engine1fuelUsed = new Offset<float>(0x090C);// Engine 1

Again the log file you posted is useless - please always post full logs. You can try with lua - take a look at the HidDemo.lua script provided: copy it to your FSUIPC7 installation folder, update the Vendor and Product names and add it to the [Auto] section of your FSUIPC7.ini file (see the Advanced User guide for further details on how to auto-start lua scripts, if needed). Once that is up and running, see if the virtual flags are recognised in the button assignments panel. Possibly. If you can work out what this is (any documentation with the device? Or PFC support?) then it may be possible to send this via lua.

This version is quite old now - the current and only supported version is 7.3.19. Please update. Also check that you are using the latest version of the PMDG 737, which is 3.0.65. I have not had that issue. You should first verify if FSUIPC7 is receiving the PMDG data. To do this, add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x400 If the PMDG offsets are enabled and working, you should see the following lines logged in your FSUIPC7.log file: If the offsets are enabled but no client data is received, then the PMDG SDK broadcasts are not enabled. If this is the case, double-check you have enabled broadcasting in the 737_Options.ini file in the correct location for your installation (see the PMDG SDK document). If it is enabled then you need PMDG support - check their support forums. If FSUIPC7 is receiving PMDG broadcasts, then you can try logging that PMDG offset (and others) using FSUIPC7's offset logging facilities to see if the updated values are logged. If so, your issue is probably with your MobiFlight set-up and you should ask about this on their discord support channel. John

The license has been updated - sorry for the delay.

It is a 32-bit float (as documented), not an integer, so I suspect that you are reading them incorrectly - monitor them as FLT32. Just checked in the PMDG 737 and they seem to be working correctly, starting at 0 and increasing: Of course, only two offset changing as there are inly two engines. John

How can I possibly answer that? Yes. These may or may not hold the correct value - try monitoring those offsets, using FSUIPC's offset monitoring facilitis, as you fly and see if the values increase from 0... If they don't work, you can use the PMDG offsets (from the Offset Mapping for PMDG 737 document - should also apply to the 738): 6494 4 FLT32 FUEL_QtyCenter LBS 6498 4 FLT32 FUEL_QtyLeft LBS 649C 4 FLT32 FUEL_QtyRight LBS You would need to initially read and save the quantities at the start of the flight, and then whenever you want to know how much fuel has been used simply read them again and subtract that number from the initial values.

If it is a joystick type HID device then it should be recognised by FSUIPC7 and can be assigned there. However, I cannot tell as you are only posting continuation logs, not full log files that include the joystick scanning section. Remove the PFChid64.dll, start MSFS/FSUIPC7, set logging for Buttons & Keys, press a few of the buttons on the PFC430 and see of the buttons are recognised. If so, they can be programmed, if not then it is just not possible. If it is recognsed as another HID type device, it may be possible to control via lua using the com library. No. that means nothing to me. If you have installed any specific drivers for this device, you should also remove them and let windows install the generic HID joystick drivers, which is what FSUIPC would need to be able to use the device as a generic joystick type HID device.

I will ask Pete about this when he returns from his holidays (next week) to see if anything can be done, but if not, and for now, you will just have to use your work-around.