Ff 767 Liveries

[Jeff]

Ive been an advocate for compression for a while now so I can agree. Remove all extras leaving a single Default for each coalition. Let users download and install their own. For campaigns just supply the liveries on install.

That's why I proposed the use of placeholder liveries, replacing the missing livery with a placeholder, but what better way to do this is to basically create a "core default livery" slot or slots, perhaps two or 3 slots maximum, which would be the core-default liveries that are installed with base DCS World core for everyone, and that would be used for the placeholder liveries when the optional liveries aren't installed, so no missing texture. These core-default liveries should go into separate folder structures that are part of the DCS core files to have a good distinction and avoid cleanup/modding confusion.

The MP client will notify if user doesn't have livery packs installed that are used by some players in a server but this may be done in-game if users can change liveries without leaving server, otherwise a notification in lobby when connecting would be enough, but then someone could join with a missing liverly later so this just has to be figured out and it's not the big problem.

It requires updates to a lot of areas, I thought of it as submodules, and they need their own e-shop pages, in-game and on the site, the patching/update system, the whole system for managing this behind the scenes has to be created, probably even some "API" for 3rd parties to register their picks for the core-defaul liveries and submit optional livery packs, preferrably split into several submodules and not a giant 20 GB one if possible.

A a popup of available submodules(liveries in this case, perhaps other assets in future) would show up when a module is being prepared for download ( =272259), with the defaults being to install everything, and then the user can untick as necessary, this way most users will just apply everything and liveries won't be forgotten if there's any fear of that.

This is far better than cutting corners on quality, yes Mig-21 bis team will optimize the liveries with it's big update ... but I hope or rather I expect they mean LOSSLESS optimization, without lowering the fidelity, graphics data is going to get bigger and bigger in future with 10 and 12-bit HDR and WCG and sizes are going to get bigger and bigger. This isn't some way to avoid not even trying some liveries and I don't want it every having that effect, but perhaps a person would try a set for a while then replace it with another set and play with those for another while, so I hope this feature doesn't promote "livery lazyness" and the default to install them all is what should help, people who are into liveries won't just forget about them that easily.

I had originally installed DCS in the HDD. Went the other way round exactly because of the performance impact. Loading times were a pain before more so because I always play DCS in VR, otherwise I much prefer BMS.

So far, I have just replaced the the "texture.house" files on the stock "feelthere PIC 190" folder with the JetBlue livery files. When I started P3D, the plane scheme was partially black, as if the plane was representing itself at night even though the time was set to "day" in the sim. Based on another post I read, I also replaced the last two lines of the "texture" CFG files with:

Alright so I hope you haven't gotten rid of the texture.house folder completely, as those are the textures that the plane refers to for all other liveries. If you have gotten rid of it, you must reinstall the plane from scratch. The way to install liveries is copy over your texture.XXX folder over to the E190 folder and add the lines they give you in the ReadMe file to your aircraft.cfg text file in the E190 folder.

Just like you Zcloudman I copied the House texture config. to KLM texture config. them I went to aircraft config and copied the flightsim 0, basicly like what Axelsubo did in the video. Only I copied and pasted a new aircraft from the original. So the new plane looks like this:

The mirroring is in regards to whether the textures are mirror image of each other.

When the sim came out, some aircraft could only have liveries made whose sides were mirror images, there was no other way at the time.

One side would be correct like DELTA for example, while the other side would read ATLED.

It is very seldom seen now

there is another thing to consider when using these - they actually Add a new mesh component to the model and a new texture, so while this presents no problem normally IF Asobo/ms update the base model of that aircraft these non mirroring liveries would need to be updated. otherwise you would be replacing that newer model file with a modded older one

no big deal really but something you should keep in mind (they should still work fine but would not have w/e update was made)

Just installed Aerosoft Airbus A320/321 from Steam store on my FSX-SE. The base models show fine in FSX but none of the liveries I downloaded from Aerosoft are showing. All were installed using the Livery Manager and I have the "Show Variations" checkbox in FSX checked.

I installed them while FSX wasn't running and restarted my PC but still liveries "no show". I've attached the aircraft.cfg file from the "Aerosoft Airbus A320 CFM" where most of the liveries are installed.

Unfortunately that was not it. I uninstalled one of the Liveries and reinstalled it again from the Livery Manager running as administrator then started FSX and it is still not there. All the Livery files are under the FSX/SimObjects/Airplanes/Aerosoft Airbus A320 CFM/ (in this case it is the Holgers' [A320 NEO CFM EGYPTAIR SU-NEO].

Hey Tom;I went through the post and tired some recommendations. I also uninstalled the Addon completely including the livery manager and installed it back again in Steam (which is running as administrator as well), recycled FSX-SE. Then I installed the Livery Manager ran it as administrator and had the same problem after installing a livery. Would you send me one livery you know for sure works to isolate the problem further?

Apparently, I set the wrong configuration when the Livery Manager ran the first time which is recorded in the Livery Manager livman.ini. I guess it looks for the SimObjects folder where the Aerosoft Airbus was installed and it suggests on the first run the FSX folder, which is fine for the normal FSX, but for FSX-SE addons installed through Steam the SimObjects folder is installed under FSX\DLC\500201. Once I updated the livman.ini everything worked fine.

After the last update to version 31.9.0 my parameter.xml file lost the AIG livery paths and unfortunately I've been unable to fix it. I think that it might have something to do with the new installation path textbox. I've installed my Steam version of MsFs on my D drive. When I direct lfolder0 path to the D\SteamLibrary/Community/aig-aitraffic-oci-beta for instance the program cannot find any of my AIG liveries which it could until the update. Now it's only able to retrieve 22 stock Asobo liveries for some reason... I hope somebody can help me in solving this mystery.

Also, I cannot set Light GA or AIG etc on the PSX app. Ticking the boxes does nothing. By default, PSX sets my default path to users/appdata/roaming MSFS/packages. That is not my install path. I changed it to G:\steamapps\common\MicrosoftFlightSimulator but still get zero liveries.

Edit: Why is PSX searching here ? Community path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Packages\Community

Scanning for liveries ...

G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\Packages\Community does not exist, skipped!

No liveries found!

However, if you want Automatic scan, the MSFS install path shown in the MSFS text box must be ok, if not change it manually. It should be a full path up to (but not included) your Community/Official folders (there where they really physically are), for exanple:

3a8082e126