John Dowson

Yes, but you need to use a lua script. You need to assign the axis to Send to FSUIPC Offset with Offset Dword Set and use an offset free for general use (e.g. 0xA000). In your lua script, which should be auto-ran (preferably in a profile [Auto] section), you can use the event.offset function which will set a handling function to be called when you move the axis lever, and in the handling function you can calibrate the value (i.e. convert the axis input value, passed as a parameter to the function) to a percentage value, and then set that value in the lvar using the ipc.writeLvar function. It should be straightforward but if you are new to lua and have issues then I can help you with this. See the FSUIPC Lua Library document in how to use these lua functions, and there are plenty of examples out there,

Pete has retired, although he does respond in the forums occasionally. I am sorry but there is no chance of this happening - as it says on the download page for this: The source for this isn't even available for anyone to update. John

I doubt it very much... I suspect so... This surprises me a lot... It would help if you gave an example. All PMDG 737 specific offsets are documented in the Offset Mapping for PMDG document, and all general offsets are documented in the FSUIPC Offset Status document. There just aren't and can't be any other offsets. The only undocumented offsets as such, are those that are used internally or have been allocated to other people or programs. They are usually only documented as "Reserved" or something similar, with the actual purpose defined by the person or aircraft/program they are reserved for (and usually free for general use if not using the program or aircraft they are reserved for). John

This sounds strange - what do you see in the In and Out boxes in FSUIPC's axis Assignment window? Maybe you need to calibrate the axis in windows calibration first? If you want to use scaling to do this, then try with 3=AV,256,F,65919,0,0,0,*-2,-16384 (or maybe *-2,+16384) John

WideClient is the same for P3D and MSFS, and the WideServer component in FSUIPC6 and FSUIPC7 is also the same...are they running on the same PCs? It is also 3 months since you last posted - was it working ok during this period? Can you also please check in the Windows Event Viewer to see if there are any com-related events reported there, and if so show them to me. You also didn't post your WideClient.ini - as I said, I need to see all 4 files from the same session to make any sense of any issues with WideClient connections. Maybe try using different ports to see if that makes a difference, although I doubt it. I will run some tests with WideClient and MSFS here later in the week and let you know if I find anything. What do you use WideClient for on the slave PC? You could possibly try using FSUIPC7 in the client PC instead - see Appendix 4 of the Advanced User manual on how to do this. This doesn't provided the same functionality as WideClient, but may be an alternative option, depending on your use. John

It is not related to your button config. Now you have multiple assignments to throttle 1 & 2: This can be problematic - only have one assignment to each throttle. Assign either to Throttle1 & 2 using Direct to FSUIPC calibration, or to Axis Throttle1/2 set with Send to FS as normal axis. But your issue is because you have calibrated with a reverse zone - try calibrating with no reverse zone if using a button for reverse. Also, can you update to the latest beta (I will release this within the next day or two) as this will help with some other issues I see in your log, available here: John

It probably isn't - I am just used yo seeing two com ports (one virtual) in the VRInsight section, but I guess you aren't using SerialFP2 so this is ok. They are just standard events, nothing to worry about. The event logs don't tell me much unfortunately, just that FSUIPC has hanged. If you don't get the issue when not using LINDA, then the problem is either in LINDA or in FSUIPC's lua script handling. First, continue without LINDA for a while to confirm this. If this is due to LINDA, you are probably better off asking about this on the LINDA support forum. But, before you do this, could you activate Lua Plugins logging and turn off logging for Events and IPC Writes, and show me a log file generated with this logging activated when it hangs,

Compress/zip them. Please try the latest beta release first, link posted in my previous comment.

I need see your FSUIPC7.log file, not the installation log file. Also, please check the windows Event Viewer and see if there are any faults or exceptions reported there, and if so please show them to me. When did this start then? Looking at your ini, it seems that you are only using FSUIPC for LINDA and a VRInsight device, which entry also looks incorrect. Try without LINDA and maybe remove the [VRInsight] section from your FSUIPC7.ini file as well. Also check that you are using the latest version of the PMDG 737

