March 15, 201412 yr Anyone using these two plugins together? Recently I updated my PE client and now it's causing XP to CTD upon load. I am just now running XSB for the first time and I successfully connected and did a flight on vatsim. Pilot Edge says there's a conflict with some file called Xsquawkbox_VATSIM.xpl But I don't see this file anywhere.... apparently XSB and PE plugins share this common file....?? | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
March 19, 201412 yr Commercial Member Xsquawkbox_VATSIM.xpl used to be the filename of XSquawkbox plugin. Perhaps that's changed now that they have 32 and 64-bit builds. It's probably moved to a 'fat' plugin architecture, in which case, check your Xplane plugins folder for a Xsquawkbox folder, or something along those lines. When you're ready to fly on PE, just move the XSB folder out of the plugins folder. Conversely, when you want to fly on VATSIM instead of PE, move the PE folder out of the plugins folder and put the XSB folder back into play. In short, only one of these plugins can be active at any given time because both of them share the same underlying multiplayer library, and as a result, both attempt to comandeer the Xplane multiplayer system, mainly so they can drive TCAS systems correctly. Keith Smith PilotEdge Founder ASEL (instrument) Lancair 360
March 19, 201412 yr Author Appreciate the answer Keith! | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
Create an account or sign in to comment