Announcement

Collapse
No announcement yet.

How to connect X-Plane 11 to the MSFlights Simlink server for group flights.

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to connect X-Plane 11 to the MSFlights Simlink server for group flights.

    To connect X-Plane 11 to the MSFlights Simlink server to participate in group flights, all you need is X-Plane and XSquawkBox.

    Here are the instructions you need for getting started with X-Plane and MSFlights:

    1. Download XSquawkBox :
    You can find it here: http://www.xsquawkbox.net/xsb/download/

    2. Install XSquawkBox :
    Extract XSquawkBox and place the files into the X-Plane\Resources\Plugins folder.

    3. Open XSquawkBox :
    3.1. Launch X-Plane 11.
    3.2. Hover the mouse over the menu system at the top left of your monitor once you are in your aircraft and select
    Plugins, XSquawkBox, Connect.

    4. Connect to the MSFlights Simlink Server :
    To connect to the MSFlights Simlink Server, insert the following parameters into the XSquawkBox Connect dialog box -

    Callsign: as appropriate
    Realname: as appropriate
    Server: 101.165.150.139 {this is the MSFlights Australia server address}
    Port: 6809
    ID:MSFPILOT
    Password:MSFPILOT
    Model:C172

    4.1. Select Connect.

    To confirm that you have connected to the server, look for your aircraft on the server map: http://msflights.net/pilots/map/map.html


    5. Smile, you're done!


    Appendix 1. To avoid seeing 737's when XSquawkBox's model matching fails :
    A1.1. Launch X-Plane 11.
    A1.2. Hover the mouse over the menu system at the top of your monitor once you are in your aircraft and select:
    Plugins, SquawkBox, Preferences, Default Aircraft ICAO : C172

    {This will make the C172 the default plane to be shown when XSquawkBox's aircraft model matching fails}


    Appendix 2. How to connect X-Plane 11 to the VATSIM server for MSFlights group flights on VATSIM.
    A2.1. Signup for a free VATSIM account from vatsim.net
    A2.2. Open XSquawkBox
    A2.3. Connect to the VATSIM Server : insert the following parameters into the XSquawkBox Connect dialog box -

    Callsign: MSF1xx
    Realname: VATSIM requires you use your real name
    Server: select a server from the list
    Port: 6809
    ID: your VATSIM ID
    Password: your VATSIM Password
    Model:C172

    A2.4. Select Connect.

    A2.5. To confirm that you have connected to the server, look for your aircraft on the server map: http://vattastic.com/

    Cheers,

    keyword: xplane
    Last edited by Bluejay; May 7, 2018, 12:24 PM.

  • #2
    Thank you BlueJay! :eagerness: Update: XSquawkBox v1.3.3 does work provided you don't use the FSD proxy. If you insist on using the proxy, you have to go back to v1.3.1 of XSquawkBox. Therefore I'm recommending using current release v1.3.3 and not using the proxy, which is a cleaner and simpler solution. The current release can be downloaded as usual from http://xsb.xsquawkbox.net/ though I'll still keep v1.3.1 in Storm's Hangar for pilots who, for whatever reason, want to keep using the proxy. You may want to adjust your opening post!

    Comment


    • #3
      Why are people using the Proxy if it's not needed?
      I seem to remember adding the correct response to Simlink so the Proxy wasn't needed.
      The Proxy should only be needed for Vpilot as you can not enter an address directly into Vpilot.

      To add to the mix....
      If XSQUAWKBOX supports voice(I dont know if it does?) try roo.servebeer.com as the server.

      Also if you Google Swift pilot client, that also seems to be coming on nicely too.
      If you don't use BOINC or World Community Grid then you should!

      Comment


      • #4
        Thanks Storm and ATC_ROO for the input.

        I wasn't sure if the Proxy might be required to ensure that all aircraft are visible to all participants in all configurations.. hence the inclusion of the configuration with the addition of the MSF Proxy.

        I've since done the following test:

        I simultaneously ran the following configurations:
        1. Prep3d V3 + vPilot + MSF Proxy on MSF Simlink server
        2. X-Plane 11 + Xsquawkbox addressing the MSF Simlink server directly

        Both aircraft are visible to each other. I have sent a screenshot to Storm to confirm. MSF Proxy is not needed for X-Plane running XSquawkBox to connect to the MSF simlink server.

        I have removed the entry in my documentation for now.

        Swift sounds likes it's going to be a great allpurpose replacement for the several pilot clients currently used for cross platform support on VATSIM.
        Last edited by Bluejay; July 14, 2017, 03:50 AM.

        Comment


        • #5
          Model matching using X-Plane 11, XSquawkBox and the MSF Simlink server

          XSquawkBox (herein called XSB) uses model matching. Aircraft models for model matching are csl packages.

          (work in progress)

          How to install models for model matching using X-Plane 11, XSquawkBox and the MSF Simlink server.
          https://www.youtube.com/watch?v=a4nvJu7gbXs

          Existing csl models are here:
          http://forums.x-plane.org/index.php?...l-kits/&page=5

          Musings on csl
          http://developer.x-plane.com/2010/03/musings-on-csls/

          Making new csl 's
          http://forums.x-plane.org/index.php?...-csl-packages/

          X-CSL, A project for a set of standardised csl 's
          http://csl.x-air.ru/?lang_id=43
          and their model list is here: http://csl.x-air.ru/info/item/302

          XSquawkbox and X-CSL
          http://forums.x-plane.org/index.php?...box-and-x-csl/

          A CSL folder typically resides in \Plugins\XSquawkBox\Resources\CSL

          A CSL folder typically is named in relation to the Aircraft model it contains.
          eg. P28R {Piper Cherokee 28}
          and contains at least:
          .obj {eg. P28R.obj containing the model airframe}
          .png {eg. P28R.png containing the model livery}
          .txt {eg. xsb_aircraft.txt containing txt that associates the .obj to an ICAO aircraft code}
          Last edited by Bluejay; July 14, 2017, 08:35 AM.

          Comment


          • #6
            Thank you all for clearing this up for me!
            Yours in flight,

            Pops :-D

            Comment


            • #7
              By the way, I only posted up the x-plane / xsquawkbox / msflights simconnect instructions because the link to the original instructions are not available to Rookie Pilots on MSFlights.net.

              Comment


              • #8
                Originally posted by Bluejay View Post
                .... original instructions are not available to Rookie Pilots on MSFlights.net.
                I don't understand specifically what this means? Can you elaborate so we can fix it. Thanks for the work in updating the instructions.

                Comment


                • #9
                  "SimLink Quick start
                  SimLink Installation instructions. This is only essential information to get you started in the simplest way.
                  Full detail explanation and any other information about the system, please refer to the excellent Post by ROO here "
                  "
                  Not sure if it's this, but when I click it, it says... "Invalid Thread specified. If you followed a valid link, please notify the administrator"
                  Yours in flight,

                  Pops :-D

                  Comment


                  • #10
                    Karl, the thread Bluejay and Pops0 refer to is visible for site admins (like myself) but sadly not available for everyone else.

                    Comment


                    • #11
                      Originally posted by Storm View Post
                      Karl, the thread Bluejay and Pops0 refer to is visible for site admins (like myself) but sadly not available for everyone else.
                      fixed
                      mike404

                      Comment


                      • #12
                        X-Plane 11: Fixing unwanted weather changes and stutters

                        When you connect to SimLink or VATSIM with XSquawkBox, by default it uses "live" network weather. Of course this is a Good Feature™ if you're flying in VATSIM under ATC as otherwise you would have to tell the controller you were not using VATSIM weather. However when you're flying in SimLink, where we expect a degree of autonomy, it can cause a problem.

                        For example, I've had a problem in SimLink where I would override the weather in X-Plane 11's set-up, say to CAVOK, and a few minutes later it would mysteriously reset to something else. This was especially embarrassing while leading a group flight recently when I'd set a nice clear sky - for taking screenshots on approach - and it suddenly changed to a foggy Cat I on short finals!

                        Fortunately this problem can easily be fixed. I traced it to XSquawkBox and its periodic weather downloads. They can be stopped by adjusting XSquawkBox's preferences and setting "Check Weather every" to zero minutes. (See pictures below, with relevant section ringed in red.) The weather will now stay as you have configured it within X-Plane 11.

                        Setting the preferences this way also removes another annoying problem. Weather updates can cause a stutter or sharp dip in frame rate if you have XSquawkBox running and connected. This is especially so if the server does not have weather for where you are, which causes XSquawkBox to "thrash" (yes that really is a genuine computer science term!) as it tries to find a weather station nearby, sending potentially hundreds of requests to the server. Setting the check weather update period to zero stops this stuttering and your flight is smooth.

                        For more information on this, please read the XSQUAWKBOX USER'S GUIDE in X-Plane 11\Resources\plugins\XSquawkBox\Docs.

                        Comment

                        Sorry, you are not authorized to view this page
                        Who has read this thread:
                        Working...
                        X