John Dowson

What do you mean by 'deleted'? I understand that as being removed from your ini file, but this doesn't make sense... Do you mean that your assignments have no affect? If that is the case, I need to see a log file where you press the button assigned to flaps, and then press another button that has an assignment but has no affect, with logging for buttons and keypresses + events activated. Maybe that is what you have already done - I will take a look at your log files tomorrow, if I have time, but more likely on Sunday. Finishing now for the evening.... John

But what am I looking for? Can you please clearly explain your issue...as I said: John

I need to see your updated FSUIPC6.ini and a FSUIPC6.log file with appropriate logging added (Buttons and Key presses + Events). What exactly is happening when you do this? Could you please explain what your actual issue is. And this also seems like a different issue to your initial posts. I have no idea what your issue actually is at the moment.... Sorry, but I have no idea what you are asking here. FSUIPC profiles are stored in your FSUIPC ini file (or files, if using profiles in separate files). FSUIPC does nothing with your aircraft cfg file. No, just zip them. They are text files and compress pretty small. John

Btw, could you please let me know your two WideFS7 order numbers. Just the order numbers please, no other details. John

Dont contact Pete for this. You need to contact SimMarket. They will then contact Pete for approval. I will let him know to expect such a request. John P.S. I have just deleted your second post, as it was pretty much the same as this one....

Yes! WideFS7 is compatible with FSUIPC4, FSUIPC5, FSUIPC6 and FSUIPC7. Unfortunately there is a no refunds policy on SimMarket. However, you could ask for a refund (as it is a duplicate purchase) and Pete may approve - WideFS7 is still with Pete so I cannot help with this. I'm not sure why your key would not validate via the installer though... Note that you can now also run FSUIPC7 on a client machine. This is different than running WideFS on a client machine, as it would maintain a seaparate and distinct offset are to that held by the FSUIPC7 running on the FS machine. Details on how to set this up are provided here: However, as you have a WideFS license (well, 2 now...!), you may as well continue with that. Regards, John

As it says in the Advanced User guide: If you remove them, they will be added back unless you add that ini parameter I mentioned. You cannot selectively keep annotations, its all or nothing. If I were you, I would just add your additional comments AFTER (i.e. at the end of the line, as the documentation states) the annotations. But if you want to remove all annotations, go ahead and add that ini parameter. John

Sorry, but I am not sure what you are asking...could you maybe rephrase? The annotations are automatically added. Looking at what you posted, the annotations on the first two entries don't look correct though - did you manually change these? They should be re-written the next time you run FSUIPC. If you do not want the ini file annotated, you can change the following ini parameter in the [General] section: Annotate=No although I don't understand why you would want to do this....! John

Also, I have noticed that you have installed FSUIPC6 under your documents folder. This can cause issues. It is better to install outside of a windows protected folder, such as in c:\FSUIPC6 or C:\P3D Add-ons\FSUIPC6. To do this, re-run the installer and select a different folder. You do not need to re-register, but after you have installed copy cross your FSUPC6.ini and FSUIPC6.key files to the new location, together with any other files (e.g. *.lua, *.mcro, *.dll) that you are using. Maybe also try re-installing the P3Dv5 client and the QW 787. Once that is done, show me your log file with the recommended logging activated if you are still having issues. John

You should also update your 787 profile to use substrings to match all the QW 787s, by changing to this:

You have a strange error in your log: Not sure where this is coming from... What do you mean by 'another button'? Does this mean pressing any button? It is better to disable controllers completely in P3D if assigning in FSUIPC, as P3D has a tendency to automatically re-assign your controllers on occasion. Could you activate logging for Buttons and key presses as well as Events (non-axis controls) and produce another log file showing your issue. John

Then I have no idea why the throttle isn't working when you first start, or why reloading your assignments would fix this, if you are not even using FSUIPC assignments.

👍

Why do you think that 'FlyByWire_A320_NEO' is a substring match for the aircraft name "Airbus A320 Neo FlyByWire"? Do you understand what a "substring match" means? Try renaming your file to "A320.hvar", or maybe "A320 Neo.hvar". I am spending a lot of time trying to communicate things to you that are explained in the Advanced User guide, and also in many other precious support requests. What exactly don't you understand? Is it the phrase "substring match"? This simply means that the name of the hvar file, without the extension, must match a substring of the aircraft name, AS LOGGED BY FSUIPC. So, check your log for the name of the aircraft, and make sure that the name of your hvar file is a substring match to that aircraft name. It really isn't that difficult.... John

Yes, copy and rename... Then I suggest you re-read it until you understand...did you not read this: If they are too bug to attach, just zip them. They are text files and zip pretty small. BUT, I do not need to see any files if your issue is that you have not put the hvar file in the correct place with a suitable name. Please try that before anything else. John

Did you check the name and location of your hvar file? If you think there is a problem, you need to enable debug logging in the WAPI and WASM, and show me your log again and also the FSUIPC_WASM.log. But first please read the Advanced User guide on how to use hvars, P44.

Yes. You need to manually change the Vendor, Product, possibly the device and also the Rotaries array (for your button numbers) John

Which is it? I can't understand this - is there not a menu item below the 'List Lvars' one, which you say is working, that says 'List Hvars'? If there is, and the lvar menu item is working then this must also be working. Are you sure that it is just not listing 0 hvars (check your log)? Why do you need that? It needs to match a substring match on the aircraft title, as logged in the FSUIPC7.log file, and also in the aircraft.cfg file I believe. For the FBW A320, it is this: Aircraft="Airbus A320 Neo FlyByWire" so your file name is not a substring match. Also, check that it is in the correct location, under the FSUIPC WASM modules folder, or in its persistent storage folder (under AppData). Please see the Advanced User guide for details.

What do you mean by 'open' in this context? If you can list lvars, the List Hvars menu item should be visible/accessible. Or do you mean no hvars are listed for the loaded aircraft? If so, have you added a hvar file for the aircraft you are using (with name if hvar file a substring match to the aircraft)? Have you read the section on how to use hvars in the FSUIPC Advanced User guide? John

...you could also try using a mouse macro, if no appropriate control or lvar exists.

For the PMDG: - check available custom controls (see the SDK documentation) - check available lvars - there is an DSUIPC control to do this which you can assign to a button or key press. The lvars and their values are listed in the FSUIPC6.log file If any look applicable, you can try changing their value (using a macro or lua script) to see if they have any affect - ask on the PMDG support forum to see if it is possible to control the switch guards externally John

How is your throttle assigned? I don't see any throttle assignments to axes either in your general [Axes] section or your profile specific [Axes.PMDG] section. Are they assigned to buttons or keys (on inc/dec controls)? If so, could try activate logging for Buttons and key operations as well as Events (non-axes controls) and produce another log file, where you load your aircraft and then operate your throttle (using your controller/assignments), then close down and show me the FSUIPC6.log file. Looking at your ini, there re a few things you could change/improve, although not related to your issue. First, you have assigned all your individual POV buttons - from your general [Buttons] assignments: You do not need to do this. You can assign a single POV button press (any) in the axes assignments tab to the axis control Pan View. However, as this is an axis control, you would also need to add this to your profile [Axes.xxx] sections. Your profile sections are also large, as you are using the full aircraft name, instead of substrings. Doing it this way, you have to add each change of livery of an aircraft manually to the profile. Instead, you could use substrings, i.e. change your [Profile.PMDG] section to the following: or maybe even just: John

What FS, version of FSUIPC and aircraft are you using? There are no standard controls for switch guards. You should look into any available lvars, or if its an add-on that comes with its own SDK, there may be custom or rotor brake controls. For MSFS aircraft, there could be hvars or more complex calculator code. As I say, it depends on the FS, aircraft and version of FSUIPC. John

There is no need to attach pictures. If you say the read isn't being logged, then I understand what that means... But what is your actual issue? That the read isn't being logged, or that MF is not seeing/receiving the value? If the latter, then you need MF support. If MF is seeing the value, i.e. it is being read, then the IPC Read logging should log this. So, is MF seeing the value? If not, please try MF support. If it is, I 'm not sure why it isn't being logged, but I am not going to look into this until you confirm that the value IS being read by MF.

Presume you mean offset logging, so you are logging the value in that offset and can see it change. If the offset is being read from an IPC client, then yes, the IPC read should be logged, if IPC Read logging is turned on. I think you need MobiFlight (MF) support, if MF cannot read the value. Your offset logging is showing that the FSUIPC offset is holding the correct value, no? So your problem seems to be with MF not reading the value, for which you need MF support. I do not use and cannot help you with MF. John