You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In a clean install with no XSquawkBox installed previously or alongside, the package is missing essential files, which are also not included in the Bluebell package:
related.txt, the fact that I included an amended version was meant as a curtesy to copy over an existing install, not as an essential delivery
Doc8643.txt
Lights.png
Apparently, in my installation survived an old XSquawkBox install. Unfortunately, XSquawkBox comes under a pretty restrictive EULA. It is not freeware. The xplanemp library used to read CSL models and display them is freeware, but not the final xsb package. And only the xsb package includes the 3 files mentioned above. So strictly speaking they are under EULA, too.
To Reproduce
Clean install, i.e. remove all plugins and follow instructions.
It will not find essential files and bail out during plugin init.
Expected behavior
Package and instructions match and enable a clean install.
Technical Info:
OS: any
X-Plane version: any
LiveTraffic version: aby
Possible Solutions
First of all confirm, which file are really really necessary.
EULA allows copying content with written permission. So try obtaining a written permission to copy, modify, and distribute those 3 files.
In the end, we probably only talk about the related.txt. Because:
lights.png: In the XSquawkBox FAQs it reads that the old lights are phased out and should no longer be used with modern OBJ8 packages (which the Bluebell one is). So very likely the lights.png is no longer necessary. The call to XPMPMultiplayerInitLegacyData requires a path to this file, but likely it's content doesn't matter. Will try with the LiveTraffic logo ;) ... and then probably just take out all that code and, thus, remove the necessity.
Doc8643.txt: See issue Use OpenSky's Doc8643 data #24: I'd like to use another file anyway as it is more up-to-date. So this issue becomes more important now. Will include it in the next milestone.
And then...quite honestly...related.txt needs an overhaul anyway and might need adaptation re the Bluebell package, now that I understood it came with XSB. So I probably create a new one anyway.
The text was updated successfully, but these errors were encountered:
Describe the bug
In a clean install with no XSquawkBox installed previously or alongside, the package is missing essential files, which are also not included in the Bluebell package:
related.txt
, the fact that I included an amended version was meant as a curtesy to copy over an existing install, not as an essential deliveryDoc8643.txt
Lights.png
Apparently, in my installation survived an old XSquawkBox install. Unfortunately, XSquawkBox comes under a pretty restrictive EULA. It is not freeware. The xplanemp library used to read CSL models and display them is freeware, but not the final xsb package. And only the xsb package includes the 3 files mentioned above. So strictly speaking they are under EULA, too.
To Reproduce
Clean install, i.e. remove all plugins and follow instructions.
It will not find essential files and bail out during plugin init.
Expected behavior
Package and instructions match and enable a clean install.
Technical Info:
Possible Solutions
First of all confirm, which file are really really necessary.
lights.png
: In the XSquawkBox FAQs it reads that the old lights are phased out and should no longer be used with modern OBJ8 packages (which the Bluebell one is). So very likely thelights.png
is no longer necessary. The call toXPMPMultiplayerInitLegacyData
requires a path to this file, but likely it's content doesn't matter. Will try with the LiveTraffic logo ;) ... and then probably just take out all that code and, thus, remove the necessity.Doc8643.txt
: See issue Use OpenSky's Doc8643 data #24: I'd like to use another file anyway as it is more up-to-date. So this issue becomes more important now. Will include it in the next milestone.related.txt
needs an overhaul anyway and might need adaptation re the Bluebell package, now that I understood it came with XSB. So I probably create a new one anyway.The text was updated successfully, but these errors were encountered: