John Dowson

If they are listed like that, then they are just individual lvars as far as FSUIPC is concerned and you can use either method. Btw, why are you using the WASMClient? You can do everything this app does directly in FSUIPC using the Add-ons->WASM menu. Cheers, John

Thats not an issue - it is just informing you that the WideServer component is running in FSUIPC and is waiting for any connections from a WideClient. However, if you are not using WideFS, you can disable WideServer in FSUIPC if you want to. John

There are a couple of things wrong with this... First, you need to determine the maximum and minimum values that the L:ENG THROTTLE 1/2 lvars take - is it really the same as your axis value range, which is usually -16384 to +16383. Secondly, you are storing the lvar value as 1 unsigned byte, which can only hold values 0 to 255. You should probably use 4 bytes, and also use the corresponding offset set function. But if your axis range is different from the lvar range, you need to calibrate the axis value first and so need to either use axis scaling or a lua script to read the axis value, calibrate it and then set the appropriate value to the lvar. I did show how to do this using axis scaling (different aircraft, in this thread: However, an easier method would be to define your own preset in a myevents.txt file and then assign your axis to use the preset. I also showed someone how to do this in this post (again, different aircraft and lvars but same principle): The preset method is probably easier, but you can use either. Any issues, let me know the lvar's range as well as your throttle axis range if you need further assistance. John

First, you posted in the Announcements sub-forum, which explicitly states NOT for support requests. I have moved your post to the FSUIPC7 support sub-forum. Please see http://fsuipc.com/ - in summary: FSUIPC7 is for MSFS2020 only. FSUIPC4 is for FSX / FSX-SE and P3D v1,4-3.4 only. FSUIPC6 is for P3D versions 4,5 & 6 only. I do not provide any software for XPlane - that is XPUIPC which is from another developer. There is no issue installing the different versions of FSUIPC on the same PC. just as there is no issue installing different flight simulators on the same PC. FSUIPC4 is always installed in a folder called Modules under the main FS folder. For FSUIPC6 and FSUIPC7, you choose the installation location yourself, and you can install anywhere you like, although it is not recommended to install under a windows-protected folder such as Program Files (or Documents). John

That is interesting - I didn't know that lvars could be indexed.... If you list the lvars (Add-ons->WASM->List Lvars) do you see them individually (as indexed) or just see B787_IRS_KNOB_STATE? In the case of the former, you can just use the ipc.writeLvar function. In the case of the latter, you can try with the ipc.execCalcCode function, e.g. ipc.execCalcCode("0 (> B787_IRS_KNOB_STATE:1)") ipc.execCalcCode("1 (> B787_IRS_KNOB_STATE:1)") ipc.execCalcCode("0 (> B787_IRS_KNOB_STATE:2)") ipc.execCalcCode("1 (> B787_IRS_KNOB_STATE:2)") John

What does this mean? What has this got to do with FSUIPC7? What have the engines got to do with the G1000? What aircraft are you using, or is this an issue with all aircraft? Do you actually want support, or is this just some sort of random observation? If the former, please explain your issue and provide more details. In the case of the latter, please refrain from posting here. John

You can try using your FSUIPC6.ini file - just copy it to your FSUIPC7 installation folder and rename it to FSUiPC7.ini. Also, delete all of the settings under the [General] section and let that get rebuilt. You may need to keep some parameters (or set them again afterwards) if you have manually changed anything (such as profiles in separate files), but best to start with a clean [General] section. If using the PMDG 737, then most, if not all, of the custom controls should be the same. However, the PMDG-specific offsets have changed so you should check those if using them. You may also want to revise the aircraft names in the profile section, if using profiles, as the aircraft names may not be the same. You can add MSFS aircraft to your profiles via the UI, but you may want to manually remove any P3D-specific aircraft. John

Ok, then this implies that one of your weather files is corrupt. To correct this, delete all of the .wx files from your FS Documents folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX. Once you have done that, you can remove the NoWeatherAtAll=Yes entry from your FSUIPC4.ini file and try again. For other issues, please raise a new topic, with a relevant title. You cannot use this same topic for all issues. Please also check for similar issues before raising a new topic. FSUIPC does not send anything, it will be the acars program that reads the state data from FSUIPC. The acars program is probably trading the beacon light state either from offset 0x281 or offset 0x0D0C. You can try logging those offsets to see if they hold the correct state of the beacon lights for the aircraft you are using (see the User guide on logging facilities and the Offset Status guide for details on those offsets). Other than that, I cannot help with 3rd-party programs that I do not know. You should try the support for the acars program. John

Ok, then the min is not exactly at 20%, You could try adjusting the scaling to get this corrected, but will be difficult to do without knowing what the axis value is at this position. No need if its working, and especially not if the axis values are not being logged. I have made a note of this and will look into this when time permits. I am rather busy at the moment... John

Ok, forget the logging for the time being - it looks like the THROTTLEn_AXIS_SET_EX1 controls are not being received back from MSFS, and so cannot be (post) calibrated and are not logged (checked in the ATR which also uses these controls). Remove the calibration, assign to the correct THROTTLEn_AXIS_SET_EX1 controls and try the axis scaling I proposed in a previous post. John

First, your log file is not a complete log file, it is a continuation log file. As I said, I need to see a complete log file, i.e. do NOT use the New Log feature. Second, your assignments are not correct: You have assigned to Throtte1 and Throttle2 and not THROTTLEn_AXIS_SET_EX1 - did the throttle even move with those assignments? I need to see a log file with the throttle axis logged. You can check this in real-time by keeping the console window open. No point in posting either incomplete logs or logs without the throttle movement being logged. Anyway, try with the scaling, as advised. Any issues, repost a more useful log together with your updated ini. I do not have the BAe-146 so need to see these file in order to understand what is happening. John

To try with axis scaling, remove any calibration (click the Reset button in the calibration tabs) and with FSUIPC7 not running add the following to the end of your axis assignment line (highlighted in bold): That should scale a 20-100% axis range (-9830 to +16383) to the full axis range (-16384 to +16383).

License sent via PM. John

Checked here and still no issues - throttle stays full and HUD shows 100% on both engines. Please show me your files as detailed in my previous comment. John

You can also try unchecking the NRZ checkbox in the calibration tab, which should allow a value of -4096 to be sent (rather than 0) when the throttle is in the min position. That should move the throttle down further, but probably not to the min position. If you can determine what the min position value is, we can skip calibration and use axis scaling instead...

Before exiting, could you move the throttle in the VC down to the min position so that I can see what value it is using for this position. Thanks.

Can you first check that you are using the latest version of FSUIPC7 (7.3.21) as calibration when using Send to FS as normal axis was disabled for a time in earlier versions. If you get the same issue, please activate logging for Axes Controls and Extras (no others), and generate a short (but complete) log file - load aircraft, move throttle to max then back to min then exit FSUIPC7). Then show me/attach your FSUIPC7.log file, together with your FSUIPC7.ini file.

You keep attaching your FSUIPC4.ini file, which just tells me that you have not added: NoWeatherAtAll=Yes to the [General] section of this file and tried with this, as I keep asking you to do. Please try that. If it still crashes, please attach your FSUIPC4.log file, and also check the windows Event viewer and post details of the crash events.

There are 3 things to try: 1. When assigned with Send direct to FSUIPC calibration, did you calibrate? If not, try that, and make sure you have checked for NRZ. If using protiles, also make sure the profile box is checked in the calibration tab. 2. You can also try calibrating (inc. reversing) when using Send to FS as normal axis. 3. Some aircraft don't play well with FSUIPC calibration, mainly some complex add-ons. For such aircraft its best to not calibrate. Note that the default calibration section will apply if there is no profile-specific calibration section, so best to create a profile-specific calibration section and Reset (i.e. remove) the relevant throttle calibration. To reverse the axis, you can then use the Additional parameters to scale input axis values functionality (see p43 of the Advanced User manual), by adding ',*-1' to the axis assignment line in your FSUIPC6.ini file. John

Try using FUEL_SELECTOR_OFF (65955) instead of FUEL_SELECTOR_SET (65962) in assignment line 62. If that doesn't work, let me know and I will take a look in more detail. John

You should be able to do this in the FSUIPC7 calibration tab. Just set the lower limit at your throttle 20% position. Any issues I can check tomorrow - I am travelling today. John

I have PM'ed you a trial license. John

Well, not that patient... I am actually on holiday at the moment, a family wedding, flying back home tomorrow... In the zip file you downloaded that contains the installer, there is also an installation and registration guide. This tells you where everything is installed. The documentation is installed in a folder under your Windows Documents folder, in a sub-folder named FSUIPC6. Start with the User Guide. There is also a separate document for the specific offsets for the PMDG 777, but save this for later. Axis assignments for the PMDG 777 should be straightforward, but best to assign with 'Send to FS as normal axis' as some folks have issues when assigning with Send direct to FSUIPC calibration, although the latter is better if you don't have issues. For button/switch assignments, PMDG aircraft use their own custom controls. See the following FAQ entry on how to use these: John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for support. I have moved your post to the main support forum, where it belongs. Please see the provided documentation - I provide extensive documentation so that I do not have to continually answer such basic questions. Read the documentation and try assigning as indicated in the documentation. If you have any specific questions, you can ask in the support forums - but please search the forums first, as most questions have already been asked and answered. John

All offsets are documented in the FSUIPC Offset Status document. The ones you can use are documented as "Free for general use" in this document. The offset area starting at 66C0 is free for general use and is 64 bytes in size. it is up to you how you use this - you can divide this up as you see fit. Just remember that you need to respect byte boundaries, so if you are storing a 2-byte integer (short), then that needs to be on a 2-byte boundary (i.e. last digit must be 0,2,4,6,8,A,C or E), a 4-byte value (e.g. int) must be on a 4-byte boundary (last digit must be 0,4,8 or C), etc. There is no maximum - you can use all of the offset areas designated as free for general use. You can also use any offset area allocated to 3rd-party aircraft or utilities that you do not use, e.g. you can use the PMDG offset area starting at 0x6420 (512 bytes) if not using PMDG aircraft or the PMDG data broadcasts. What do you mean by 'generate errors'? If an lvar value can be stored in a byte (in range 0-255 or -127 - +127) then you can store in consecutive bytes. However, all lvars are, by default, 8 bytes - although you can treat/convert them to byte values (usually for Boolean 0/1) or 4-byte values (for standard integers), but would usually need 8 bytes for storing floating point values. So the size of the offset would be dependent on the data that it is holding. So, for example, to store 4 lvars that hold integers, you would use (for example) 0x66C0, 0x66C4, 0x66C8 & 0x66CC.