John Dowson

See the README.txt file included in the zip file you downloaded. Most likely your VC++ redistributables need updating. John

You should also attach your FSUIPC7.log file for such issues so that I can see what is happening when you load the king air... Well, if you have removed its profile, you will first need to add that back in again or create a new one... Your PMDG B738 profile has the following entry: So that will match any aircraft that has the string RCAF in its title - so the King Air must have that string in its title somewhere.... I suggest you change that to match the B738 and only the B738, If you still have issues, show me your updated FSUIPC7.ini as well as your FSUIPC7.log file created in a session when you load the aircraft that you are having issues with. John

Which folder? What is the time/datestamp on that? Can you attach all 5 files I mentioned in the same post please, even if you have attached them in previous posts. Makes my life easier...!

No...I don't understand why this is so difficult - you posted the correct files in your very first post that started this thread, but since then it has been difficult to get the files from you at the same time. It is not worth me looking at your files when posted in different posts/days as they could be from different sessions, as I can only tell what is happening by looking at the timestamps from the logs, and ini files are re-written when the application closes with the settings used. This is why I need to see all 4 (or 5) files from the same session, and preferably in the same post so that I know they actually are from the same session. The files I always need to see are: From the server/FS PC: FSUIPC7.log, WideServer.log - the FSUIPC7.ini is also helpful From the client PC: WideClient.log, WideClient.ini It also strikes me as strange that you are attaching a WidServer.ini file - where is this from? You should not have one of these, and you certainly don't need or use it.... Is this referring to your WideClient issue or something else? If not WideClient, can you please give more details as this may be related.

Why are you posting that file? As I keep saying, I need to see all 4 files from the same session to make any sense of any issues with WideClient connections. Post all 4 files - well, 5 better, if you include your FSUIPC7.ini, or none at all.

Yes of course - check logging for Events and they will be logged to the FSUIPC7.log file, or Open console and you can see them in real time - although in MSFS you may also see many other events which are constantly emitted by some aircraft. You can use the DontLogThese ini parameter to stop such events being logged - see the Advanced User guide for details. This is the first mechanism to use to determine how to program/assign a physical switch/button to control a VC one.

You posted in a very old topic (2003!) for FS2004. I have moved your post to the correct support forum. Are these knobs axes or buttons? Not sure what you mean by 'console of FSUIPC doesnt recognize them' - do they register in the assignment panels? Either button assignment if the knobs trigger buttons, or the axes assignment panel if they are axes. If you attach your FSUIPC7.log and FSUIPC7.ini files I can take a look, but not sure if I can help with this... I have no knowledge or experience with ELITE hardware. Maybe other users with this hardware can help, or maybe try ELITE support. There are a few other posts on Elite hardware and it seems they use a proprietary protocol and only work with their drivers, so I suspect that you need their support for any issues, But I can take a look at your files. John

FSUIPC4 is already compatible with Windows 11. You are using an old and unsupported version of FSUIPC4, 4.974 - please download and try the current version, which is 4.977. This version of simconnect is not compatible with your version of FSX: Please install the 10.0.61637.0 version of simconnect. John

No, P3D doesn't read or write anything to offsets - they are managed by FSUIPC. The read column indicates if you can read the offset, and if so how it is populated, the write column indicates if you can write to the offset, and if so how that is handled by FSUIPC, with the status keys being defined in the first page of the document.

This is very strange...There is no difference in functionality that is dependent upon when FSUIPC7 is started. Did this happen in previous versions of MSFS / FSUIPC? What was your previous FSUIPC7 version? Are you using any special ini parameters in FSUIPC in FSUIPC for key handling, such as UseKeyboardHook, TrapMSFSkeys or LuaTrapKeyEvent? This is also very strange. FSUIPC receives all keyboard input from either MSFS (by default) or windows (when it has the focus or when UseKeyboardHook is set) and does nothing with the keyboard as a device. Could you show me/attach your FSUIPC7.ini file please. Not at the moment. This is very perplexing and seems to be particular to your system or installation. I cannot think of anything that could possibly cause this behavior.... John

Documentation is installed by the FSUIPC installers, and also available a a separate download from Offset documentation attached.... John FSUIPC Offsets Status.pdf

Ok, strange that caused a latency issue rather than failing to connect altogether. But glad this is now solved, and thanks for the update. Cheers, John

