John Dowson

Also see John

You should have tried the free license before purchasing, available at the top of this forum. Can you show me / attach your FSUIPC7.ini and FSUIPC7.log files. It is certainly not a good idea to randomly change things that you do not understand.... If your issue is with SkyDemon, have you tried contacting their support? I have been on holiday since last Thursday: As it states on the purchase page - NO REFUNDS. This is why I provide an extended trial license. John

I have not used the freeware SPAD version for many many years, and don't have this installed any more. I will download and take a look, but it will take me a few days before I can get around to this (just back off of holiday). I will update once I have investigated. In the mean-time, could you show me/attach your FSUIPC6.log and FSUIPC6.ini files. John

There may be an lvar - you need to log the lvars and check to see if one looks applicable - lvars are NOT logged with non-axis events. However, if it is a "click-spot", then you should look into using a mouse-macro - see the Mouse Macros section in the Advanced User guide. John

Then you are using FSUIPC7, and should have posted this in the FSUIPC7 sub-forum. II will move your post. Can you please show me/attach your FSUIPC7.ini and FSUIPC7.log files, the latter generated from a session where you experience the issue. John

It would, but there is no way to do this. Input Events are aircraft specific - I just call the sim to ask what Input Events are available, and get a list back, and there is no way to categorize the list returned. P.S. As Input Events are MSFS / FSUIPC7 only, I have moved your post to the FSUIPC7 / MSFS support sub-forum

Different aircraft use different controls/events. You can use the logging facilities in FSUIPC to see what an aircraft is using - for axes controls, just set logging for Axes Controls, open the logging console (Log -> Open Console) and see what is logged when you move the axis in the VC, then use that. Note also that for some aircraft there can be no controls/events that work, and you have to look into other methods of control, such as Input Events or Lvars. John

That is a SIOC error. Try SIOC support. You can post/attach your FSUIPC7.log file and I can take a look for any issues in FSUIPC7, but I cannot help with SIOC issues, sorry. John

Sorry. but I do not understand your question, and have no idea what SLC is. If you are having a problem installing the FSUIPC WASM module, then please show me your InstallFSUIPC7.log file, and also please show me your FSUIPC7.log file. Note also that if you just want to install the WASM for use with another product, you can download and install the WASM without installing FSUIPC7. The stand-alone WASM module is available here: FSUIPC WASM Module 1.0.4 John

As it states in the FSUIPC Lua Plug-ins document, lua filenames have a limit of 16 characters: Also, FSUIPC scans for valid lua files when oy is started and adds any found to a [LuaFiles] section of your FSUIPC6.ini file. There is no such section in your ini file and so no lua files have been detected. John

I can look into making these offsets writeable, but not sure when I will have time to look into this at the moment. For the time being, why not just use the provided FS controls: I can look into triggering those controls when the offset is written but it will be a week or two before I get time to look at this - I will update this thread once I have taken a look. John

As I said, everything needs to be ran at the same privilege level to connect, and always better to run as non admin - only run as admin if you have to, and of do run EVERYTHING as admin. Why don't you try the support forum for FSRealWX? P.S. I am on holiday now, back next Wednesday the 26th.

Don't think so - and I did ask the OP to check this in my first comment: Strange thing is it was all previously working, so not sure what, if anything, has changed...

The log looks fine - FSUIPC is registered but not WideFS (not required unless you are using WideClient in a separate PC): Is FSUIPC actually running when you see this message? If so, FSRealWX may be tied to a specific version of FSUIPC, but I would find this strange as it also supports FSX and P3Dv2-5 so must certainly work with other versions of FSUIPC.. You could maybe try asking about this on the FSRealWX forums. In the key file - FSUIPC.key (or maybe FSUIPC3.key). I really don't think a windows update could cause this. The way 3rd party programs communicate with FSUIPC is the same way in in all versions of FSUIPC and they are still working... No idea what those are... Those are the FSUIPC files - the application (FSUIPC.DLL), your settings, the log file, the installation log and your key file (registration details). John

You can download FSUIPC7 from fsuipc.com or the download section of this forum: Your key details will be in your SimMarket account (if you have lost your purchase email, where they are also given) - and you can also download FSUIPC7 from your SimMarket purchase/order history, and also the SimMarket App. If you cannot find your key details, let me know your order number and I will send them to you. John

It is better to use ServerName, but with the actual server name and NOT the IP address. You can use ServerIPAddr if you like (with the actual IP address of course, and not the server name!), but you should only use this if you are using fixed ip-addresses for your server, otherwise the IP address can change on router or PC reboot.

But that is wrong! As I said previously, 192.168.22.50 is the ServerIPAddr, not the ServerName. Try changing that to the actual name (better), or switch to using ServerIPAddr if using the IP address and not the actual name. John

I do provide manuals for a reason! Did you also correct the ServerName / ServerIPAddr parameter as well, as mentioned? I am downloading windows 24H2 now anyway... John

The documentation did say that 0.0 would be written if the lvar doesn't exist. This is incorrect, and I have updated this now (for the next release). John

Did you try any of the above? I have tested there now and get the same - a drop of roughly 3fps, so I really can't understand why you are seeing such a drastic drop in FPS when using this aircraft. I also tried switching to use VSYNC (at 50% monitor refresh rate) and I get a steady 30 FPS with or without FSUIPC running. John

Is this the z9b version? If not, please download and install that from There is a note on that version that says: so maybe that is the registration issue... John

No idea what could cause this - maybe check any windows logs. Also check that you are running both applications at the same level - if you are running one with admin privileges and the other without, then they will not connect. I have never used or see FS9 or FSUIPC3 - both way before my time I'm afraid, so I don't think I can help you much. You probably don't need a license anyway if just using to connect a 3rd party app (but I am not sure about this). If you attach your FSUIPC3.log file I can take a look but I am not sure there is anything I can do... John

Presumably the PCs running 24H2 and 21H2 are different PCs, and so will have a different configuration. Did you do what I asked, i.e. check your network configuration, firewalls, workgroup name, etc? Did you read the provided documentation and go through the trouble-shooting steps outlined there? If not, can you please do that first and confirm that you have read and checked the steps outlined in the documentation. This is not correct - the colon should be an equals sign, and that is an IP address and not a server name, and so should be (if that is the correct IP address): ServerIPAddr=192.168.22.50 However, usually better to use the ServerName ini parameter instead unless you are using fixed IP addresses. As I said, I am not running 24H2 yet and will check once it has reached here, but I doubt that this is an issue with this release.

License sent via PM. John

Nothing has changed for this in in FSUIPC... Those offsets use the simvar RECIP ENG FUEL FLOW (indexed by engine) which are documented under Reciprical (Piston) Engine Vars as The following SimVars are only valid for piston engines. For non-piston engines, maybe try offsets 0x2060 and 0x2160 which hold the indexed simvar TURB ENG FUEL FLOW PPH. Otherwise, you need to ask about this on the FBW forums. John