-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make CSL paths configurable #42
Comments
"Make multiple calls to XPMPLoadCSLPackage to load additional CSL directories if there is more than one." What if they overlap, possibly with conflicts (same ICAO, different models/liveries) |
I would test that and see what the multiplayer library makes of it. Anyway...there are more issues than that. From your logs, e.g., I read that CSL models are also installed in folder not called "Resources/CSL". I would miss them. So I am unsure how to allow for a very simple install also for beginners on the one hand, while on the others allow power users like you to fine-tune settings. Just an idea I had: LT writes out the directories found into the LiveTraffic.prf. A power user can edit that file and specify exactly which directories to consider and which not. And the beginner would just ignore all that and LT would find something somewhere... And maybe I just make things too complicated and should simply demand a CSL package in my directory like all other plugins do...it's just 3.5 GB in the end :) |
"And maybe I just make things too complicated and should simply demand a CSL package in my directory like all other plugins do...it's just 3.5 GB in the end :)" Yes, disk space is very inexpensive - support of clueless users is very expensive ;-) |
Yea...I gonna roll back that complexity. The only thing I gonna offer is to configure one (maybe five) paths to CSL directories. And for installation and startup purposes LiveTraffic will only check in its own Resources/CSL. Full stop. |
Current Situation / Problem
Currently, LiveTraffic looks into the hard-coded path
plugins/XSquawkBox/Resources/CSL
to find CSL packages. If XSB is installed elsewhere that will fail.Checking X-IvAp paths is not even implemented yet.
Suggested Solution
Walk all plugins, search for "Resources/CSL" and just take that.
Make multiple calls to
XPMPLoadCSLPackage
to load additional CSL directories if there is more than one.Benefits
Independence if individual user's setup.
** Still to do **
The text was updated successfully, but these errors were encountered: