Version: 1.7.7 (Su4 as well)
Frequency: Consistently
Severity: High/Blocker
Marketplace package name: C208B EX
Context: I have a Simobject Patch type mod for the default C208B
Bug description:
If I put any .cfg files inside the SimObjects\Airplanes\asobo_c208b\presets\asobo\c208b_passengers\config\ folder
Then the Sim can’t find the default localization for the C208 specific inputs.
I have an extra button made for the aircraft and I have a en-US.locPak in the root folder that contains the tooltip texts for the button, and it has 2 new actiondb entries as well, but this is across all variants, and only the passenger variant presents this issue, because I added the cargo pod to the cargo page , and had to increase the max_number_of_stations in the flight_model.cfg in it’s preset folder.
If I remove this 1 file , the issue goes away, ( I even tried removing everything else from the mode, and the issue still present, so my above repro should work). If I add these lines to my own localization file it reads them in so I suspect the issue is the sim stops looking for the default loca file in this situation, the interesting part is it only fails with these inputs, no other input, or any other c208b specific localization is impacted, as far as I could find.
Repro steps:
- Make as Simobject Patch type package
- Add the SimObjects\Airplanes\asobo_c208b\presets\asobo\c208b_passengers\config\flight_model.cfg (or any other cfg for this folder) to this package
- Check the controls for the aircraft in the menu
Attachments:
Also there is a high possibility that I’m just dumb and used the localization file structure wrong. But so far the only way I could make my new button show proper tooltip is by using a en-US.locPak in the root fonder.
you should be able to hard code the tooltips (just remove all the TT: entry stuff that reads from the locpak)
the only purpose in using the Localization files is too provide multiple language selections for each entry
you cant ‘add’ variables or actions to the code via the localization files afaik if thats what your trying to do, those are only created in the xml’s
the localization files are just a list to ‘fill in the blanks’ in the xml files with language specific terms
I did some more testing and the described issue is not caused by the localization, even if I removed the localization files, if I have a cfg in the presets , the issue is present.
im not sure what the issue is tbh, your saying its not reading localization files if u add a fm in a preset
that really makes no sense- these localization files are not really connected specifically and should not affect the coding afaik
what is in this fm file in the presets - this seems to be where the issue is
these are ‘merge’ files and normally Only contain edited comments that are Already included in the flight_model.cfg’s from common or an attachment folder
these presets become the “variants” you see in the menu
you would need a partial aircraft.cfg to give it a new menu name and maybe an attached_objects file to comlpete the ‘listing’ for this preset if your not overwriting a default - do you have the aircraft.cfg? or are you overwriting this into a default preset folder?
I know, the fun part is, even if I put in the default cfg (yes the nearly empty one with auto merge) file , unchanged, it affects the localization like in my picture.
Now idea how that can be, that is why I suspect it might be a bug with the modular system.
i dont know what that picture is showing, or why (for all i know its irrelevant- the Loc files are not for coding)
the flight_model is not really connected to the localization file directly, its possible its missing a critical entry if it cant read it but …
these localization files are not necessary for a mod at all- in fact any entry that would be filled by one can be hard written in the cfg
Yes , they are not supposed to be connected. The picture shows the menu / controls section.
I’m forced to use the localization file, I needed the tooltip added in an compiled behavior xml, and I was not able to make it accept hard coded text directly. I would do that if it would accept it. But it only eats localization variables like:
AIRCRAFT.TOOLTIPS.TITLE.BELOW_ICING_MIN_SPD
PUSH_BELOWICINGMINSPD
I had to make a locPak file with AIRCRAFT.TOOLTIPS.TITLE.BELOW_ICING_MIN_SPD
But as I mentioned , even if I remove my localization file, the issue reimains.
The controls specific to the C208 variant , in my case the passenger variant, becomes unlocalized if I put any cfg in the presets folder. I need the flight_model.cfg there because I need to increase the number of load stations so the cargo pod can be shown on the EFB and be loaded with luggage.
So the combination of several factors. But as my testing shows the the menu/controls becoming unloclaized is tied to the fact of having cfg files in the presets folder of my package, or not.
PS.: Might be something to do with the fact that the C208B specific localization looks like to be still encrypted.
PS2.: the localization strings were readable in the .fsarchive file. I duplicated them in my en-US.locPak and added my own button’s text at the end and this way everything works, but this is quite a hack.
