@DA40CGDFQ , asobo-aircraft-da62-sdk is the
package name of the sample DA62 sdk. If your package name is mycompany-
aircraft-toto , you would put " @mycompany-aircraft-toto, " before TT.
You can either put this in the Aircraft Editor > Camera > Ui Title
corresponding to your camera or in the camera.cfg UITitle=“@mycompany-
aircraft-totoTT:GAME.PANEL_CAMERATEST…”
ok this works, however there is now an inconsistancy with quotes. without the
@ modification, the AE saves with quotes. with the @ modifier it save without
quotes. The @ one has no quotes, the instrument02 is changed to 03, has
quotes.
Why the difference here compared to XML? Or is this a new requirement for XML
as well? Can we please ensure that this is documented for ALL developers?
i’m in SU12 Beta, and used AE as the input. I did not use a text editor. First
I input in AE with quotes, that did not work, then I added without quotes, and
did a save resynch. then worked.
That’s an interesting example to use, I don’t see that anywhere in the
definition of the DA62 sample model? it appears to actually be @DA62_SDK_AIRCRAFT? Is this going to be a normal thing? that the package name
be used hardcoded into items? I’m confused as to which is the package name. Is
it the name of the directory containing the whole package, or the directory
the VFS sees… the directory in the SimObjects\Airplanes? If it’s the package
directory, doing this is going to cause problems for me. It’s really important
to me that my Community directory be organized. So I rename the package
container directories by type, like aircraft–blah and scenery-nh–blah and
objlib–blah. (Technically, I wish author was the last item in the name, but
that’s not important). So if the package directory name is hardcoded into
files in the package, I’m not going to be able to keep my Community directory
organized. Makes me very, very sad. I so wish we could put packages in
directories in the Community directory like we used to in all prior versions
of FS. That would help a little bit (I still hate organizing the directories
by author).
I’m very confused now. Is this Cameras.cfg specific? Or variable specific? In
aircraft.cfg I’m having a similar problem. If I create local localization file
en-US.locPak in the root directory of the base aircraft package (and add it to
the layout.json),
I find the the description, ui_model, and ui_manufacturer variables work (as
well as any clickspot names and other stuff), but the ATTCOM variables don’t
work (I swear this worked prior to SU12, maybe SU10 timeframe last time I
noticed?, but maybe I’m mistaken. I still have some testing to do). You’re
saying I need to add the @ package_directory_name in front of the TT for the
ATTCOM variables, but not the others? As I said, I still have to do some
testing, but, I swear if I do all this in a livery, even overriding what’s in
the base package, it works straight out without the addition of the package
name prior to TT. Is this base package specific? Again, I might be wrong.