General Category > General Discussion

Long load times at all couatl airports

(1/2) > >>

Iced8383:
A few days ago I started experiencing extremely long load times in P3D v3 at all of the FSDT/flightbeam airports that I have, and it only happens at those ones.  My sim will load up through the initial loading screen, get to the point where I see the jetways/moving vehicles but no buildings, then freeze for about 2-5 minutes (e.g. 2 minutes at PHKO, 5 at KSFO HD) depending on what scenery I'm loading into.  When I arrive into scenery that uses couatl, I experience the same issue.  Once the scenery starts loading my sim locks up for a few minutes.  I've tried reinstalling all of my couatl airports with removing the addon manager/couatl, installing the standalone addon manager, and a full reinstall of P3D v3 with no fix.  Before the issue began I was experiencing airport load times of 15-20 seconds at most.

virtuali:
"minutes" it's not normal, and unheard of.

You must have some kind of issues with Simconnect, like another addon sending so many commands to it, that is flooding the communication channel with FSX, so our module doesn't get enough time to talk with it.

It's best to activate the Simconnect diagnostic mode to understand what's going on, this way:

Open Notepad, and copy the following text:


--- Code: ---[SimConnect]
level=verbose
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9

--- End code ---


Save the file as SIMCONNECT.INI in this folder:

Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files

At the next FSX launch, you should see a text window with diagnostic messages: the FIRST 5-6 lines are important: you should try to note what they are saying.

Iced8383:
Here's the first few lines of the diagnostic tool:


--- Code: ---0.00000 SimConnect version 3.0.0.0

0.00168 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Lockheed Martin Prepar3D v3\SimConnect, MaxClients=64
0.00306 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.00447 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft ESP\SimConnect, MaxClients=64
0.00589 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Lockheed Martin(R) Prepar3DÖ\SimConnect, MaxClients=64
0.00737 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Lockheed Martin Prepar3D v2\SimConnect, MaxClients=64
0.00891 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Lockheed Martin Prepar3D v3\SimConnect, MaxClients=64
0.01009 Server: Scope=local, Protocol=IPv6, Address=::1, Port=60007, MaxClients=64
0.01114 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=60008, MaxClients=64
--- End code ---

virtuali:

--- Quote from: Iced8383 on October 25, 2015, 11:49:20 pm ---Here's the first few lines of the diagnostic tool:
--- End quote ---


--- Quote ---0.01009 Server: Scope=local, Protocol=IPv6, Address=::1, Port=60007, MaxClients=64
--- End quote ---

Have you installed a 3rd party product that requires Simconnect over a network ? See here:

http://www.fsdreamteam.com/forum/index.php/topic,12574.msg95311.html#msg95311

Iced8383:
I did some digging around and found that I do have a simconnect.xml and a simconnect.cfg located in both my active sky next and P3Dv3 SDK folders.  Would those have anything to do with it?

Edit:  I probably should've added this in the OP, but I use Windows 10.

Navigation

[0] Message Index

[#] Next page