John Dowson

First, you posted in the main support forum, Please use the sub-forum for FSUIPC7 if your issue/question is with this product, I have moved your post. FSUIPC7 has practically no influence on how log it takes MSFS to start-up and load to the main menu. However, in the latest version there is a delay between when FSUIPC7 detects that MSFS is running and when it attempts to connect. The default for this value is 60 (seconds), and can be adjusted by using the new ini parameter DetectToConnectDelayAuto (or DetectToConnectDelay if starting manually, which has a default of 1 second). Is that a 3rd-party app that connects to MSFS or to FSUIPC7? Sounds like it is trying to connect to MSFS, which has nothing to do with FSUIPC7. That indicates that FSUIPC7 could not connect to MSFS. Can you please show me/attach your FSUIPC7.log file please. As you are a new user you will have a restricted limit for uploading files, so you will probably need to compress/zip this file before attaching. Also please make sure that you exit FSUIPC7 before attaching the log file. Also attach your FSYUPC7.ini file (better in a separate post, and also zipped/compressed if too large). John

Great - glad this has finally been fixed! I have released this now (7.4.10), and this will be the last update before the SU15 release. John

I think I may have found the issue... When the reconnect is started, the old connection wasn't being closed, and so some data was being received from the old connection, including the setting of various flags relating to the state of the connection, so the new connection wasn't being initialised correctly as the delayed response from the previous connection had confused things. I have corrected in the attached if people experiencing this issue can try it (especially @Cuantreau who is still pm 7.4.5). For those who have adjusted the DetectToConnectDelayAuto ini parameter to resolve their issue, you should remove this when testing this version, although probably better to add that back in afterwards (although shouldn't actually be needed/neccessary if this fix works, but still better to use this due to unrelated connection number issues). Please attach a log file if you get the same issue - preferably with logging for Extras enabled. John FSUIPC7.exe

No, not if it is working. A lot has changed between 7.4.5 to 7.4.9, and the changes were done to improve the start-up/initialisation process due to other reported issues, which were fixed by these changes. It is not possible to isolate any specific change that has caused this issue, especially as I do not and never have had this problem. Looking at the logs. this seems to be related to re-connection issues which is why the current solution is to delay the initial connection until MSFS is actually ready to receive and process the requests. I will continue to investigate to see if I can find a better solution, but it is very difficult as I cannot reproduce here. John

They cannot connect to the simulator as they are running on your client PC, where only WideClient is running. Do they connect to the FS or are they FSUIPC client applications? Your log shows two of these apps connected to WideClient: 13859 New Client Application: "FSC" (Id=1420) 108562 New Client Application: "FlyChrono" (Id=12096) so they are connected. Do they not work? Note that you must have a plane loaded and ready-to-fly for the WideServer component to be started, i.e. they will not work when MSFS is in the main menu. Note also that the run programs in your ini are commented-out (preceded by a semi-colon) John

The manuals are always included in the installer and are installed as long as they have not been deselected from installation. I really don't understand the issues you are reporting with this. Can you not open the Advanced User manual pdf? You don't need Adobe, but you do need a pdf reader and always have. Most browsers can also open pdf files, but I use Foxit. John

Don't wait for the new key file - use the current one for now and download and use the new one when available. John

What switches and for which aircraft? Many of the standard controls don't work in MSFS, especially for add-on aircraft. You need to look into using other methods. For most aircraft, you should look to see if there is an appropriate preset defined - use the HubHop site (https://hubhop.mobiflight.com/presets/) to search for the function/button by aircraft/aircraft provider. All presets are available for assignment in FSUIPC7 by checking the 'Select for Preset' checkbox. You can then click the Find Preset... button which will open a tree-dialog that should allow you to easily find the preset. For PMDG aircraft there may be presets available, but you can also use the custom controls. To use these, please see the following FAQ entry: Almost all buttons/switches in PMDG aircraft can be controlled using the provided custom controls (take a look at the header file where the custom controls ae defined). You can also try looking at Input Events for some functions, although not all aircraft support these, You can list the input events available using Log -> Input Events. You can also see these being used, and the parameter to be used (if any), by activating logging for Input Events (Log->Input Events) and then clicking the button/switch in the VC. In fact logging is the mechanism to determine what to use for a button/switch assignment, especially with Event logging activated (Log->Events). If you open the logging console (Log->Open Console) you will see what events are used by a button/switch in real-time when you click/press the button in the VC. If you have any issues with a specific button/function in an aircraft, you can post again. Check there isn't a post covering this first, and give your post an appropriate title (i.e. include the aircraft name and provider if not Asobo, and the function you want to control). John

They are just different ways of assigning, and only the standard axis controls are used when sending direct to FSUIPC calibration, i.e. you cannot use the *_EX1 controls with this, for example.

But why are you attaching that? As I said, I do not need to see this as you found where the documentation was installed. Sorry, but I do not understand this. All manuals are pdf files, not text files. You need a pdf reader to open them. John Sorry, missed this: Yes.

Yes... But what have you assigned to? You need to assign to the controls that work for the aircraft that you have loaded. I don't have the Fenix, but for the: CRJ - assign with 'Send to FS as normal axis' and use the THROTTLE1_AXIS_SET_EX1 and THROTTLE2_AXIS_SET_EX1 controls (or THROTTLE_AXIS_SET_EX1) PMDG737 - the standard Throttle assignments should work with this aircraft, assigned using send to direct FSUIPC calibration default 787 - the standard Throttle assignments should also work with this aircraft If you cannot get the throttle working for a specific aircraft. please show me/attach your FSUIPC7.ini file and the FSUIPC7.log file, generated with logging for Axes Controls activated - just load the aircraft, move the throttle through its full range and back again, then exit FSUIPC7 before attaching the files. John

The key expires. You should download and try now, but the licensed facilities will stop working on the 2nd April. I will post a new key on the 2nd or 3rd April, so just download and install the new/updated key file once I have updated it and then you can continue with your evaluation. John

They are skipped if the same version is already there (i.e. from a precious install). No idea what this is, There is only one version of FSUIPC6, no demo version. The same version can either be licensed or not, depending in whether you have a license and have registered it, which you have. I don't need to see it if you have no problems. Note that, for future reference, you can always compress/zip text/log files before attaching them. You will have a low upload limit being a new user to these forums, but this will increase as you post. John

All key press assignments will "work", i.e. they will send the assigned control to the FS. What may not be working is specific controls in the PMDG aircraft - you need to use the custom controls. So, for example, these are the custom controls for the spoilers/speed brake: and these for the flaps: To use custom controls, please see the following FAQ entry: John

Then please use the main support forum - you posted in the sub-forum for FSUIPC7 only. I will move your post. The manuals should be installed in a subfolder called FSUIPC6 of your Windows Documents folder. The InstallFSUIPC6.log file should tell you where they were installed and if there were errors - check that and post/attach it here. John

@Tuomasi Please try the attached version(7.4.10d) with DetectToConnectDelayAuto=375 In this version i have updated to allow a maximum value of 500. John FSUIPC7.exe

There is no poll rate of the offsets, and all offsets are treated equally by the event.offset function. What would be different would be the update rate of the offsets. Most standard offsets are populated and the sim visual frame rate, whereas the PMDG offsets are populated when the PMDG (client) data is received/broadcast from the aircraft. I therefore suspsect that this is related to the data broadcast rate if the PMDG client data. I can do some testing here at some point to check this, but I am not sure when I will have time to do this as I have quite a backlog at the moment... John

But that is a new ini parameter not available in 7.4.9. Please download the latest beta, 7.4.10c - attached above, and try again. A value of 300 might not be enough for your installation, looking at your log files. Looks like you need a value of 375, but this is currently not possible. Try with 300 first, and if that doesn't work let me know and i will change the maximum value to 500. john

Ok, then you can use the presets G58 Fuel Boost Pump R Switch Off G58 Fuel Boost Pump R Switch Lo G58 Fuel Boost Pump R Switch Hi I am not sure why there are not similar presets for the left pump, but you easily add these by adding the following to your myevents.txt file: //Black Square/Baron G58/Fuel G58_Fuel_Boost_Pump_L_Switch_Hi#1 (>A:CIRCUIT SWITCH ON:4, Bool) 2 (>L:var_FUEL_Switch_Pump_1, number) G58_Fuel_Boost_Pump_L_Switch_Lo#1 (>A:CIRCUIT SWITCH ON:4, Bool) 1 (>L:var_FUEL_Switch_Pump_1, number) G58_Fuel_Boost_Pump_L_Switch_Off#0 (>A:CIRCUIT SWITCH ON:4, Bool) 0 (>L:var_FUEL_Switch_Pump_1, number) Maybe, but this is the FSUIPC support forums and therefore I need to show how this can be assigned in FSUIPC for other users who come across this, not how to assign this is using Spad.Next. Anything that you can assign in Spad.Next, you can also assign in FSUIPC. John

Yes - I will ask about this on the Asobo forums. John

No idea, sorry. FSUIPC relies on the simconnect functions to load/save a flight and has no control over what is actually saved and loaded. You could try reporting this to either Asobo or Fenix. However, also note that the function used to save a flight (SimConnect_FlightSave) is still documented as 'NOTE: The current status of this function is NO ERROR, NO RESPONSE', which is Asobo's way of saying that this function is still not working correctly. John

But why did you even try with 105? That was the value I determined for another user based upon his log file. Looking at your log file, the value you need is around 240. As I have said, I will create a FAQ entry on how to determine the value needed. Basically you need to look into the log and find the timestamp of the detected log message: and then find the last 'SimConnect_Open succeeded' message, which from your prev log is this: The difference between those two timestamps is 241.359 seconds, so 240 is a good starting value for this parameter for your installation. John

Ok, that is interesting. So it seems that the installer is picking up the environment variables from an 'Admin' account, rather then the user's account. I think the admin privileges are only needed for the registry update and not the installation itself. I will see if I can update the installer to either not request admin privileges, or to only request for the registry update and not for the other parts of the installation process. John

The default values will be the same as in the current release - 60 (seconds) for DetectToConnectDelayAuto and 5 (seconds) for DetectToConnectDelay. Both ini parameters will have a maximum value of 300 (seconds) and a minimum of 1 (second). I will also create a FAQ entry on how and when to adjust this value from the default. John

I have checked these now (in the Asobo G58). The FUEL Pump 1 and FUEL Pump 2 input events work with a parameter of 2 for off, 1 for lo and 0 for high, The deice input events all work with a parameter of 1.0 for on and 0.0 for off. John