John Dowson

Windows error 740 is "The requested operation requires elevation", i.e. you need admin privileges for the operation, so yes, it is a permissions issue. Do you mean you set each one as unchecked? If checked, they will run in admin mode and so would require FSUIPC7 to be ran in admin mode, which in turn would require MSFS to be ran in admin mode. I think the issue is that TrackIR does require admin mode, and will request this if not ran in admin mode. See the following post for possible work-arounds to start TrackIR automatically: John

I don't know what "pop out manager" is but I would be very surprised if that updated your FSUIPC7.ini file....anyway, glad its all working again. John

Hard to test without the GF hardware though.... And a Happy Easter to you! John

Yes, I would think that 0x07F2 should be a signed word ("SW"). @eagle11 Your script would also be simpler if you read the value as a signed value rather than unsigned, and you are also using value as both an integer type and a string type...seems quite confused...but if it works....!

Again you are not providing enough information - what do you actually see when you move the axis? Is another axis recognised? If so, ignore that and try again. If another axis is again recognised, ignore that and try again. Repeat this until the axis you want to assign is recognised. Profiles have nothing to do with axes scanning / recognition - profiles just dictate how the axes assignments are saved/stored. If you still get issues, please attach your FSUIPC7.log and FSUIPC7.ini files.

As the Asobo cessna 172 classic (aka "Cessna Skyhawk Asobo") uses your dr400 profile - does this occur with all aircraft using that profile, or only this one? It would strike me as very strange if this only occurs to this aircraft in this profile... Also strange that this suddenly started! You have got DirectAxesToCalibs set (to Yes) in your profile - not sure why you have set this. Anyway, I have cleaned your ini a bit, so could you please try the attached (save/rename your current FSUIPC7.ini, and then download the attached to your FSUIPC7 installation folder). If you get the same issue, could you generate another log file for me, with Axes Controls logging enabled as well as Extras logging, but just load the aircraft, and then activate the left brake through its full range, then the right brake, and then exit FSUIPC7. Then attach the log and ini files again. And if you really need DirectAxesToCalibs set (please see the Advanced User guide for this ini parameter), try setting that to All instead of Yes - this will allow offset writes for axis inputs to the brakes to be calibrated, where Yes will only allow this for rudder, aileron and elevator axis offsets, FSUIPC7.ini

The AFC Bridge is only for the lights on the Bravo, and shouldn't affect the Axes. At least it was - I haven't looked at this for a while (and don't use it). There are also other ways to get the lights to work with FSUIPC. Yes - that icon only displays a splash screen and starts MSFS. It doesn't start FSUIPC7 - that is done by MSFS itself, if you selected the auto-start component during installation. To start FSUIPC only, you can just double-click the FSUIPC7.ese in windows explorer. If auto-start isn't working, see the FAQ section - there is a topic there on this subject. You can assign to the Honeycomb axes without MSFS running, but only in the general section (i.e. not in an aircraft-specific profile) and this also has other limitations, so always better to have MSFS running when assigning axes. And I suggest you read some of the documentation - the Installation and Registration guide to start with, and the User guide. You should at least be familiar with those documents, and also check the documentation (as well as searching this forum) before asking for support. I get the same questions all the time from new FSUIPC users...it would save everyone time if they read the provided documentation and used (i.e. searched, not post) the forums for similar issues. What was your issue with the Assignments menu not being present (i.e. registration valid in installer but not registered when running FSUIPC7)? You haven't responded in your other post - can I take it that this is solved and delete that post (as if it is for FSUIPC7, its in the wrong place) ?

What do you see when you hit the rescan button? Do the MOVE LEVER labels change to Joy# and Axis# and show a joystick id and axes letter? If so, an axes change was detected - if this isn't the one you are moving, click the Ignore Axis button and that axis will be ignored until you close the axis assignment dialog. Sometimes a jittering axis can prevent the axis you are trying to be assigned from being detected. If that is not the case, please explain what you see in that box (e.g. do the MOVE LEVER labels change? Is a joystick number and axis letter registered, and if so what?)and attach your FSUI{C7.ini file. Didn't you also post in the main support forum saying that you had registered in the installer but FSUIPC was unregistered? Was that for a different version of FSUIPC?

Good luck with that!

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.