John Dowson

This is normal for prop aircraft... Sounds like the rudder is far too sensitive. Could you show me your latest FSUIPC7.ini file please. Also a log file with axes controls logged showing your issue would also be useful.

As well as what Pete has said, maybe the axis doesn't need reversing - did you try with the Rev checkbox unchecked? Or are you saying there is no difference to the axis output values regardless of that setting?

So do I! I do provide temporary/time-limited licenses for you to try before you buy...but too late now! Some controls work on some aircraft and not on others, so you need to try them, You can use 'profiles' to have different assgnments to different aircraft. One way to determine what controls are used is to activate logging for events (and also open the log console). If you then click on the UI element you want to control, you should see the event (and parameter) that it is using. You can then try assigning to that. However, be aware that not all events logged from the UI will work when sent via Simconnect (i.e. from FSUIPC). There are various posts both on the FSUIPC (MSFS) forums and in the Asobo forums There is a list of all MSFS provided controls created at run-time, called Controls List for MSFS Build 999.pdf, located in your FSUIPC documents folder. FSUIPC added controls are documented in the FSUIPC User Guide. I just don't have the time or resources for that. Its just me (although Pete helps out when he can), and I have little enough time for development as it is after covering support issues posted on the forum (as well as on the Asobo forums and avsim). For the time being at least, its just easier for me to keep requests in one place, the support forums. John

Have you tried assigning to that event/parameter? Also maybe try the stable or vanilla version - I have had reports of different things working in different versions of the FBW mods. Maybe also check for lvars as these will be available shortly (via lua or macros),

Make sure they are exactly as specified in your purchase email. But if you have previously registered and have a key file, there is no need to re-register. If you don't have your old key file, you can also create it manually. Details on how to do this are in this post:

You can recover your registration details from your SimMarket account.

Try a right click and select 'Save as...'.

Ok - same problem as before, I forgot to add add the extra lines to receive the extra lvar name CDAs. Corrected in this version: FSUIPC-WASMv0.4.9.zip

Which aircraft are you using? Toggle master battery has been reported as working for some aircraft (Baron, Longitude). The ELECTRICAL MASTER BATTERY offset at 0x281C is documented as 'Currently not working for the 747-8: always shows on. Can switch off, but not back on', but at offset 0x3102 it is documented as working for read & write - but it has the same issues as 0x281C.

But 2044 is the maximum. Your CRJ has 1738, and you can see/access/update them. no? Why to you expect there to be more than are available? Is it working ok for you with 1738 lvars? Why do you expect to see more?

Forget about lvars/hvars for now - they are not yet accessible via FSUIPC. But they certainly shouldn't be needed for master battery. Search for existing topics on this please, I'm sure there are already posts on this... and maybe check the offset documentation spreadsheet. Also, please remember, if using LINDA and have issues you need to go to the LINDA forums. I haven't looked at your files as I beliebe @jaxx identified your problem. But if you still have issues, please post again, and also attach your latest files.

Ah, sorry, probably is in a restricted or beta forum.... But we are going off-topic here....this is a discussion topic for the WASM! Please raise another topic for other issues.

Ok, but there is only one version of FSUIPC7 - the payware features are activated by the license, but it is the same as the free version.

Can you please also show me your FSUIPC7.ini file please

First, you posted in the FAQ section, where it explicitly states NOT for Support Requests. I have moved your post to the main support forum. You can use the offset area starting at B000, which uses METAR weather strings. However, you may find it easier to use a 3rd party weather engine to control weather, either free or payware.

No problem. What do you men by this? You can read and write lvars when the sim is paused. However, I have disabled lvar functionality (from the WASM) when MSFS is in a main menu (or aircraft in a parking state). There are some lvars available in this state from the loaded (or partially loaded) aircraft, but there is really no point doing anything with them. FSUIPC detects 3 out of the 4 pause states - still not possible to detect the default 'pause' (but more like an alt/att freeze), but that one really shouldn't be used - even though it is currently the MSFS default pause! I have posted in the Asobo forums on how to detect the various pause and in-menu states via simconnect events, if you are interested check there. With MSFs especially, I find its best not to do anything (via simconnect or WASM) until a plane & flight are already fully loaded, or the results are unpredictable. Another issue is that this state is also very difficult to detect! In the WASM, I have added a delay of 1500ms (can change using the ini parameter LvarScanDelay) which delays scanning of lvars for that amount of time after the 'ready-to-fly' state is deduced. If you increase this (or you can just issue a reload command instead) you will see that you will get a few more lvars than the first time (for complex aircraft) as the aircraft model continues to load and/or change. Ok, thanks.

Ok, thanks. You may get this earlier though as Pete has said he may look into it for you, even though he has "retired"...! I need to allocate the offsets first though, and make a decision as to whether to start re-allocating old offsets (FS9 and before) that are (hopefully!) no longer used... Will keep you informed. John

Yes, this is possible. However, I don't know at the moment when I will have time to look into this. I also have several other pending new feature requests. I'll add this to the list, and and let you know when I come around to looking at this in detail. It will probably be a few months away though, as I've a lot on my plate at the moment with getting lvar access working in FSUIPC7. Once thats done/released, I will start on the backlog of other user requests. Regards, John

As it says in the README, install both x86 and x64 libraries. FSUIPC will need the x64 (64-bit), but best to also install the x86 (32-bit) as well.

As mentioned above, did you click the Register button and if so what happened? If it said your key was valid, then check your installation location - make sure you haven't installed FSUIPC6 under your Documents folder, especially if you are using OneDrive or some other cloud-based storage mechanism for your Documents. If all else fails, you can manually create your key file. Create a file in your FSUIPC installation folder called FSUIPC6.key, with the following contents, substituting the details in bold with those from your SimMarket order:

The splash screen is not related to anything else - it should display that while MSFS is starting. I've really no idea why that isn't working for you, but its not important to the functionality. But there is no such message...can you show me what this message says please. And FSUIPC7 runs ok? What happens when you try to run FSUIPC7 on its own, by double-clicking the FSUIPC7.exe? If you get an error when running FSUIPC, you need to update your VC++ redistributables. See the README.txt provided.

No. Sleep is not a blocking system call, so the script will be killed anyway, as you observed.

A few bug fixes and improvements, and max number of lvars increase to 2044 in this version (now the latest and only supported version, so please update): FSUIPC-WASMv0.4.8.zip @andhogThis also contains a few further corrections for when using > 1022 lvars, so can you please test this and let me know. I have released anyway, as this version contains a few other corrections that need to be released, the main one being that lvar/hvar CDAs were getting confused on a reload.

Yes, it should be killed regardless of whether it is 'sleeping' or not. However, I suspect that if the process is sleeping due to a blocking system call, then it won't be killed before that is returned. This is why there are sometimes issues killing luas that use the com library.

I have moved your post to the specific sub-forum for FSUIPC7. This is because you have hidden known file types in Windows Explorer - see the Addendum on the last page of the Installing and Registering FSUIPC7 manual. What do you mean by this? Can you show me your FSUIPC7.log file please. You will have to follow the advice in the Addendum before you can see this file. Which desktop link - the one FSUIPC7 creates? Do you see the splash screen? Does MSFS start? What needs to shut down - MSFS or FSUIPC7? Also, please don't attach .exe, .bat or .ico files - I have all those! I have removed them. When there are issues, I usually need to see your logs and ini files. Also, for start-up issues, I need to see your EXE.xml, so please show me this file: C:\Users\garyp\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml