John Dowson

Error 10061 is a windows socket error 'Connection Refused'. Is WideServer enabled and active on the server (i.e. in FSUIPC7? Can you show me your FSUIPC7.log and WideServer.log files as well please. What are you using WideFS for? It is also possible to run FSUIPC7 on a client machine. Depending on your use case, this may also be a solution (and negates the need for the WideServer license). There is an appendix in the Advanced User guide that shows you how to set this up. Other than that, please show me the additional files and I will look into this further, but probably not until Monday now. John

What does this mean? Can you please be more explicit in what you have tried and what occurred, and answer my direct questions. Also attach your updated files, otherwise I cannot help you. I would like to see an FSUIPC4.log file generated after you ran the simconnect installer. Did you try running as admin? If so, where is the log file from this? How did you install FSX? I think you may need to uninstall and re-install using the Steam client. But let me look at the log files first. John

Try the macro file in the first message in that post I referenced, and then assign to the macro:lvar and give a parameter, although I am not sure what the parameter values should be. Try 1 to activate and 0 to turn off, which is standard, and if that doesn't work you can try listing the lvar values (there is a control available for this - List local panel variables) to see how they change when you manually start the ignition and engines. As for your mouse macros, I am not sure why they aren't working. It could be that mouse macros don't work for the FSLabs A32x (not sure, I don't have this aircraft), or that the mouse action (3 - Left single click) is not correct. You could try changing it to use a click followed by a left release, i.e. However, I think you will be better off looking at the custom controls provided by the aircraft. The FSLabs A32x aircraft use the Rotor Brake control with the parameter indicating the actual function. There should be a tutorial on how to use these with FSUIPC on the FSLabs forums - see this post: John

How did you manage that? When you install FSUIPC6, it should detect FSUIPC5 is installed and remove that... You could just remove FSUIPC5, but maybe first try the following: - uninstall FSUIPC6 by using the provided uninstaller (in its installation folder) - then re-run the FSUIPC6 installer -this should detect that FSUIPC5 is installed and uninstall that before re-installing itself Otherwise, you can just remove the FSUIPC5 entry from your DLL.xml file - uf you don't know where that is, the location should be in your FSuipc5/6 installation log files. You can also just rename/remove/delete the FSUIPC5.dll - that will also stop it being loaded! John

But isn't that the same...how else would you maintain airspeed other than using the throttle (with maintaining the same altitude...)...

FYI, I have added the following to the Installing and Registering FSUIPC7 guide, under Invalid Key Problems: This updated document will be available in the next release (Sunday 28th August). John

I was going to release v7.3.8 after the SU10 release, but now this has been delayed I will be releasing this at the weekend, on the 28th. I am updating the installer and documentation at the moment, but the exe itself will be near-enough the same as the latest beta available in the Announcements sub-forum. These are the changes: I am not enrolled in the MSFS beta program (yet!) so do not know what, if any, changes will be required for FSUIPC7. Unfortunately I may also be on holiday around the time of the release. I will review the SDK/SimConnect (and WASM) updates once released. John

Registration instructions are given in the Installing and Registering FSUIPC4.pdf which is included in the zip file that you downloaded. Copy the details exactly as specified in your SimMarket account or purchase email (best to cut and paste). Any problems. let me know your order number and I can check your details here (DO NOT POST your key details!). Note that 99% of registration issues are due to user error, or trying to use a license for a different version of FSUIPC. There can be issues if using unicode (i.e. a non-ascII character set) when you may have to manually create your key file, but I don't think this will be relevant to you... John

Maybe also see this thread - it is for FSX but still applicable: https://www.flightsim.com/vbfs/showthread.php?220563-Autopilot-Airspeed-Hold John

What issues - throttle issues I presume... Looking at your FSUIPC7.ini, you have not tried anything mentioned in this thread... The first thing you should do is create an FSUIPC profile for the Hjet. You will be asked if you want to import the axes to this new profile - you should click 'yes' to accept this. Once the profile is created, exit FSUIPC7 and open your FSUIPC7.ini in an editor. Then remove the following assignments (highlighted in bold) from the [Axes.Hjet] section (or the [Axes.xxx] section where xxx is the name of your Hjet profile): Then add the following section: (replacing Hjet with the name of your Hjet profile). This will map the throttle lvars to FSUIPC offsets. You can then assign your throttle axis to those offsets, which will update the offsets when you move the assigned axis, which in turn will update the throttle lvar values. You can then add appropriate scaling of the values, as the range of the lvars is -1 to +1, whereas the range of your axes values will be -16383 to +16384... if you don't know how to do that, maybe just start by adding the following lines to your [Axes.Hjet] section and we can take it from there: Try that, and any issues please attach your updated FSUIPC7.ini as well as your FSUIPC7.log file. Note that when using lvars for axes assignments, it is a good idea to increase the lvar update frequency by changing/setting the WASM ini parameter LvarUpdateFrequency - this is described above and in the Advanced User guide. John

