7 hours ago, himmelhorse said:

Hello mate,

I am really surprised nobody has mentioned a manual for MSFS before this. (he says, hunting through previous topics and posts.)

A MANUAL is sorely needed      + 37,592,019,595 bumps

Tony

I made a wishlist item for this.  Sitting at 76 votes right now.  If more people vote for it, it might end up in the Feedback Summary 😉

https://forums.flightsimulator.com/t/add-a-learning-center-or-other-official-documentation/284765

49 minutes ago, Midnight Music said:

The freeware developer community has already figured out a fix to the livery issue. Updated paints will be forthcoming.

https://flightsim.to/blog/flight-simulator-patch-1-10-7-0-brakes-liveries-heres-how-you-fix-it/

Lee

Great news! Many thanks to you and the marvelous freeware developer community

Sten-Ake

53 minutes ago, Midnight Music said:

The freeware developer community has already figured out a fix to the livery issue. Updated paints will be forthcoming.

https://flightsim.to/blog/flight-simulator-patch-1-10-7-0-brakes-liveries-heres-how-you-fix-it/

Lee

Does anybody know if this is now a "feature" going forward, or will this just be necessary until there is a fix?

4 hours ago, Midnight Music said:

The freeware developer community has already figured out a fix to the livery issue. Updated paints will be forthcoming.

https://flightsim.to/blog/flight-simulator-patch-1-10-7-0-brakes-liveries-heres-how-you-fix-it/

Lee

Good catch, but that solution has a syntax problem which will not work for most addon liveries but probably works for the specific example. Here is the wrong entry in the layout.json file (edit: I mean as far as MOST add liveries are concerned).

"path": "SimObjects/AirPlanes/Asobo_A320_NEO_LIVERYNAME/MODEL.LIVERYNAME/model.cfg"

The entry above in bold is the mistake.The layout file HAS to reference precise file names. The above file reference has 3 underscores then the livery name. The sim cannot read this file because it doesn't exist for the vast majority of addon liveries because the above example refers to a custom-made folder that is not standard. For the vast majority of livery addons, the path should actually read thus:

"path": "SimObjects/AirPlanes/Asobo_A320_NEO/MODEL.LIVERYNAME/model.cfg"

You also need separate model folders for EACH separate livery. As an example: You want to add 3 liveries to the default livery. So in your simobjects folder you have this:

Texture.A

Texture.B

Texture.C

You now need to also create the following folders:

Model.A

Model.B

Model.C

Each model folder must contain a model.cfg file that is just a repeat of the standard model.cfg that references the standard interior and exterior models.

Each of the texture and model folder names and file names need.to be referenced in the layout.json file.

In the aircraft cfg file, the first FLIGHTSIM.0 entry only needs this model reference 

Model=""

The rest of the FLIGHTSIM. 1/2/3 entries need to have this:

Model = "A"

Model = "B"

Model = "C"

To save time I recommend one of the two auto-layout tools which work very well and save you hours of work fixing the liveries issue that this sim update has generated.

So you can see what utter chaos Asobo has created here - with an update that didn't even intend to interfere with the community liveries, but they have somehow managed to do so, and it now appears they are blaming this on "user error". I have to say that is outrageous!

As to why some people are having no problems seeing added liveries, I don't know the reason, except that it probably has nothing to do with whether you removed files from your community folder before the update. It could be connected with some kind of file or folder caching.

But the point is that Asobo CREATED the community folder precisely so you could install modded and custom content. You shouldn't have to remove mods or additions just because there is a general sim update, in the same way Microsoft doesn't expect you to move all your documents, images and programs somewhere else just because there is a Windows 10 update.

 

 

Edited October 30, 20205 yr by robert young

38 minutes ago, robert young said:

Good catch, but that solution has a syntax problem which will not work. Here is the wrong entry in the layout.json file:

"path": "SimObjects/AirPlanes/Asobo_A320_NEO_LIVERYNAME/MODEL.LIVERYNAME/model.cfg"

The entry above in bold is the mistake.The layout file HAS to reference precise file names. The above file reference has 3 underscores then the livery name. The sim cannot read this file because it doesn't exist. The path should actually read thus:

"path": "SimObjects/AirPlanes/Asobo_A320_NEO/MODEL.LIVERYNAME/model.cfg"

 

I haven't followed this issue in detail, I think you may be misunderstanding what that fix is suggesting, Robert.  The thrust of this change is not modifying anything in the stock aircraft directory.  It's just adding a model.cfg to the folder used by the livery itself and referencing it from the variation configuration.

