• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS [GUIDE] Creating Livery Packages for MSFS

Not sure why you need to include the whole model file? Just alias it. Distributing a modified model file does not sound like a particularly good idea especially without permission of the original devleoper.

Adding via the FSX way is hacky and requires the user to do more. We should be looking at this new way as the future (and it is). Why are you trying to go backwards?


And your point? I use the registration NOVA24. Its there as a placeholder for users to set what they want. Are you going to police every user of your livery to make sure they ONLY use a VALID registration number? Let ASobo have their marketing.

The whole model file - because it works for me atm. I have no plans on sharing my work until I can figure out what I am doing wrong. Why do some megapack liveries seem to work, when mine don't despite having an identical layout as far as I can see - and I have been checking since day one. I found one fault once where I had a period instead ov a comma. The only thing I am left with now is having 4096 hi-res dds images that are larger than the Asobo standard. I might have to edit in the exact flle size into those ....DDS.json files and also find out how the creation date conventions work.

The FSX way was never hacky in FSX, and since the orbx marketed aircraft all live in the community folder, then the fallback coding really is straightforward. Like I say - I won't know till I try.

So you use a personal and fictional Identification. I have no problems with that. But it is not real-world authentic, and when I do paints of realworld aircraft, they are primarily with the owner's express permission so that the liveries reflect that aircraft as realisticall as possible (and save me from getting copyright lawsuits filed against me). And if my liveries are fictional, then so are my registrations - I do check international registries wherever I can. For me "Authentic" is the be all and end all. of a repainter's true worth. As for policing every user - Do be brief, man! If microsoft couldn't do it... but they never publishe a livery or model without clear reference to copyrights and granted permissions from the realworld counterparts. Airbus, Boeing, Kenmore seaplanes... and neither Fs 9 to FSX nor msfs have ever been different. They are spotless as far as possible, with what they sell.

Anyway, that is just my view on repainting. Will I be sharing mine? Possibly - if I live long enough. Just like I shared the hundreds I have already shared. And yes, some of mine did break the copyright rulings. And yes, I did have problems with one copyright holder threatening a "cease and desist". But since then, any of my liveries all had the owner's seal of approval. From Patty Wagstaff through many more. And I do warn the owners that I don't wish to be held accountable if my liveries are bu66ered around with.

Yeah - I am a nut job. I don't care what anyone else does... ;)

Picture attached - fictional w-i-p The next time you see it, it will hopefully be in-sim (health willing)
 

Attachments

  • Jab170trial3.jpg
    Jab170trial3.jpg
    106.7 KB · Views: 31
Agreed. See above. Which is why I keep asking how to get this damned problem right. No one has yet given me a workable answer. Not even your guide works for me. Sorry.
Yea I might have some updated stuff. I mainly did this for @Novawing24 and other painters I know who were asking about how to do livery packs as I mostly do aircraft. I have the Jab so let me see what I can come up with tonight.
 
The whole model file - because it works for me atm. I have no plans on sharing my work until I can figure out what I am doing wrong. Why do some megapack liveries seem to work, when mine don't despite having an identical layout as far as I can see - and I have been checking since day one. I found one fault once where I had a period instead ov a comma. The only thing I am left with now is having 4096 hi-res dds images that are larger than the Asobo standard. I might have to edit in the exact flle size into those ....DDS.json files and also find out how the creation date conventions work.

The FSX way was never hacky in FSX, and since the orbx marketed aircraft all live in the community folder, then the fallback coding really is straightforward. Like I say - I won't know till I try.

So you use a personal and fictional Identification. I have no problems with that. But it is not real-world authentic, and when I do paints of realworld aircraft, they are primarily with the owner's express permission so that the liveries reflect that aircraft as realisticall as possible (and save me from getting copyright lawsuits filed against me). And if my liveries are fictional, then so are my registrations - I do check international registries wherever I can. For me "Authentic" is the be all and end all. of a repainter's true worth. As for policing every user - Do be brief, man! If microsoft couldn't do it... but they never publishe a livery or model without clear reference to copyrights and granted permissions from the realworld counterparts. Airbus, Boeing, Kenmore seaplanes... and neither Fs 9 to FSX nor msfs have ever been different. They are spotless as far as possible, with what they sell.

Anyway, that is just my view on repainting. Will I be sharing mine? Possibly - if I live long enough. Just like I shared the hundreds I have already shared. And yes, some of mine did break the copyright rulings. And yes, I did have problems with one copyright holder threatening a "cease and desist". But since then, any of my liveries all had the owner's seal of approval. From Patty Wagstaff through many more. And I do warn the owners that I don't wish to be held accountable if my liveries are bu66ered around with.

Yeah - I am a nut job. I don't care what anyone else does... ;)

Picture attached - fictional w-i-p The next time you see it, it will hopefully be in-sim (health willing)
No dramas.

