Binding key, not working-MSFS

[martynahubert]

Hello.

I had to reinstal FSUIPC 7 because didn't want start with MSFS, even If I tried launch seperate, I don't know what happened and now I try bind keys landing lights and taxi for PMDG 737 but not working,

All previous version worked normally.

I use newest, payware version.

Regards Maciek.

 

 

FSUIPC7.log FSUIPC7.ini

[John Dowson]

Your file shows that FSUIPC could not connect to MSFS:

Quote

     1250 Auto-started via EXE.xml with DetectToConnectDelayAuto=60, InitialStallTime=20
     1250 **** Auto-start tuning is active
     3344 Simulator detected
    63344 Trying to connect...
    83360 **** SimConnect open event not received in required time limit: Re-connecting now...
    83578 Trying to connect...
   103578 **** SimConnect open event not received in required time limit: Re-connecting now...
   103797 Trying to connect...
   123797 **** SimConnect open event not received in required time limit: Re-connecting now...
   124016 Trying to connect...
   144031 **** SimConnect open event not received in required time limit: Re-connecting now...
   144250 Trying to connect...
   165156 Failed on SimConnect_Open for AI Traffic Client, return = 0x80004005

Nothing is going to work if it can't connect.

I don't understand why it can't connect, or why it didn't log another 'SimConnect open event not received ...' message at 164250 and try again. Did MSFS reach the main menu stage, and if so how long does this take?

Can you reboot your PC and try again. If FSUIPC again fails to connect by the time MSFS is in the main menu, exit FSUIPC and show me the log file again (please always exit FSUIPC7 before attaching files). Then restart FSUIPC7 manually - does it then connect or not?

[martynahubert]

As You adwised, I rebooted computer and everything works as it should, unfortunately I can't add the log file because it is 16 kb in size and maks total size can be 14 kb as You know  and by the way, I can't find it anywhere bind key for runway lights, has not been added or are you planning to in the future?

[John Dowson]

1 hour ago, martynahubert said:

As You adwised, I rebooted computer and everything works as it should,

Ok - when you get strange connection issues, ir is normally down to windows and a reboot us needed,

1 hour ago, martynahubert said:

I can't add the log file because it is 16 kb in size and maks total size can be 14 kb as You know 

The upload limit is rather restrictive for new forum members - it will increase as you post more. You can also zip/compress the files as they reduce very well, but no need to see your files if its working.

1 hour ago, martynahubert said:

I can't find it anywhere bind key for runway lights, has not been added or are you planning to in the future?

FSUIPC provides access to all FS controls (and more) - there just aren't any for the PMDG 737 runway lights, You can use the available presets though, by checking 'Select for Preset', then click the Find Preset... button and navigate to the PMDG 737 presets. You can also use the MF HubHop site to search for presets - the following are available for the runway lights:

For PMDG aircraft, you can also use the custom controls provided by the PMDG SDK - see the following article on how to use these (although many are available via presets, but not all):

John

[martynahubert]

ok, everything is clear, thank you very much for your help.

Regards.

Maciek

[martynahubert]

Hello

Yet, still is problem. sometimes after once rebot PC , Fsuipc work  but tonight I reboted PC 3 times and nothing then I tried restart manually Fsuipc but not launching

[martynahubert]

FSUIPC7.log

[John Dowson]

13 hours ago, martynahubert said:

I tried restart manually Fsuipc but not launching

What do you mean by this? Do you not see the FSUIPC splash screen when FSUIPC starts? Can you not see the main window after pressing Alt+F?
The log file you attached is again showing that FSUIPC cannot connect to MSFS. But I don't understand why it stops after 4 attempts.

What other add-ons are you using?

Once MSFS starts, how long does it take to arrive to the main menu state? Can you time this please - do the following
     - start MSFS and time how long it takes from when you see the MSFS window appear (or, better, from when you see the FSUIC splash screen) to
        when it gets to the main menu state. Also, when FSUIPC starts (i.e. after you see the FSUIPC splash-screen) exit/quit FSUIPC - do this
        by opening the main window (Alt + F) and then select File -> Exit.
     - Once MSFS started and has reached the main menu, manually start FSUIPC7. Does it now connect? Exit MSFS and show me the FSUIPC7.log file
        from this test,
     - Open the FSUIPC7.ini file and set the DetectToConnectDelayAuto ini parameter to the approximate number of seconds it took MSFS to
        start and arrive at the main menu. Also set the InitialStallTime ini parameter to 45.
     - then restart MSFS. Does FSUIPC7 now start and connect ok? Show me the FSUIPC7.log file from this test.

If this issue persists, then I may need to see a SimConnect log file, as it seems that FSUIPC is unable to obtain a simconnect connection for some reason. To generate a SimConnect log file, see the following FAQ entry:  

 

