Hi we have been informed that SU16 totally kills the blackbox simulation shorts products
this product was created as a group of packages with textures and common behaviours in a common package
these were referenced by other packages in the group and it now apears that neither textures or behaviours are accessable acroos packages
can you confirm what changes have been made and why
The changelist for SU16 is available in the official forums.
Can you elaborate on the issue you are having with information such as:
Basically any information that can help us help you.
Best regards,
Eric / Asobo
Hi @EPellissier
i looked at the changelog and it doesnt mention anything i can see that would cause this issue
the package that contains the textures and behaviours is
blackboxsimulation-shorts-regional-common
this is referenced from the packages
blackboxsimulation-shorts-regional-sd360
blackboxsimulation-shorts-regional-sd330
blackboxsimulation-shorts-regional-sherpa
all of this was created using bundles and groups as we were instructed and advised at the time of release
Everything has been working perfectly under msfs2020 since the relase of this product over a year ago
SU16 now breaks this cross package referencing of both textures and model behaviours as can be seen here
Regards
Antony
BBS
v1.3.0 works normally for me on SU16.
Can you give more details of your installation please ?
Marketplace ? Webstore ?
Installation method ?
@SteamedPhoenix4 @NightMercury358
Just installed the said packages on 1.39.9.0 Steam version:
This is what I get:
Would it be possible that your customer fiddled with “blackboxsimulation-shorts-regional-common” in such a way that it is not mounted anymore by the sim? The Packages window shown above could help diagnose such an issue.
Best regards,
Eric / Asobo
Just for the record - I have now tested all liveries of all 3 aircraft through the DevMode Aircraft Selector and did not see any pink texture.
Best regards,
Eric / Asobo
Also make sure that it’s not GSX fiddling with your models…
@EPellissier we ARE the customer Eric 
Apologies but I don’t get it - aren’t you working for BBS as your profile seems to suggest? 
Or do you mean you are the developer and are seeing this issue since SU16? In that case, I’d suggest you ensure you don’t have leftovers from a partial build of the project somewhere else. Also make sure no DevMode project is loaded (because the built project would be automatically mounted).
Have you checked what the Packages window shows?
Best regards,
Eric / Asobo
@EPellissier Sorry for misleading you
Yes I am with BBS but you asked if “the customer” had fiddled with it …
This issue is apparent with my Own community folder Installation as well as being reported by a customer so I was simply letting you know that it was Myself also with the issue.
We have however discovered that in My own case at least, the common folder for this product had been Disabled (not by me) so We appear to have now fixed this issue and have contacted the customer…
We will let you know if it is somehow the installation of the Update that caused the initial error
Thanks for the information, let us know if the situation for your customer requires further investigations.
Best regards,
Eric / Asobo
Apparently the other client with this issue is on XBOX and using a marketplace purchase
I have suggested he re-install and will report back on his result.
I am not one to normally believe in co-incidence though 
I have had multiple instances in the past where a package doesn’t mount right (almost like a partial mount, as some things still worked) on PC/Xbox if the user installs the package from Marketplace and then immediately tries to use it. This was with scenery, not aircraft, but I always recommend a restart of the sim app before using marketplace purchases.
Disclaimer though: I haven’t personally verified if this is still an issue in the last year or two. I just know I have had it happen in the past.
Not saying this is your issue, but a good step to take when debugging.
