John Dowson

PMDG recently fixed the parking brake, but this fix seems to have actually broken it for many users - see this post: I am not sure what they have done (have not had time to look into this in detail yet), but I certainly cannot change the functionality at offset 0x0BC8 as that is a general offset for all aircraft. For now, I suggest you check the PMDG forums for information about this issue. I will look into this further when time permits... John

It is the same offset in FSUIPC7 - 0x05C4, and is also read-only. To set the frequency, you need to use the appropriate control/event (or maybe preset, depending on avionics). Usually you would set the frequency by inc/dec of the current (standby) frequency, and the inc/dec controls should inc/dec through the 8.33KHz spacing.

That is an output preset - i.e. it returns a value, and does not actually do anything. For assignments, you need to restrict to input presets. John

Use the MobiFlight HubHop server to search for presets: https://hubhop.mobiflight.com/presets/ This is documented in the Advanced User guide. John

Well, it can be made available, by looking at the value of 3 simvars: CIRCUIT SWITCH ON, BUS LOOKUP INDEX and BUS CONNECTION ON. If needed, you can add them to free offsets, and use a lua script to update a fourth/fifth offset with the actual avionics master 1/2 state when any of those change. John

This will almost certainly depend on the aircraft that you are using, i.e. will be different for each aircraft (use profiles). Try searching for a preset for separate avionics on https://hubhop.mobiflight.com/presets/ for the aircraft you are using, and you can then assign to these by checking the Select for preset checkbox. If you look at the code for the preset, this should indicate the lvar which holds the individual avionics states, and you can add these lvars to an FSUIPC offset if you want to read the state. John

You can use the mouse-click parameters instead - a left/right click should inc/dec. Otherwise there is also probably a preset available for this - you can search for available presets on https://hubhop.mobiflight.com/presets/, and presets are available for assignment by checking the Select for preset checkbox. John

Yes, I have checked further and it shouldn't present any issues. However, it will increase the time taken to read the buttons section, although this shouldn't be an issue. I may move this setting to an ini parameter if I get time - I will let you know if I do this before release. John

Yes, if it isn't causing any issues....

Thanks Ray!

You say it works fine with MSFS - is that running on a different machine (i.e. not on FSXCOMPUTER)? Your problem looks like a firewall issue blocking the connection on port 8002 (or something else is using that port). But if that is the case, I don't understand how you got that successful connection I showed you in an earlier post. Can you please try with all firewalls disabled (client, server and also on any routers) to check this and rule this out. Also please check all PCs are in the same windows workgroup. What version of windows are you running an your various PCs? John

That is a very old version of P3D and is no longer supported by FSUIPC. You need to update P3Dv4 to a later version. The minim version for FSUIPC6 is 4.3 (i.e. latest version only) and the minimum version for FSUIPC5 is 4.1. John

Thanks Ray - presume that is this post: https://www.avsim.com/forums/topic/628812-installing-rcv4-on-my-new-build-computer-running-p3d-v53. There doesn't seem to be a solution posted there, and the OP said ' with instructions which I have tried but with no luck'. The dll and instructions are available here: https://appuals.com/how-to-fix-msstdfmt-dll-is-missing-error/ Maybe @Jlinckecould post his solution, for others who have the same issue and come across this post. Thanks, John

For the PMDG aircraft, using the Rotor Brake control, you can only send mouse operations as the parameter. Rather than using the Rotor Brake control, you can use custom control numbers instead. Using these, you can also use mouse operations as the parameter (for parameter values >= 0x2000 / 8192) but you can also set the value directly, when the parameter is < 8192. See For the Fenix, looking at the presets they are using lvars, not Rotor Brake controls, so you won't see anything logged. You need to list the lvar values, and see how they change when you operate the switches in the VC (i.e. list the values before and after you operate a switch). If you know what lvars are being used, you can also add those lvars to a free fsuipc offset, and use FSUIPC's offset monitoring facilities to log the lvar changes. I don't have the Fenix, so can't help much further with that - you can use the MF HubHob site (https://hubhop.mobiflight.com/presets/) to see the calculator code for the presets which should tell you how they are implemented - with lvars, hvars or controls/events. John

Maybe...I am not 100% sure about any side-effects of this change, but I have updated to allow up to 9999 in the attached beta version, 7.3.16c. Please test this and let me know if ok or not - if not, then I will reverse this and look in more detail when time permits, but this will be very low priority. John FSUIPC7.exe

I cannot open those files - I get a data error. And why is the log file so large anyway? If you are just logging Buttons & Keys and Events, loading an aircraft and pressing a few assigned keys (which aren't working, and then exiting, the log file should be no where near that size. So can you please try again, and just use the default windows Compress to zip file option to compress.

You should never modify the [LuaFiles] section - that section is maintained by FSUIPC. But ipc.control does not have an offset parameter, only one for the control number and one for the parameter to the control. John

As I said, I will renew the trial license next week, on Monday 9th...

Please see this post/comment: If the UserCfg.opt file cannot be installed, you can try and correct this, but this only means that the WASM module isn't installed. You can extract the WASM module by unzipping the following file: C:\FSUIPC7\SDK\FSUIPC-WASM.zip, then unzip fsuipc-lvar-module.zip and copy the folder fsuipc-lvar-module to your MSFS Community folder. John

Neither is fail! I will generate a new trial license next week. John

compress/zip it and then attach.

I think these things can depend on the shell being used....e.g. command prompt vs windows terminal vs power shell....

The FSUIPC4.log file you posted is a continuation log, and so useless. Please only attach full log files for support - don't ever start a new log file. Well, you did say ' I've hardcoded the address inside the wideclient.ini file to specifiy 192.16.1.3.' (should be 192.168.1.3) but the WideClient.ini does not show this, and the logs you are posting show it is trying with the address 192.168.1.100. And as I stated in the previous post, your log showed an initial successful connection to the 192.168.1.3 address. I don't understand this....the log files are created on start-up, although some buffering (by the OS/Windows) may occur before they are actually written to disk, So, can you please set the ServerIPAddr in your WideClient.ini and try again, Reboot both server and client machines before you re-test. And if it still fails then show me all the necessary files (complete, not continuation) which are your FSUIPC log and ini files, your WideServer.log file, and your WideClient log and ini files - all from the same session. Also, please check your Windows Event viewer to see if any network events/failures are reported. Maybe also try running the windows network diagnostics tool(s) to see if they report anything. Your issue is related to your network set-up, not FSUIPC or WideFS. Check the installation of the network cards and your cable(s), and maybe any network logs if you have any/can find them. John

For you, no! You asked for an update of the trial license on 31st May 2022, so you have been using the (trial) licensed version for over 6 months. I provide a trial license for users to see if FSUIPC7 is suitable for their needs. If you are still using FSUIPC7, you should buy a license, not continually use the trial license provided. As people are now doing this, I will be leaving longer periods where a trial license isn't available, to prevent such practices. John

What is PF3? I do not have the time or knowledge required for this. Another million? No where near making the first one....! I will look into using RC4 with MSFS at some point, but I am afraid that this is low priority. I am currently spending most of my time on support issues, and find it difficult finding time to add new functionality to the existing products I support.... John