[martynahubert]

11 hours ago, John Dowson said:

What do you mean by this? Do you not see the FSUIPC splash screen when FSUIPC starts? Can you not see the main window after pressing Alt+F?
The log file you attached is again showing that FSUIPC cannot connect to MSFS. But I don't understand why it stops after 4 attempts.

What other add-ons are you using?

Once MSFS starts, how long does it take to arrive to the main menu state? Can you time this please - do the following
     - start MSFS and time how long it takes from when you see the MSFS window appear (or, better, from when you see the FSUIC splash screen) to
        when it gets to the main menu state. Also, when FSUIPC starts (i.e. after you see the FSUIPC splash-screen) exit/quit FSUIPC - do this
        by opening the main window (Alt + F) and then select File -> Exit.
     - Once MSFS started and has reached the main menu, manually start FSUIPC7. Does it now connect? Exit MSFS and show me the FSUIPC7.log file
        from this test,
     - Open the FSUIPC7.ini file and set the DetectToConnectDelayAuto ini parameter to the approximate number of seconds it took MSFS to
        start and arrive at the main menu. Also set the InitialStallTime ini parameter to 45.
     - then restart MSFS. Does FSUIPC7 now start and connect ok? Show me the FSUIPC7.log file from this test.

If this issue persists, then I may need to see a SimConnect log file, as it seems that FSUIPC is unable to obtain a simconnect connection for some reason. To generate a SimConnect log file, see the following FAQ entry:  

 

I mean that I restart fsuipc, splash screen showed up then disappears and that's all, not connected with MSFS

Now  I launched MSFS and this time Fsuipc connected with MSFS, next exited Fsuipc as You adwised, then restart manually and the same as before,  just showed up splash screen, disappears and not connected

From the moment the FSUIC splash screen showed up to the moment it went to the main menu state, it took 4.36 sec.

I use many addons, for example FS Realistic and what I noticed, when I restart manually , fsuipc splash screen showing up together with FS Realistic even though FS realistic is already running in the background, maybe that's the problem.

FSUIPC7.log

[martynahubert]

connected  again with MSFS 

test with new ini entry

just in case I tried restart manually fsuipc, just splash screen, not connected

FSUIPC7.log

[John Dowson]

12 hours ago, martynahubert said:

From the moment the FSUIC splash screen showed up to the moment it went to the main menu state, it took 4.36 sec.

That seems very quick...so when FSUIPC tries to connect, MSFS is in the main menu state. I don't understand why it cannot connect then...
Are you doing anything with MSFS, or is it just waiting un the main menu?

The log file you attached shows that FSUIPC eventually connected, but took over 3 minutes, and you manually quit FSUIPC after 6mins 25 seconds.

12 hours ago, martynahubert said:

I use many addons, for example FS Realistic and what I noticed, when I restart manually , fsuipc splash screen showing up together with FS Realistic even though FS realistic is already running in the background, maybe that's the problem.

That is strange - I don't know why it would do that... You could maybe try with  FS Realistic not running 9or auto-started) to see if that makes a difference.

Could you show me / attach your EXE.xml file so I can see what else is being started - the location of this file will be logged in your InstallFSUIPC7.log file.

I think you will need to activate logging in SimConnect (see that FAQ entry I referenced above) and show me a SimConnect.log file. Once activated, start MSFS and ley everything auto-start. Leave it for a few minutes, and if FSUIPC doesn't connect, exit MSFS and show the the SimConnect.log file (or files), together with your FSUIPC7.log file. They will be very big and will need zipping/compressing. Even after that they will probably be too large to attach and you may need to use a file-exchange service to show it to me.

Can you also add the following to the [General] section of your FSUIPC7.ini file please:
     TestOptions=x800
That will add additional logging around the start-up and connection.

[martynahubert]

"The log file you attached shows that FSUIPC eventually connected, but took over 3 minutes, and you manually quit FSUIPC after 6mins 25 seconds."

Right, You told me after you I see the FSUIPC splash-screen) exit/quit FSUIPC by opening the main window (Alt + F) and then select File -> Exit.

So I did like this, You can see new log

Always I wait for MSFS, I do nothing else during waiting.

With regard SimConnect I'll do a bit later and I'll send You.

FSUIPC7.log InstallFSUIPC7.log

[John Dowson]

Please show me this file as well: C:\Users\marty\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml

2 minutes ago, martynahubert said:

Right, You told me after you I see the FSUIPC splash-screen) exit/quit FSUIPC by opening the main window (Alt + F) and then select File -> Exit.

Yes, but it connected and was working when you did this, although it took far longer to connect than it should.

