Hello,
after update 7 and updated warrior model, third party liveries are not working, from the interior cant see the aicraft exterior parts, and from the external view the access door and interior look transparent, maybe suggested changes in configuration files? thanks!
It’s possible they have an improperly created model.cfg file. They probably have a SimObjects\Airplanes\blahblah\model directory. You’ll find a model.cfg file in there. See how it compares to other model.cfg files, and if you find an irregularity, see if correcting that fixes it.
Technically, the Model directory isn’t needed anymore (depending), and you can remove the reference to the model.cfg file from the layout.json of the livery. See if that fixes it.
Edit: I just checked my N276ND livery (on flightsim.to), and it works just fine. I’d compare the structure of my livery vs. that one and see if you can find any differences to figure out what’s wrong. As I mentioned, it’s most likely a problem with the model.cfg file.
Nothing unusual after a Sim update, you have to wait for your favorite liveries to be compatible with SU7.
This is my own created livery, and that’s what I intend to do… update them for the latest SU7, but I don’t know what should I modiffy
Don’t think it’s SU7. This problem occured with the new updates by JustFlight I believe.
I had the same problem with my liveries and simply deleted the “model.xxx” folder and adapted the aircraft.cfg and layout.json accordingly. Worked for the Arrow III and the Warrior II. The Turbos don’t seem to have that problem with the newest version.
There’s a wonderful program for comparing directories and files called Winmerge.
https://winmerge.org/downloads/?lang=en
As I said, my Warrior livery is compatible and I haven’t had to do anything to it since I released it to keep compatibility.
Thank you Flyingscool5650, however could you please elaborate how to do it? I’m not exactly sure which model.xxx should I delete.
thanks!
Well, what I actually would do is winmerge the model.cfg in my livery vs the one in yours. My bet is you’ll find yours is different.
But, the other solution is to edit your layout.json and remove the line with model.cfg in it.
Then, in aircraft.cfg, in the [FLTSIM.x] section(s)
make sure all the Model = lines look like this
Model="" ; model folder
which one is your livery?
Just to confirm, the model.cfg values changed in the latest update to address an issue introduced by SU7.
Martyn - Just Flight
The model.cfg file in the add on repaints needs to be updated with all five values set to true.
That did the trick! thank you Donka73!
Can you give an example, a template to follow please.
Hi Ken,
If you open the model.cfg file under the model folder for the problem livery with a text editor, you will see a few lines of text and 5 of them end with the word false. Simply change this to true and save and the livery will work.
If you need more assistance with this I can share a copy of the file when I’m back at my pc.
Well, that was a lot easier than I thought. Your advice (and time to let my first coffee of the day hit me), did the trick.
Thanks!
Welcome mate.
I only see four lines in the model.cfg that can be changed, as follows:
withExterior_showInterior=true
withExterior_showInterior_hideFirstLod=true
withInterior_forceFirstLod=true
withInterior_showExterior=true
What’s the fifth?
That’s the four that changed.
Martyn - Just Flight
