John Dowson

March 29

1 hour ago, Francisco Sanchez said:

Unfortunetly, FSLTL ai traffic do not load any traffic. It appears to be connected to MSFS but no air traffic.

I do not know anything about FSTL, but if you think that this is related to FSUIPC7 then you at least need to show me your FSUIPC7.log file. I cannot help you (or anyone) if you are not showing me the information I need to diagnose issues.

52 minutes ago, BillA said:

For me it's the time it takes from aircraft/route selection in the World Map until the aircraft is loaded and ready-to-fly that's taking so long I have to close the sim. Was working fine, then updated FSUIPC. Loaded the sim and the issue started.

Why have you not attached your FSUIPC7.log file?

Can anyone and everyone who has any issue whatsoever, please attach your FSUIPC7.log file. I seem to have to ask for this every time - please get into the habit of attaching this for ANY issue. If you continue to post but not show me the required files you will be ignored from now on - sorry but I am getting pretty fed up with asking for this file numerous times and still not seeing people attaching this...

John

March 29

5 minutes ago, BillA said:

I updated to the latest version of FSUIPC7 and now when loading my PMDG 737s it takes a very very long time to load, I'm talking about waiting like 10 minutes or even 15 minutes to load.

FSUIPC7 has no effect on the loading times of aircraft...
And what loading time are you referring to? The time it takes from starting MSFS2020 until it gets to the main menu, or the time it takes from aircraft/route selection in the World Map until the aircraft is loaded and ready-to-fly?

If you are having connection issues with FSUIPC7, please attach your GSYUPC7.log file. Also try the 7.4.11a beta version posted above and try configuring those recommended ini parameters.

13 minutes ago, Michael DelFranco said:

I just successfully tested with the FSUIPC7 v7.4.11A provided above, with recommended ini settings added .

Your log shows it connected ok but you still had a few failed connection attempts. and you should use:
DetectToConnectDelayAuto=220

i.e. a delay of 220 seconds rather than 190. This is based on the following:

Quote

...

4078 Simulator detected
194094 Trying to connect...
204094 **** SimConnect open event not received in required time limit: Re-connecting now...
204094 Trying to connect...
214094 **** SimConnect open event not received in required time limit: Re-connecting now...
214094 Trying to connect...
224109 **** SimConnect open event not received in required time limit: Re-connecting now...
224109 Trying to connect...
224172 SimConnect_Open succeeded
224172 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
...

which shows that the connection was established roughly 220 seconds (224172 - 4078 = 220094ms or approx 220 seconds) after the FS was detected.

John

March 29

6 minutes ago, pilotguy27 said:

Killing FSUIPC7 and restarting it solves the Simconnect issue for me.....hope there is an update soon....

Please read this thread, try the updated version posted above and tune the ini parameters mentioned above.

This issue seems to be due to the slow start-up process of MSFS. The defaults are tuned for systems that take around a minute between starting MSFS and it getting to the main menu state, If you have a lot of add-ons and your system takes longer than this then increase the DetectToConnectDelayAuto parameter as well as the InitialStallTime parameter.

March 29

I have posted an updated version for you to try in that other thread, together with the ini parameters to try. Please use that thread for this issue going forward - I will close/lock this thread now.

John

March 29

I have only seen one log file for this issue, but that log file indicates that the call to open the simconnect connection is not returning/completing in the required time-limit (5 seconds), and so it is continually re-connecting to try and obtain a connection. Can those experiencing this issue please try the attached version, and add the following to the [General] section of your FSUIPC7.ini file:
DetectToConnectDelayAuto=300
InitialStallTime=30
If you still see lots of messages in the log like this one:

Quote

153547 **** SimConnect open event not received in required time limit: Re-connecting now...

then increase the DetectToConnectDelayAuto parameter until these disappear. Please show me/attach log files if this works or not.

@GNeild Thanks for the log file - please try the attached and use the following (i.e. add to the [General] section of your FSUIPC7.ini file):
DetectToConnectDelayAuto=190
InitialStallTime=10

John

FSUIPC7.exe

March 29

For those experiencing this issue, can you please show me/attach your FSUIPC7.log file and let me know if you are using a Steam or MS Store installed version of MSFS2020. Can you also try exiting FSUIPC7 if you are on the main menu of MSFS2020 and FSUIPC7 still hasn't connected, and restart it manually to soo if it then connects.

John

March 29

10 hours ago, Francisco Sanchez said:

I also attach my log file as requested and hope there is a solution.

Your log shows that FSUIPC7 cannot connect to MSFS for some reason. What happens if you exit FSUI{C7 and then restart it manually when MSFS is in the main menu? Can you try that please and show me the log file.

10 hours ago, Francisco Sanchez said:

1) Where is the new ini parameter? I see only fsuipc.ini file in the main folder.

You add this ini parameter to the [General] section of your FSUIPC7.ini file when needed. I am not sure if this will help, but try adding
DetectToConnectDelayAuto=300

John

March 28

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.

25 minutes ago, Francisco Sanchez said:

Since last FSUIPC7 v7.4.10 update for MSFS2020. I started sim and took a few more time to load main menu.

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).

25 minutes ago, Francisco Sanchez said:

Then When loading a flight and launch FSLTL traffic injector I received the message " Simconnect connection failed : ensure MSFS is open and loaded to or past the Main Menu, trying again in 30 seconds".

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.

25 minutes ago, Francisco Sanchez said:

Once in flight, I opene FSUIPC axes menu and receive the message "Calibration restricted: Please note that as are you not connected to FS, you can only calibrate axes that have been assigned in FSUIPC"

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

March 28

10 hours ago, Cuantreau said:

I tried this version you posted three different times in three different airports, msfs booted and closed and one pc reboot in between. Hotkeys worked each time, thank you so much for fixing now I'm able to use an FSUIPC version grater than 7.4.5.

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

March 27

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

March 27

47 minutes ago, Tuomasi said:

Do you need more logs?

No, not if it is working.

1 hour ago, Cuantreau said:

Something must have been done from v7.4.5 to 7.4.9 because with 7.4.5 (the version I'm using because of hotkeys not working) this problem never happened, maybe John can look that through and regress that mods to make it work again, if this can be done at all.

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

March 27

20 minutes ago, Retard said:

I have tried FSCommander, FlyChrono, Plan-G and smartcars3 which I need for my VA but they do not detect a running simulator.

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

March 27

6 minutes ago, HansW said:

About thge PDF's: I understand your irritation, but the first download of the FSUIPC6 file contained all the manuals and I could print them just as they are, without Adobe.

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

March 27

40 minutes ago, Jaspar11 said:

I have downloaded and will wait for new key

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

John

March 27

23 minutes ago, abh_jc_03 said:

Any reason the switches wouldn’t work?

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

March 27

1 minute ago, abh_jc_03 said:

Why dies one use the send to FSUIPC and other send as FS axis?

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.

Report · March 27

6 minutes ago, HansW said:

So here is the installFSUIPC. file Thank you very much.

But why are you attaching that? As I said, I do not need to see this as you found where the documentation was installed.

6 minutes ago, HansW said:

I saw the Manual Advanced Users: Unreadable signs. Not a textfile. Do you have a tip to change taht?

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:

6 minutes ago, HansW said:

is this the Main Forum?

Yes.

March 27

8 minutes ago, abh_jc_03 said:

Does FSUIPC work with these aircraft?

Yes...

9 minutes ago, abh_jc_03 said:

I can’t get FENIX 320,PMDG737,Aerosoft CRJ and even default 787.

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

March 27

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

Report · March 27

2 minutes ago, HansW said:

In the InstalllFSUIPC file you can read: Skipped etc at the lines of the user manuals.

They are skipped if the same version is already there (i.e. from a precious install).

3 minutes ago, HansW said:

Rest the question of the demo?

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.

4 minutes ago, HansW said:

When I attach the installfile then the Topic is digitally oversized. Do you really nee d the fle?

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

March 27

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:

Quote

// Pedestal - Control Stand
//
#define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER               (THIRD_PARTY_EVENT_ID_MIN + 498)
#define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_DOWN       (THIRD_PARTY_EVENT_ID_MIN + 4981)
#define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_ARM           (THIRD_PARTY_EVENT_ID_MIN + 4982)
#define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_UP           (THIRD_PARTY_EVENT_ID_MIN + 4983)
#define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_50           (THIRD_PARTY_EVENT_ID_MIN + 4984)

and these for the flaps:

Quote

#define EVT_CONTROL_STAND_FLAPS_LEVER                   (THIRD_PARTY_EVENT_ID_MIN + 507)
#define EVT_CONTROL_STAND_FLAPS_LEVER_0                   (THIRD_PARTY_EVENT_ID_MIN + 5071)
#define EVT_CONTROL_STAND_FLAPS_LEVER_1                   (THIRD_PARTY_EVENT_ID_MIN + 5072)
#define EVT_CONTROL_STAND_FLAPS_LEVER_5                   (THIRD_PARTY_EVENT_ID_MIN + 5073)
#define EVT_CONTROL_STAND_FLAPS_LEVER_15               (THIRD_PARTY_EVENT_ID_MIN + 5074)
#define EVT_CONTROL_STAND_FLAPS_LEVER_20               (THIRD_PARTY_EVENT_ID_MIN + 5075)
#define EVT_CONTROL_STAND_FLAPS_LEVER_25               (THIRD_PARTY_EVENT_ID_MIN + 5076)
#define EVT_CONTROL_STAND_FLAPS_LEVER_30               (THIRD_PARTY_EVENT_ID_MIN + 5077)

To use custom controls, please see the following FAQ entry:

John

Report · March 27

2 minutes ago, HansW said:

I installed FSUIPC6 under P3D v4.5.

Then please use the main support forum - you posted in the sub-forum for FSUIPC7 only. I will move your post.

4 minutes ago, HansW said:

All the usermanuals are gone. According the manual the manuals are installed in the Windows Documents Folders. Nothing to see overthere.

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

March 27

@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

March 27

17 minutes ago, Fess_ter said:

Is this a result of FSUIPCs poll rate of the PMDG offsets or is it something in the PMDG code with their broadcast rate that delays outgoing data for a moment?

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

March 27

1 hour ago, Tuomasi said:

I have attached my last two logs running version 7.4.9. Even with the setting DetectToConnectDelayAuto=300

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

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information