I cannot help with issues with SU12 beta as I do not yet have this installed. Make sure that you are using the latest release (7.3.17), or the latest beta available here: If you get the same issue, please show me your FSUIPC7.log (with lua debug logging activated) and FSUIPC7.ini files, as well as your RAAS lua script. Log and ini files are located in your FSUIPC7 installation folder. If you don't know where that is, use the File->Open Installation folder option from the FSUIPC7 main menu. John

I have still not had time to re-organise my hard disks to install the SU12 beta - I will do this when I get time. I will check the performance in the released version. Maybe try with the WASM disabled to see if this is a WASM or FSUIPC issue. Temporarily remove the WASM from your community folder and then see that sort of FPS drop you see when FSUIPC7 is running.

Yes, strange. But I cannot help if you are not providing the files I requested.

If everything is running at the same privilege level, then you need to contact Pegasus support for this issue, I cannot support third party products. As I have said many times now, I have nothing further to say on this topic. I will leave this topic open so that ither users can post any solutions found for this, but I will not be commenting again on this topic. John

You will not see the same values as written, as the offset status document says: However, you should see the same values in those offsets if writing the same value. Can you please add monitoring to those offsets (in FSUIPC), activate lua debug logging and generate an FSUIPC6.log file showing your issue. Attach that with your lua script and your FSUIPC6.ini file and I will take a look. John

I see no profile for the PMDG 737 in your FSUIPC7.ini file. You should create a separate new profile for this aircraft and also make sure the calibration is profile-specific. Sometimes FSUIPC calibration can cause issue with PMFG aircraft, in which case you should make sure that you have a profile-specific calibration section (otherwise general calibration will be applied) and clear/reset the throttle calibration in that profile. Also check your MSFS assignments - you should either assign in MSFS or FSUIPC7, not both. This sounds like you either have dual assignments (MSFS & FSUIPC) or FSUIPC's calibration is interfering and should be removed. John

I have nothing more to add to what has already been said on this topic... John

When and how often are you seeing these spokes (not sure what you mean by "CPU rendering time")? You can try turning-off the lvar-scanning feature by setting LvarScanFrequency=0 in your FSUIPC_WASM.ini to see if this is the cause, although that should only run at a max of twice per second in the default configuration.

Could this be related to the new feature that scans for lvars and automatically pushed new lvars to WAPI clients? When this happens, all lvars are dropped and reloaded and must be re-registered for a callback (n the lvars-available callback function)? Note also that there is a new WASM/WAPI version available here: You can monitor them manually by just listing them in either FSUIPC7 or the WASM Client application. For better monitoring, you can add them to an FSUIPC offset (using the FSUIPC7.ini [LvarOffsets] section) and then monitor the offsets using FSUIPC7's Log->Offsets feature. John

What has changed? Is it still ok with P3D? If this was working ok, then something must have again changed in your system Network connections issues can be difficult to pin down....I can only suggest that you try the usual techniques - make sure everything is up-to-date, reboot everything, try with girewalls disabled, etc...

Ah, sorry - thought you were talking about 7.3.18b for some reason, not 7.3.17b.... The errors were caused when shutting down FSUIPC7 - this was fixed a while ago but not sure what version, bur should certainly be resolved in the latest beta. Cheers, John

They look to be from 7.3.17 not 7.3.16b (unless I forgot to update the version)....there is also a version 7.3.18c available which you can try, available here: Any issues, please comment on that topic. John

Still a few issues in that version though - please try the latest beta, v7.3.18c (and WASM 1.01, WAPI 1.02), available here: John

Great - glad its all working again! Cheers, John

This should be fixed in the latest beta, available here: John

Ok,, thanks for the update. Glad you found a solution. Are these events in the MF Hub Hop site? I only update the events.txt file on releases - it is up to you, the user, if you want to update between releases. No point sending me the file as I update this from the MF Hub Hop site before release. You can submit them to the Hub Hop site if not already there. A later beta version is available, 7.3.18c, which contains the latest evemts.txt file as of yesterday, available here: John