It looks like your macro is assigned and being called: Maybe you can show me your macro file? But, rather than using mouse-macros, you should first try either the standard controls and/or lvars. From this post, it looks like there are lvars available for both the engine start and the ignition: John

This would be a very complex lua script as it would basically have to implement the IAS hold function of an auto-pilot. Why don't you just use an auto-pilot? If the aircraft you are using does not have an auto-pilot (or the AP doesn't have an IAS-hold feature, which is not all that useful in prop aircraft IMHO), you could look into using the ATIasHold. freeware program - see - main web page here: http://www.intrasystem.it/ATIas/ATIasHold.html : - ATIasHold: Hold the Speed with any Airplane. No need of any Autopilot. Using only the Engine Pressure. John

You have also installed FSX under your Program Files (x86) folder. It is not recomended to install under this folder due to windows permissions/security. In fact, as this is a steam install, FSX should be installed under your Steam folder.... As a test, try running FSX with Admin privileges to see if that makes a difference...

Sorry, I have no idea - there is no functionality for audio control in FSUIPC. I think you would be better off asking this question on the Asobo forums or the forums for the 3rd party software that you are using. Regards, John

Did you try running as admin? What do you mean by this? SimConnect is an API, how can you run this? The fsx_sdk_sp1a.exe file is an installer that should install the SimConnect API version you need for the version installed. HOWEVER , your latest FSUIPC4 Install.log now shows that you DO have the correct SimConnect version installed for your build of FSX: What happens now when you run FSX? Can you show me your latest FSUIPC4.log file please. John

PMDG provide an SDK for many (if not all) of their aircraft, which provide additional data for 3rd party programs by the use of a SimConnect facility called 'Client Data Areas'. This is quite technical, but it enables developers to request additional data for PMDG aircraft by the SimConnct API which is supported by most major flight simulators (e.g. P3D, FSX. XPlane, MSFS, FSW, ...). Unfortunately, althought the 737 for MSFS does have this facility, the actual details of the SDK (i.e. what data is provided) has still not been finalised. I have no partnership or special connection with PMDG (although they have kindly provided me with a license for the MSFS 737-700) but I can enquire about this via their support forum - as can anyone. The FMC pushback looks to be something implemented in the aircraft itself and looks to bypass the MSFS ground services, so the pushback information is not available. They should either provide this additional information via the SDK, or (better) also update the MSFS variables so that the pushback state can be detected. I will report this to them. John

I don't know Volante so can't really comment. but I don't know how a flight can be saved without using the provided SDK function SimConnect_FlightSave - still documented as: NOTE: The current status of this function is NO ERROR, NO RESPONSE.

Can you please be more specific...did you find such a folder an SDK installer and if so what were they called? Did you re-install FSUIPC4 - and if so, where is your new installation log? Did you try using the loader? If so, what happened - and can you show me your FSUIP4.log file from when using that... John

👍

The FSUIPC7 separate documentation package is quite out-of-date at the moment. I will update it in the coming days. For now, to get the latest documentation, download and install FSUIPC7 and just select the Documentation component to install. This will also install FSUIPC7, but you can remove or just not use that if not needed. If using the SDK, it is also better to install that using the FSUIPC7 installer as that will also be more up-to-date. John

What ACARS and virtual airlines system are you using? Have you tried their support first? How is FSUIPC involved? There are now many support topics on ACARS systems with MSFS and FSUIPC7 - try searching the forum to see if any of these previous reports are applicable. Otherwise, please supply more information - ACARS system and virtual airlines software you are using, what you are using FSUIPC7 for with these, and attach your FSUIPC7.log and FSUIPC7.ini files (both located in your FSUIPC7 installation folder). John

It is as documented: The returned value gives the number of bytes actually sent (or at least, placed in the buffer). The com.writefeature function just passes through to the windows HidD_SetFeature function. There are some 'correct size' checks and the passed in size may be adjusted - you can skip this parameter and the correct size should be used (I think!). The returned value will be what was actually written to the device' buffer. You could try logging HID activity to see what is happening. From the Log->Custom menu, enter 0x200. This should then log all HID activity.

Ok, I managed to request pushback via the FMC and I can see that that offset is not changing when using the FMC for this. I am afraid that this needs to be addressed by PMDG. They should either update/use the same simconnect SDK simvars/events or provide this information in their SDK. John

Offset 0x31F0 contains the correct pushback state when requesting/using the MSFS ground services. I am not familiar with how to request pushback via the FMC - if you could let me know I can test that here... John

I have just checked assigning and calibrating as you do for the 747 and it works as expected here. I am therefore wondering if the following button assignments could be interfering: Check your log (when Events logging activated, and maybe also Buttons & Keys) and see if button 9 is beunf detected as pressed and so sending decrease controls. Maybe also check the calibration of those axis in the Windows fame controllers panel to check they are the same there. Other than that, please show me your FSUIPC7.log as previously requested.