Hello Team Asobo, and you, Sylvain, Quick question. I was sent to you that you
might know. If I am in the Test Phase of a Beta, doing testing on the Store
compiled, encrypted version Plane, and its been downloaded from MS and
installed on my PC into MSFS, can I ‘also’ do a Build (export a Package, not a
Community version, but Dev virtual version, standard SDK plane) in MSFS and
run that in MSFS, will it over-ride the Store plane? Another words, will my
test plane be seen instead of the store version when loading its file? It
appears to be doing that. I tried it, but would like the official word. I
changed some coding in some of the behaviors in the DEV model files (SDK
center) and the changes were in the plane in the sim, so it appears to over-
ride the identical plane that is from the store. This would mean we wouldnt
need to delete the plane (store version) from the sim just to make tests.
Would be a nice feature. Bill Lionheart Creations
A completed, developed project can be copied into a test version being
uniquely named but otherwise identical. In this way they can be evaluated side
by side and incremental adjustments to the test version, can be edited into
the previously completed version, toward.an update
release. One could accomplish similar with a livery type package, that would
also have to contain and replace the elements being edited. Here, the
replacement is “conditional,” in that the original published “red” version
will have all the original settings, but the addon livery “blue” version, will
have the replacement panel, etc.
I know, another prize winning ‘no available answer’ question. I found that
when you go to delete the test ‘Store’ plane, and you have the ‘Developer’
plane loaded and active, ‘2’ planes appear of the same one in the ‘Content
Manager’. Easy enough to just delete the store model to ensure ‘pure’ testing
in the Developer version. Reloading just takes a short while to redownload.
But would be good to know if we could possibly test both with both on the
drive. ole Bill
We can indeed test both, simultaneously. Two techniques to do so have already
been commented here and this is an excellent opportunity to elaborate on each.
You probably already know that it would be very easy to create a “unique
duplicate,” by changing just a few parameters, name, GUID, etc. Once
completed, you would have a standalone mirror which you can test and evaluate
next to the original. In regard to the “livery Package” duplication technique,
it’s important to remember that anything in the livery package will replace,
or supercede elements from the original Package. So obviously, it will replace
the original livery with it’s own, but one could also swap panels, external
stores loaded, etc and once loaded, will be an available variant of the
original Package. As frustrating as unanswered questions can be, it is my
belief that a vast volume of unposed questions exists. In my own experience, I
spent years reading along at a developers site, hoping people would ask the
questions I needed, before I finally got the nerve to pose my own. This thread
alone has twice the followers as participants and we can only guess the number
of bookmarks. If there is any time we can offer insight, even if it only
remotely relates to our own problems, it can still be valuable imo.