The tool I alluded to earlier available on this forum has been invaluable for compiling the layout.json files for my set packages.

In regards to the registration, if you modify the panel.cfg and adjust the registration entry size to be a single pixel it "disappears" and allows the texture underneath to show through, so even if the user adds a registration it won't show. You also won't end up with a block of polygons showing blank.
 
No dramas.

The tool I alluded to earlier available on this forum has been invaluable for compiling the layout.json files for my set packages.

In regards to the registration, if you modify the panel.cfg and adjust the registration entry size to be a single pixel it "disappears" and allows the texture underneath to show through, so even if the user adds a registration it won't show. You also won't end up with a block of polygons showing blank.

The "Jason" tool... Yep - me too. But it's not actually the answer to my problems. I use it. Also, deleting the existing layout reduces file quantity by 1, so when the tool runs, I can create a layout with 23 or 24 files before saving the layout.json. Should I reduce it by one more and delete the manifest too and insert it after I create the layout.

Panel.cfg - Yep, I reduce both to interior and exterior to zero actually.

That's why I found FSX addon texture so much easier - not so much farsearting around. I understand the guide from s3rious (which OzWookiee shared) and I understand the auto.json tool and still I can't add a livery to the community folder. And still others have added good liveries that work. Mind you, I am not in ideal health. Perhaps I had a brainfart somewhen and I can't see the wood for the trees anymore...

But I will get the hang of it one day, even if Covid gets me the next... :scratchch
 
Okayyy...

Progress! The IRIS Jabiru is in the community folder. It has a standard aircraft.cfg. I can create a new texture folder. IT WORKS (mind you, I didn't expect anything less from IRIS)

...and it is a D sight easier than all that faffing around with Asobo madness ;)

Oh yes; it is still w-i-p and distribution would be safe and legal.
 

Attachments

  • IRISgreat.jpg
    IRISgreat.jpg
    155.4 KB · Views: 46
  • JabiruStbdLowObl.jpg
    JabiruStbdLowObl.jpg
    147.3 KB · Views: 48
  • JabiruParkedThree.jpg
    JabiruParkedThree.jpg
    287.8 KB · Views: 41
  • JabiruInDaHouse.jpg
    JabiruInDaHouse.jpg
    249.3 KB · Views: 53
@OzWookiee and co.

I have the Jabiru and the LongEZ both repaintable in my community folder - the beauty is that they work simply by adding a new [FLTSIM.xx] block to the aircraft.cfg - IRIS has the edge for providing an excellent set of PS paintkit textures, but the LongEZ is slightly more fun to fly at really low levels.

Some odd things are different between aircraft:

1. The Rutan uses an = sign between separate [FLTSIMxx] blocks, the Jabiro not.
2. Jabiru: ui_thumbnailfile="SimObjects\Airplanes\IRIS_J160\Texture.VH-KLB\thumbnail.jpg" - Rutan: ui_thumbnailfile=""
3. The Jabiru has one model folder per livery (eg model.19-5396) and also has two version models - the C and D. Rutan uses just one - I actually think I can see the logic there so not really confused

But none of those are really major.

What remains confuddling though, is that this method works, even through the updates to msfs, yet the 3rd party liveries for msfs aircraft in the official\onestore library often cause msfs to "sulk" when a new game update is installed - such as the marketplace disappearing or the content manager freezing. Most of these are using OzWookiee's guides - well, the GA piston engined aircraft. I hate flying tubes in simulators, so unreal and so "boy racer"ish for me ;)

More grievance is caused by the fact that the aircraft I really wanted to paint in msfs (especially in the premium and deluxe versions) are almost impossible to paint because of that DRMProtection flag being set in the manifest.json - ah well... Oh, and third-party devs are in on the act too - Carenado's aircraft are similarly DRM locked

Anyway, does anyone know a definitive, fully functional, msfs/Asobo approved way to add our liveries into community and not have to move them out every time msfs updates and we have spent days trying to fix? And is there a (legal) way to repaint DRM protected models? And will msfs/Asobo ever realise that mirrored textures are anathema! (Incidentally, they do know about that - there is a comment in the SDK that more or less says they do this deliberately to save data space, so "Concretus Scatus" ;)

Two proofs of concept below:
 

Attachments

  • JabiruStbdLowObl.jpg
    JabiruStbdLowObl.jpg
    147.3 KB · Views: 35
  • LongEZTues10.jpg
    LongEZTues10.jpg
    351 KB · Views: 36
Okay ....finally got my Repaint to show up in sim ....but no textures just a clay Aircraft ..like i would see in 3ds max prior to texturing
first image is what i should be seeing( A textured aircraft).....2nd is what i am seeing
 

Attachments

  • 2021.02.10-01.07.png
    2021.02.10-01.07.png
    3.6 MB · Views: 10
  • 2021.02.10-01.07_01.png
    2021.02.10-01.07_01.png
    3.3 MB · Views: 10
Top