John Dowson Posted March 29 Report Share Posted 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 Link to comment Share on other sites More sharing options...
BillA Posted March 29 Report Share Posted March 29 Here is the log FSUIPC7.log Link to comment Share on other sites More sharing options...
Empire Posted March 29 Report Share Posted March 29 Hello, Since the update, Takes MSFS so long to load up more so than before. 20mins to load into the aircraft FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted March 29 Report Share Posted March 29 @BillA Please try with DetectToConnectDelayAuto=200 InitialStallTime=5 Please re-attach your log after trying with these - and please make sure that you exit FSUIPC7 before attaching your log file. @Empire Please also remember to exit FSUIPC7 before attaching log files. You are also using 7.4.10 - please update to 7.4.11a attached above. Also please try with those ini parameters mentioned above (i.e. add to the [General] section of your FSUIPC7.ini file) and show me the log using these settings. Again, for all those who have this issue, you need to set the DetectToConnectDelayAuto parameter to a high enough value so that this message isn't logged (although a few re-connection attempts shouldn't be a problem, too many retries can cause issues due to a long standing simconnect issue with the number of connections used): Quote 68312 **** SimConnect open event not received in required time limit: Re-connecting now... John Link to comment Share on other sites More sharing options...
wackydude75 Posted March 29 Report Share Posted March 29 The new file ad the 2 Lines in the .ini helped for me. Fenix and FSLTL working normally now, thank you! Link to comment Share on other sites More sharing options...
ark1320 Posted March 29 Report Share Posted March 29 Hi John, Many thanks for all your quick attention to the various FSUIPC7 to Simconnect connect problems over the past couple or weeks. Wonderful support! I see you have now introduced a third new General section parameter called InitialStallTime. Do you see this as a replacement for the previous parameter DetectToConnectDelay, which was for manual FSUIPC7 loads, or do you expect this new parameter will be in addition to the previous ones? I'm just wondering which parameters will be available to experiment with should a future Simconnect connect problem come up, such as when SU15 is released. Thanks, Al Link to comment Share on other sites More sharing options...
John Dowson Posted March 29 Report Share Posted March 29 1 hour ago, wackydude75 said: The new file ad the 2 Lines in the .ini helped for me. Fenix and FSLTL working normally now, thank you! Ok, but please note that they are example values - you should tune those to your system. I have explained how to do this several times in this topic already, vut I will create a FAQ topic on how to tune this when I get time. 18 minutes ago, ark1320 said: I see you have now introduced a third new General section parameter called InitialStallTime. This is actually an old parameter that has always existed, but I deprecated the use of this in the last few versions as it should not be necessary. I have added this back in the latest (beta) release though as it seems that it is needed for some systems where it is taking a long time for the return message of the initial connection request. 21 minutes ago, ark1320 said: Do you see this as a replacement for the previous parameter DetectToConnectDelay, which was for manual FSUIPC7 loads, or do you expect this new parameter will be in addition to the previous ones? I'm just wondering which parameters will be available to experiment with should a future Simconnect connect problem come up, such as when SU15 is released., This is an additional parameter. It is better to leave this as the default value and only update if absolutely needed. Better to adjust the DetectToConnectDelay and DetectToConnectDelayAuto parameters first. If you are starting manually, then the value of these parameters depends upon when you are starting FSUIPC7. If you are starting when MSFS2020 is running and either already in the main menu or you have loaded an aircraft, then you can and should use the default values. If you are starting FSUIPC7 before MSFS is started, then you should set the DetectToConnectDelay parameter to a higher value - start at 60 (seconds) and increase until you don't see any re-connection messages. Only tune the InitialStallTime parameter if continually receiving this message: Quote 43312 56968 **** Data not received in required time limit: Re-connecting now... I will tune/adjust the defaults for these for SU15 and rebuild against the latest SDK (currently 0.24.1.0 for SU15) and release a new version once SU15 has been released. Please also note that for the next few days I will have limited time to respond to support requests....please be patient. John 1 Link to comment Share on other sites More sharing options...
Empire Posted March 29 Report Share Posted March 29 updating to 11A - added the lines = sim loading times back to normal 😉 Link to comment Share on other sites More sharing options...
alexanderluzajic Posted March 29 Report Share Posted March 29 6 hours ago, John Dowson said: please update to 7.4.11a attached above Above where... lol. I must be blind, sorry 1 Link to comment Share on other sites More sharing options...
Clinton Fernandes Royston Posted March 30 Report Share Posted March 30 (edited) Exactly where is the latest 7.4.11a download? nevermind found it Edited March 30 by Clinton Fernandes Royston Link to comment Share on other sites More sharing options...
John Dowson Posted March 30 Report Share Posted March 30 Note that the only change from 7.4.10 to 7.4.11a is the ability to configure the InitialStallTime ini parameter. This can help but should not be necessary if you configure the DetectToConnectDelayAuto correctly. The default value for InitialStallTime in 7.4.10 is 5 (seconds), which should be sufficient for most users. So I would advise people with this issue to first try with the current release 7.4.10 and configure the DetectToConnectDelayAuto ini parameter first, and only update to 7.4.11a if you are still getting issues. John Link to comment Share on other sites More sharing options...
Francisco Sanchez Posted March 30 Report Share Posted March 30 There is 22 hours ago, John Dowson said: 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. 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 Sure John. There my log. Francisco FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted March 30 Report Share Posted March 30 15 minutes ago, Francisco Sanchez said: Sure John. There my log. If you look at your log, you will see this: Quote 328 Auto-started with DetectToConnectDelayAuto=220, InitialStallTime=10 3172 Simulator detected 223172 Trying to connect... 233172 **** SimConnect open event not received in required time limit: Re-connecting now... 233172 Trying to connect... 243172 **** SimConnect open event not received in required time limit: Re-connecting now... 243172 Trying to connect... 253172 **** SimConnect open event not received in required time limit: Re-connecting now... 253172 Trying to connect... 263172 **** SimConnect open event not received in required time limit: Re-connecting now... 263172 Trying to connect... 273172 **** SimConnect open event not received in required time limit: Re-connecting now... 273172 Trying to connect... 283172 **** SimConnect open event not received in required time limit: Re-connecting now... 283172 Trying to connect... 293172 **** SimConnect open event not received in required time limit: Re-connecting now... 293172 Trying to connect... 303172 **** SimConnect open event not received in required time limit: Re-connecting now... 303172 Trying to connect... 313172 **** SimConnect open event not received in required time limit: Re-connecting now... 313172 Trying to connect... 323172 **** SimConnect open event not received in required time limit: Re-connecting now... 323172 Trying to connect... 333172 **** SimConnect open event not received in required time limit: Re-connecting now... 333172 Trying to connect... 343172 **** SimConnect open event not received in required time limit: Re-connecting now... 343172 Trying to connect... 353172 **** SimConnect open event not received in required time limit: Re-connecting now... 353172 Trying to connect... 363172 **** SimConnect open event not received in required time limit: Re-connecting now... 363172 Trying to connect... 373172 **** SimConnect open event not received in required time limit: Re-connecting now... 373172 Trying to connect... 383172 **** SimConnect open event not received in required time limit: Re-connecting now... 383172 Trying to connect... 393172 **** SimConnect open event not received in required time limit: Re-connecting now... 393172 Trying to connect... 396234 SimConnect_Open succeeded You have DetectToConnectDelayAuto set to 220, but this is still not enough time for your installation. You can see that it finally connects at timestamp 396234, so you need to use a value of 393 for the DetectToConnectDelayAuto parameter. It is not difficult to determine the value for this parameter - just look at your log file and the timestamp for the SimConnect_open succeeded message, divide this by 1000 (i.e. convert from ms to seconds) and then subtract 3 or 4 (the timestamp from the Simulator detected log message). John Link to comment Share on other sites More sharing options...
von Posted March 30 Report Share Posted March 30 I just downloaded and installed FSUIPC7, Version 7.4.10 No edits to the ini file. Started FSUIPC (I do not use the FSUIPC’s Batch to auto start MSFS). Started MSFS. Took 140 seconds to get to the Welcome / aircraft selection screen. Selected PMDG 737-600 at KDTW. Took 90 seconds to load the flight. Looks good. Exited MSFS. Log file information: 281 ------------------------------------------------------------------- 297 LogOptions=00000000 00000001 297 Manually started with DetectToConnectDelay=1 297 *** FSUIPC WASM module not detected - not adding WASM menu 30094 Simulator detected 92063 **** SimConnect open event not received in required time limit: Re-connecting now... 97063 **** SimConnect open event not received in required time limit: Re-connecting now... 102063 **** SimConnect open event not received in required time limit: Re-connecting now... 107063 **** SimConnect open event not received in required time limit: Re-connecting now... 112063 **** SimConnect open event not received in required time limit: Re-connecting now... 117063 **** SimConnect open event not received in required time limit: Re-connecting now... 122063 **** SimConnect open event not received in required time limit: Re-connecting now... 127063 **** SimConnect open event not received in required time limit: Re-connecting now... 129578 SimConnect_Open succeeded 129578 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 129578 MSFS version = 11.0.282174.999 Link to comment Share on other sites More sharing options...
ark1320 Posted March 30 Report Share Posted March 30 1 hour ago, von said: I just downloaded and installed FSUIPC7, Version 7.4.10 Based on your log file, looks like the sim was detected at about the 30 sec point, and you connected to SimConnect at about the 130 sec point (rounding the values) so if I understand John's guidance correctly, you would need a DetectToConnectDelay setting of 130 - 30 = 100 sec (maybe add an additional 1 or 2 sec to be safe). Note that the log time stamp values are in milliseconds. Al Edited: In the above, changed DetectToConnectDelayAuto to just DetectToConnectDelay since FSUIPC7 was started manually, not automatically. Link to comment Share on other sites More sharing options...
Francisco Sanchez Posted March 30 Report Share Posted March 30 45 minutes ago, John Dowson said: If you look at your log, you will see this: You have DetectToConnectDelayAuto set to 220, but this is still not enough time for your installation. You can see that it finally connects at timestamp 396234, so you need to use a value of 393 for the DetectToConnectDelayAuto parameter. It is not difficult to determine the value for this parameter - just look at your log file and the timestamp for the SimConnect_open succeeded message, divide this by 1000 (i.e. convert from ms to seconds) and then subtract 3 or 4 (the timestamp from the Simulator detected log message). John Got it. Thanks. But let us know why this happens when previous version was ok? Where is the origin of this issue? Link to comment Share on other sites More sharing options...
Doc_Z Posted March 30 Report Share Posted March 30 Just to clarify for older and slower minds; Download the .11a file. Run the .exe and then replace the .ini file with the one provided and add the two lines? Link to comment Share on other sites More sharing options...
ark1320 Posted March 30 Report Share Posted March 30 19 minutes ago, Doc_Z said: Just to clarify for older and slower minds; Download the .11a file. Run the .exe and then replace the .ini file with the one provided and add the two lines? I don't think a FSUIPC7.ini file is provided -- that is specific to each user. But yes, do add the new [General] section parameters as discussed in the above posts if needed. Al Link to comment Share on other sites More sharing options...
John Dowson Posted March 30 Report Share Posted March 30 44 minutes ago, ark1320 said: Based on your log file, looks like the sim was detected at about the 30 sec point, and you connected to SimConnect at about the 130 sec point (rounding the values) so if I understand John's guidance correctly, you would need a DetectToConnectDelayAuto setting of 130 - 30 = 100 sec (maybe add an additional 1 or 2 sec to be safe). Note that the log time stamp values are in milliseconds. No! The user is manually starting FSUIPC7, and is not having it auto-started by MSFS. Notice this log line: Quote 297 Manually started with DetectToConnectDelay=1 Your analysis of the time is correct, but the user needs to set the DetectToConnectDelay ini parameter to 100, bot he DetectToConnectDelayAuto one. 35 minutes ago, Francisco Sanchez said: But let us know why this happens when previous version was ok? Where is the origin of this issue? But the previous version was not ok! It may have seemed that way, but what was happening is that messages were being received from an old connection and was screwing up many aspects of FSUIPC7. The only change that is causing this issue is to actually issue a close command to close a dead connection before starting a new one. Previously, the old connection was left open when the new one was started, and it is messages from this old/dead connection that was causing issues. John Link to comment Share on other sites More sharing options...
John Dowson Posted March 30 Report Share Posted March 30 4 minutes ago, Doc_Z said: Just to clarify for older and slower minds; Download the .11a file. Run the .exe and then replace the .ini file with the one provided and add the two lines? You do NOT need to use that version,. Just try setting the DetectToConnectDelayAuto and/or the DetectToConnectDelay ini parameters correctly. only then if you have issues, download 7.4.11a and adjust the InitialStallTime ini parameter. Link to comment Share on other sites More sharing options...
ark1320 Posted March 30 Report Share Posted March 30 3 minutes ago, John Dowson said: No! The user is manually starting FSUIPC7, and is not having it auto-started by MSFS. Notice this log line: Very sorry John, edited my post so it is correct now. Al Link to comment Share on other sites More sharing options...
Doc_Z Posted March 30 Report Share Posted March 30 Will there be an updated version any time soon? Link to comment Share on other sites More sharing options...
John Dowson Posted March 30 Report Share Posted March 30 1 minute ago, Doc_Z said: Will there be an updated version any time soon? No, I don't see a need. The next update will be for the SU15 release, in a week or two - or whenever that drops. Link to comment Share on other sites More sharing options...
Doc_Z Posted March 30 Report Share Posted March 30 Added the lines and Fenix and FSLTL seem to be working fine. My GSX Pro isn't. Is there a connection between FSUIPC and GSX that might cause a problem? Link to comment Share on other sites More sharing options...
John Dowson Posted March 30 Report Share Posted March 30 46 minutes ago, Doc_Z said: Added the lines and Fenix and FSLTL seem to be working fine. Did you set the correct value for your system, as shown in this thread several times. Do noy just copy values I have given for other users - look at your log to determine what the optimal value is for your system and use that, 48 minutes ago, Doc_Z said: My GSX Pro isn't. Is there a connection between FSUIPC and GSX that might cause a problem? I can't see how this issue can affect connections to FSUIPC, as they do not use SimConnect (this issue is related to SimConnect threads only). But, as for all issues, I need to see your FSUIPC7.log file. What is the issue with GSX Pro? Link to comment Share on other sites More sharing options...
Recommended Posts