Ok - yes, as the reg profile string bksq-aircraft-analogbaron will be a substring match for the turbo folder bksq-aircraft-analogbaronturbo. The matching is on profile strings to folders, not vica-versa - sorry about that. Glad its working with that beta version - that change will be included in the next official release. Thanks for testing so promptly. Cheers, John

Ok, then you can assign to it directly and don't need to use the lua com library, which is always the easy path... 👍 Cheers, John

Don't you mean that the regular / none-turbo version picks up the turbo profile? I can't see how it can happen the other way around... This is due to the substring matching that is done on the the profile folder name to the actual folder name. There was previously a parameter to define this but this was removed some time ago, before I added the functionality to match on the aircraft folder name. However, it can be useful when using UseAirLocForProfiles=Yes, in situations like this. Can you try the attached version please where this has been re-instated - download it and use it to replace your existing FSUIPC7.exe (make sure you are using the latest release first - 7.3.19, and if not first update to that). Then add the following to the [General] section of your FSUIPC7.ini file: ShortAircraftNameOk=No I haven't tested this yet but will do this later or most probably tomorrow.. let me know if this is ok and solves your issue. Cheers, John FSUIPC7.exe

Note that you can also create your own presets to use lvars (plus hvars, etc) that don't already have a preset listed in the MobiFlight preset list (see https://hubhop.mobiflight.com/presets/). You can also define your own preset (using the myevents.txt file) to take a parameter if needed, otherwise it can be without, as the MF presets are defined. See the Advanced User guide (WASM section) for details. @rlw9srYour log file shows that you are using an old and unsupported version of fSUIPC7 - 7.3.11. Please update to the latest version, 7.3.19. Also, for future reference, please include your FSUIPC7.ini file for issues with assignments (as asked for). Only activate the logging required or asked for (otherwise log files can become too large and contain superfluous info) and always exit FSUIPC7 before attaching files. John

Yes, I know - but I was wondering if it was a joystick type HID device. If so, it would be registered in the FSUIPC4.log file under the joysticl scan section, and would be available for direct assignment via the UI as that is always the easiest methpd to assign. But I guess it isn't. 👍 Cheers, John

To use custom controls, you should select the <custom control> entry from the assignment drop-down menus with Select for FS control checked. No need to manually edit the ini file. If any assignment isn't working, I need to see your FSUIPC7.ini file and your FSUIPC7.log file, the latter generated with logging for Events and Buttons & Switches activated. Make sure the log file is complete (i.e. do not use the New Log feature) and exit FSUIPC7 before attaching the log file). John

No. you are correct to add that back in if you want to have FSUIPC7 to be restarted automatically. Looks like the GSX installer is behaving badly and replacing the exe.xml with its own, whereas it should respect what is there and add its own entry - i.e. just update it to start GSX if already present, otherwise its free to create its own. You should report this to GSX. I have had many issues previously reported about other 3rd party products doing, as well as some corrupting the existing exe.xml so that DSUIPC cannot add its entry - this issue should reveal itself in the log and is documented in the FAQ entry on auto-start. Also, rather than manually add, you can just re-install FSUIPC7. Cheers, John

If the joystick is recognised as a HID joystick type device by FSUIPC, you can use FSUIPCs assignment facilities. Otherwise, it would need a lua script using the com library. But if its working using Python and you are happy with this then probably no reason to switch to Lua. Cheers, John

The license is still available and still valid. I will not be updating it until the 3rd or 4th April. John

That's what I would have thought, but doesn't seem to be the case... Ok

MobiFlight's response: I checked in the sim with the latest FBW A320-Dev and the code for the AP 1 button is (>H:A320_Neo_FCU_AP_1_PUSH) which matches the Hubhop event. I tested with my panel and it works. Just in case, you do need to have a flight plan entered in the MCDU and be airborne for the AP buttons to activate, though. Note the part in bold - was this the case when you tested?

Message back from MobiFlight/Jamie Leon: "I can verify that later today. Thanks for reporting it."

I do not know why you would think that....if I require to see a log or ini file, I will ask for it, and usually with specific logging activated to diagnose your issue. As presets ARE working for you, your issue is with specific presets, which are provided by MobiFlight. I only provide the mechanism that allows presets to be used - I cannot help with specific presets - you need to ask about these with whoever provides the preset, as I have said.... I think that is enough on this topic - I am repeating myself here....