I do not know or understand why simconnect is either not responding or taking a very long time to respond, I can only think that this is due to other simconnect clients, which is why I would like to see a simconnect log file (as this shows all simconnect activity.

Not sure why you attached that log file - just shows that you exited FSUIPC after 14 seconds, and there is no additional logging.
For the time being, please run with the logging console open (Log -> Open console) and monitor the messages, and only exit FSUIPC if you see that it cannot connect after a minute or so.
Also please set the following options in the [General] section of your FSUIPC7.ini file:
   InitialStallTime=45
   DetectToConnectDelayAuto=20
   StartUpTuningDoneVersion=-1
   TestOptions=x800

This will reset those parameters and prevent auto-tuning changing them (as well as setting the additional logging),

This issue seems very different from your original issue. Did this connection problem start recently?

[martynahubert]

I tried "To get a SimConnect LOG", I did everything as you described file I saved in folder C:\Users\xxx\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState, I tried as well to C:\Users\xxx\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache but there is no any file "SimConnect1.Log, unless I've did something wrong,  replaced path to logfile where I want to store but nothing, just in case I added this file.

 

exe.xml FSUIPC7.ini Simconnect.ini.log

[John Dowson]

The file you attached is called Simconnect.ini.log whereas it should be called just SimConnect.ini (i.e. remove the .log)- and it should be under C:\Users\xxx\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache.

Check your SimConnect.xml file as well (same location), and make sure the MaxClients entries are all set to 128 - if not, update them.

What is this entry for in your EXE.xml:

Quote

   <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>D:\Prepar3D v5\Addon Manager\couatl64\couatl64_boot.exe</Path>
    </Launch.Addon>

?

Also please try the attached EXE.xml - I have moved the FSUIPC entry to be started before the others,

John

exe.xml

[martynahubert]

Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>D:\Prepar3D v5\Addon Manager\couatl64\couatl64_boot.exe</Path>
    </Launch.Addon>

 

its for GSX ground services from fsdt to use jetways or stairs, bus with pax and etc. without runing couatl64 nothing work.

Since yesterday I launched 3 times MSFS and everytime FSUIPC worked and connected to the sim but first I disabled FS Realistic autostart because, before I had set like this, maybe that was the problem, anyway I will also try what You described at last post. Just in case I attached new log

FSUIPC7.log

[John Dowson]

3 minutes ago, martynahubert said:

Since yesterday I launched 3 times MSFS and everytime FSUIPC worked and connected to the sim but first I disabled FS Realistic autostart because, before I had set like this, maybe that was the problem, anyway I will also try what You described at last post. Just in case I attached new log

Yes, it does seem to ne something else that is causing issues with the SimConnect connections. Setting MaxClients may help. The EXE.xml I provided just starts FSUIPC before the other add-ons, but this may not work as the others may still connect first.
What you could also try is starting FS Realistic via FSUIPC - see the section Programs: facilities to load and run additional programs in the Advanced User guide.

The log looks ok, but I wouldn't recommend a setting of 4 for DetectToConnectDelayAuto, and your log does show some re-connections. I would not recommend any setting below 20, and usually advise 30 as the minimum.

John

[martynahubert]

I launched this time 4 times with new settings at file exe.xml and connected as well so it seems that the problem is solved for now, I hope nothing change, just in case I'll inform You again, anyway thank You very much for help.

As usual You can check again file.

Maciek.

FSUIPC7.log

[John Dowson]

It is connecting but you are still getting quite a few re-connection attempts, as it seems the simconnect open call is taking a long time to respond.
You could try the attached version, where I have allowed negative values for the InitialStallTime which will prevent the open call from timing out. Could you try this version please, and set
    InitialStallTime=-10
which will just log a message every 10 seconds until it connects. I would be interested to know if it does eventually connect, or if it is necessary to time-our and reconnect.

Thanks,

John

FSUIPC7.exe

[martynahubert]

Hello.

I'm sorry for so late aswer.

I'v changed, You can check log

FSUIPC7.log

[John Dowson]

1 hour ago, martynahubert said:

I'm sorry for so late aswer.

I'v changed, You can check log

That log is not using the version posted above, it is using 7.4.18 (the current released version). Also, you haven't set InitialStallTime=-10 :

Quote

     2985 Auto-started via EXE.xml with DetectToConnectDelayAuto=30, InitialStallTime=15

or maybe you set this but it was reverted as you were using the wrong version.

[martynahubert]

Now, You can check.

I had set InitialStallTime=-10

FSUIPC7.log

[John Dowson]

1 hour ago, martynahubert said:

I had set InitialStallTime=-10

You did not set this:

Quote

     1188 Auto-started via EXE.xml with DetectToConnectDelayAuto=30, InitialStallTime=15

That will always log the value it is using on start-up. You either set it in the wrong ini file, added/changed it while FSUIPC7 was still running, or maybe added it again and there is another entry.