PilotEdge Forums

I tried the FSX sb but when I connect it just hang and says "sending login info".

A couple questions. Does it hurt to have the older vatlim.dll in the networks folder. I tried renaming it and still get the hanging when I trie to connect.

Below is my directory structure for SB 4 with the new files.

Thx
Ron


Directory of C:\Program Files (x86)\SquawkBox

01/27/2010 06:19 PM <DIR> aircraft
01/27/2010 06:19 PM 118,761 airlines.txt
01/27/2010 06:19 PM 12,808 csl_legacy.txt
01/27/2010 06:19 PM 1,535 fictional.txt
01/27/2010 06:19 PM 253,054 equipment.txt
01/27/2010 06:19 PM 11,295 liveries.txt
01/27/2010 06:19 PM 4,935 related.txt
01/27/2010 06:19 PM 2,579,968 simconnect.msi
01/27/2010 06:19 PM <DIR> sound
01/27/2010 06:19 PM <DIR> weather
01/27/2010 06:19 PM 308,209 wx.txt
01/27/2010 06:19 PM 307 readme.txt
01/27/2010 06:19 PM 77,824 sbuninstall.exe
01/27/2010 06:19 PM 13,400 squawkbox_eula.txt
01/27/2010 06:19 PM 2,550 squawkbox.ico
06/19/2011 03:06 PM 797,184 squawkbox_pe_fsx.ex
06/19/2011 03:06 PM 1,462,784 ts3client_win32.dll
06/19/2011 03:06 PM 397,312 fmodex.dll
06/19/2011 03:06 PM 770,384 msvcr100.dll
06/19/2011 03:06 PM 4,457,472 sbimage.dll
06/19/2011 03:06 PM 205,824 sbtrans10.dll
06/19/2011 03:06 PM 76,800 sbaicontrol10.dll
06/19/2011 03:16 PM <DIR> .
06/19/2011 03:16 PM <DIR> ..
06/19/2011 03:16 PM <DIR> logs
06/19/2011 03:18 PM <DIR> networks

It does not hurt to have the vatsim dll in the networks folder.

I have it set to ignore that library so that a user won't attempt to connect using the wrong client.

Any chance that a firewall is in play here?

Verify you're picking the main server, not the dev server?

First of all congratulations for the launching of Pilot Edge. I'll be glad to use it for my continuous IFR training once it's full blown (paid) version is up and running. By now, I'm finding a similar problem as described above. After starting FSX and positioning the plane in the ramp, I open SB, fill it up as instructed ("test" / "beta", etc), but then nothing happens. SB freezes in there with the "Sending login info" window, and FSX is unresponsive...Help! I can't wait to start using it. Thanks in advance.

Welcome, and thanks for the kind words. Can you try connecting at a remote airport (PANC, KORD, KMMU, any of those would be fine) and let me know if FSX still locks up.

If it doesn't hang then it's traffic related, and we'll deal that next. If it still hangs then it's a new, unrelated issue.

Thanks for the reply. I tried starting from one of the distant airports but it didn't work. After trying different things I finally got to connect. I believe the issue is somehow related to using one of my monitors at full screen mode. In full screen mode, when I leave the FSX screen to connect the SB, the FSX crashes. Anyway, I'm glad that I got to use the system today. The experience was good and I'll be back often.

Max,

That's great to know, thanks for the info.

Are you perhaps moving between applications and FSX in full screen using Alt+Tab?

If you are, that will cause application crashes, fragmenting and screen tearing that can be the culprit. Try using Alt+Enter to take FSX out of Full screen, and then click the application tab in the task bar, or Alt+Tab to grab the secondary application. Then return to FSX and Alt+Enter to return to full screen.

I have been having similar issues as maxlago except it sounds like he is using multiple monitors while I am only using one. From best that I can determine the majority of my problems (FSX crashing or Not Repsonding; SB login errors) have been a result of UAC. I am very unfamiliar with UAC but have found the most success with connecting when I disable all UAC from the win7 start menu. I am not sure how unsecure this makes my computer but it allows me to connect and fly on Piloedge so I'm happy for the time being.

Unfortunately, though I am able to connect much more consistently, FSX has twice now "locked up" after about 10 or 15 min of flight. I think this maybe a compatibility issue between my version of FSX (FSX deluxe) and win7. I have read that some FSX are 32 bit and win7 is 64. Not sure how to address this w/out having to buy a compatible version of FSX. This problem has occured, although less often, even when I am not connected to Pilotedge (or any other ATC service) which is why I believe it is likely to be something other than the ATC Server.

If anyone can help me with my compatibility issue and save me from having to buy another copy of FSX it would be greatly appreciated!

*edit* - I will note that I had firefox running in the background (skyvector and airnav) and was switching between the two programs periodically.