http://squawkbox.ca/downloads/

Thanks for the heads up.However, I think most users nowadays seem to prefer FSInn. SB has become too cumbersome and with too long development cycles. FSInn came out of nowhere and has in my opinion has totally blown SB away. But that's just me...Cheers,Pat

On the other hand, in my little world I'm not_aware of anyone using FSInn! :) I'm very satisied with Squawkbox 4 but I admit I have never tried FSInn.

SB3 here too!

I have tried FSInn, didn't like it at all and went back to Squawkbox. I'm not using either at the moment, because of a problem I'm having, but when it is resolved, I will still be using SB3 (and am now downloading the update - thanks for the heads-up).It's always going to be down to personal preference, but I don't like FSInn. :-)Cheers,Ian P.

Where can I find the list of fixes or changes incorporated in the new version?EDIT:Found it!Send aircraft information to all clients, not just pilots. Allows visual ATC clients like tower to display SB aircraft correctly. Allow use of .msg command without entering an initial message. Fixed crash bug triggered by opening multiple instances of the options dialog (bug 534). Fixed several typos in the VIP aircraft.cfg file (bug 544). Fixed problem where newly added planes briefly appear at the user's location (bug 556). Flight plan dialog items are saved in the registry even if the flight plan is not transmitted or saved. Added support for new FSUIPC events triggering private voice PTT (requires FSUIPC 3.50 or greater). Added code to check for innapropriate local modifications to equipment.txt that would cause bad data to be transmitted in the PI packet. Increased FSUIPC connect timeout from 2 to 4 seconds and require two consecutive failures to trigger a failed connection to FS. Upgraded to FSUIPC 3.50. Upgraded to SquawkBox Data 2005112600. Added major VIP3 update. Version 3.0.3Bryan

And of course I meant Squawkbox 3 not 4, in case somebody wonders... :)

Changed to SB3 for now because of problems with FSInn I've been having (FSInn randomly locking out keyboard access to FS, randomly starting itself when not running, not tuning voice (in fact not even noticing a controller is voice enabled)).FSInn 1.1 of course didn't work with voice at all because of that (with 1.0 I could manually tune AVC after looking up the channel in servinfo, 1.1 blocks the ports needed for its own built in client which doesn't tune because it never sees there is anything to tune to).Might go back to it in time as I do like the product overall, but it's a tad too rough around the edges in its current state.

>Thanks for the heads up.>>However, I think most users nowadays seem to prefer FSInn. SB>has become too cumbersome and with too long development>cycles. FSInn came out of nowhere and has in my opinion has>totally blown SB away. But that's just me...>>Cheers,>PatI don't know anyone that uses FS Inn, almost all the Vatsim people I talk to seem to use SB3. I like the idea of an all in one program with sound included, one click and your on,......

I just started using FSInn. So far I like it very much. Seems a bit better performance wise on my system. I will get the SB upgrade though.Lawrie

I prefer SB3. I had to switch to FSInn because the previous version of SB would cause the looping stutters that alot of people were having problems with. It just so happens that FSInn and SB3 released new versions at the same time, so I'm glad to be back to SB3. Its just a much "cleaner" interface. Everything it needs to be functional is located in 4 or 5 menus, as where FSInn has something like 10 or 12. Its just not very streamlined. I appreciate colors, but FSInn overdoes it on things like their VATSIM voice library control panel. There are like 4 or 5 color coded buttons, on that panel alone, that I have no clue what they do. I'm not going to spend 2 hours reading the manual in hopes of finding the answer and then having to remember, while flying, what they do.KISS method for me.

>Thanks for the heads up.>>However, I think most users nowadays seem to prefer FSInn. SB>has become too cumbersome and with too long development>cycles. FSInn came out of nowhere and has in my opinion has>totally blown SB away. But that's just me...>>Cheers,>PatI cant stand FSINN and dont go any where near it. FSINN is still very much in the minority compared to SB.

I use both.I guess it depends on what I'm doing.If I'm flying with a group of friends doing some VFR, then I use FSInn.If I'm flying my airliners, then I use SB3.STAY AWAY FROM FSInn 1.1 beta... it's caused SERIOUS issues outside of Flight Simulator. It killed my TCP/IP stack more than once, causing me to restart my network daemon before I could do anything on my computer. It also caused FS9 to crash 75% of the time on any flights longer than an hour. Each crash was different... It would load itself even though you tell it not to. The voice didn't work ( see explanation from a previous poster about blocking it's own ports ).... etc etcI just hate seeing flying question marks... put in an option for an OVERALL DEFAULT MODEL if nothing matches. On SB3 if a plane isn't recognized, then it shows a giant question mark on a triangle.That's just stupid. :(

>It killed my TCP/IP stack more than once, causing me to restart my network daemon before I could do anything on my computer. It also caused FS9 to crash 75% of the time on any flights longer than an hour.