I'd also be surprised if you needed to provide a different model for every livery, I'd suspect as long as they reference a model it will probably be sufficient.

I'd be interested in folks who have this problem trying something:  don't add models to your livery folder, just add model="" to every FLTSIM.x section.

It's possible Asobo made a more comprehensive change than I thought, but I have a hunch that would work and would be a good bit less effort.

(Apologies if this has already been tried and doesn't work...  I haven't had any time to experiment with this myself yet.)

 

 

Additionally, do we have confirmation that the exact same liveries that worked for one person don't work for another?    A fair number of liveries already came with their own model.cfg and I'd suspect they'd work without any changes, that might be why it's a problem for some folks and not others, perhaps?

I have liveries with the 'model.cfg' file that also don't work.

Its all very strange. First time I got the sim to load after the patch, I had the liveries working - including those WITHOUT the 'model.cfg' file.

Later, the liveries problem started, and now its just broken!

Strange.    I just wrapped up some work and did some testing myself with some C152 liveries that didn't have a model.cfg but did reference model="" in the aircraft.cfg and that worked, as I would think.    But then I commented that out so they had no named model config, which I would think would break it if the solution linked here is the problem... but they didn't break at all.

Bizarre.

1 hour ago, kaosfere said:

 

I haven't followed this issue in detail, I think you may be misunderstanding what that fix is suggesting, Robert.  The thrust of this change is not modifying anything in the stock aircraft directory.  It's just adding a model.cfg to the folder used by the livery itself and referencing it from the variation configuration.

I'd also be surprised if you needed to provide a different model for every livery, I'd suspect as long as they reference a model it will probably be sufficient.

I'd be interested in folks who have this problem trying something:  don't add models to your livery folder, just add model="" to every FLTSIM.x section.

It's possible Asobo made a more comprehensive change than I thought, but I have a hunch that would work and would be a good bit less effort.

(Apologies if this has already been tried and doesn't work...  I haven't had any time to experiment with this myself yet.)

You have a point. However the syntax of that proposed fix is clearly targetted to general modding and livery additions, but it might work ONLY for the specific mod it refers to, and that is because there IS a file with those under-scores. My point is that though the intention is noble, that fix is not universal. What I set out was an example where someone is attempting to simply make an addon livery work.

Most livery mods refer to the default aircraft and its model. So what I tried to do was give tips on the most typical case, which is that someone creates extra liveries for a default aircraft. In that example I think my corrections are valid.

As to whether you need to add multiple model folder entries for a standard livery addon, the answer is most definitely yes, because I tried assigning each FLIGHTSIM.x entry to one master model folder and it did not work. I had to create an individual model folder for EACH of the texture variations for it to work. I concede that others might have found a way around this.

But my central point is that before this update by Asobo, you didn't even need to fiddle around with model folders at all. In fact if you look at V1 and V2 of my Bonanza mod, you won't find any reference to models. The sim accepted just the textures and automatically found them in the hanger and sim. Each FLIGHTSIM.x entry in the aircraft cfg references the default model. There was no need to add model folders. That is why I stick to my point about this. The update has forced hundreds of freeware and payware developers to spend hours and hours hacking through in some cases up to 300 livery files just because Asobo did not quality-test their update.

Edited October 30, 20205 yr by robert young

Well I take back what I said about liveries working fine for me after the update.  Yesterday I could select a different livery but today I cannot, the one I first chose is now locked in place. 

This morning my Liveries worked. Have not checked since, because I'm waiting for a working throttle fix.

Edited October 30, 20205 yr by DJJose

There's now updated liveries starting to appear on the various addon sites which have been altered to work with the recent update.

7 hours ago, robert young said:

The update has forced hundreds of freeware and payware developers to spend hours and hours hacking through in some cases up to 300 livery files just because Asobo did not quality-test their update.

Oh yeah, I'm not arguing with you about the unfortunate aspect of it at all.   Was just hoping to find the "least effort" solution for folks.

37 minutes ago, kaosfere said:

Oh yeah, I'm not arguing with you about the unfortunate aspect of it at all.   Was just hoping to find the "least effort" solution for folks.

Actually Rob, I wonder if I can ask for your assistance on this very subject. Can I PM you and ask for your advice?

20 hours ago, himmelhorse said:

 

A MANUAL is sorely needed      + 37,592,019,595 bumps

 

About as many pages as well