From their Discord

@everyone

**FSLTL Base Models 1.7.0** available in FBW installer

**IMPORTANT: ** We HIGHLY suggest uninstalling your currently installed Base Models before installing this version. Not uninstalling first can leave old and orphaned folders behind that are no longer used.

__(please close MSFS before updating)__

**__New:__**

- Added B77WF

- Added CRJX

- Added DHC6

- Added E290 (Thanks <@466016096508575744> !)

- Added E75L

- Liveries:

- 150+ new or updated real-life and historical liveries

- 250+ new or updated VA liveries

- Over 2800 liveries now

**__Updates:__**

- Model changes and fixes:

- A21N - Rebuilt animations and configs; added fan blade animation

- B77W - Rebuilt animations and configs

- BCS1 - Rebuilt animations and configs; smoother engines and tires

- DH8C - Rebuilt animations and configs; added missing elevator

- E170 - Rebuilt animations and configs; added steering animation

- Lighting:

- Added newer lighting setup to all newly added models + rebuilt models listed above

- Work continues to add to remaining existing models

- Landing gear culling improvements:

- Model changes to improve visible distance of landing gear objects applied to all newly added models + rebuilt models listed above

- Work continues to add to remaining existing models

**__Misc:__**

- VATSIM .VMR changes - See separate post

- https://discord.com/channels/781587165989175386/1563984189513273506/1563984625716560064

Livery list on the website has been updated.

We have some major changes on the horizon that will hopefully allow us to release updates much more frequently. We'll have more details in the near future.

13 hours ago, grandfred29 said:

- Landing gear culling improvements:

- Model changes to improve visible distance of landing gear objects applied to all newly added models + rebuilt models listed above

- Work continues to add to remaining existing models

I'm doing a flight from Zurich with the new models and had a look around. The parked B77W aircraft had their landing gear showing at distance while other types didn't. So it looks like they have improved the landing gear culling issue. Once they've updating the other types, it might not be an issue any more.

I appreciate what FSLTL are doing, but it was fine before Asobo moved the goalposts on the LODs, causing people all this extra work for no good reason.

7 hours ago, BruceA320 said:

I'm doing a flight from Zurich with the new models and had a look around. The parked B77W aircraft had their landing gear showing at distance while other types didn't. So it looks like they have improved the landing gear culling issue. Once they've updating the other types, it might not be an issue any more.

Main gear is better, nose gear not so much.

Sorry- but I'm a Discord ijut- do we install all 3 vmr's for vPilot in priority 1, 2 and 3.... or is there just one preferred?

Ta- C

Thanks, FSLTL for your hard work!!

1 hour ago, cavaricooper said:

Sorry- but I'm a Discord ijut- do we install all 3 vmr's for vPilot in priority 1, 2 and 3.... or is there just one preferred?

Ta- C

You just need one. Option one seems to be the favorite among users.

It is up to you to decide which .vmr file best matches your needs/wants. ONLY ADD ONE FSLTL .VMR FILE TO VPILOT! We highly suggest you experiment and find the option that works best for you. Don't like any of them? Create your own!

========================

Available option files:

Option 1: You prefer the model to be correct or close with only same-family fallback, even if it means a blank livery.

Option 2: You prefer correct airline matching over model matching. This is more similar to the old .vmr. The closest available model/livery will be matched, same model family or not.

Option 3: You prefer the model to be correct or in-family, but are ok with model substitution for models not in Base Models. No airline livery for the model, but the model is included in Base Models, you'll see a blank exact match model. No airline livery and we don't have that model, you'll see an airline livery on a fallback model we do have.

========================

As always, and regardless of which .vmr you use, what you see in VATSIM highly depends on what information the other pilot is using for airline code and model, which .vmr files you have added to vPilot and in what order those .vmr files are used.

The examples below try to explain what each .vmr file option will show based on what a VATSIM pilot entered assuming you are using no other .vmr files:

Example 1:

VATSIM pilot: AAL B738

Option 1/2/3: AAL B738

Direct match

Example 2:

VATSIM pilot: AAL B736

Option 1/2/3: AAL B738

No AAL B736 livery, AAL livery is available for a model in the same family

Example 3:

VATSIM pilot: AAL BCS1

Option 1: Blank BCS1

No AAL BCS1 livery and no AAL livery available for any model in that family

Option 2: AAL A319

No AAL BCS1 livery, AAL livery on closest model in size is chosen

Option 3: Blank BCS1

No AAL BCS1 livery. Other AAL liveries exist, but blank BCS1 is chosen to be model-accurate

Example 4:

VATSIM pilot: AAL CONC (Concorde)

Option 1: Blank A21N or A321

No AAL CONC livery, no CONC model available, model we do have is chosen as closest in size

Option 2: AAL A21N or AAL A321

No AAL CONC livery, AAL livery on closest model in size is chosen

Option 3: AAL A21N or AAL A321

No AAL CONC livery. No blank CONC available. AAL livery on closest model is chosen

Do they offer a low res option ?

No but you can use Ordenator or other tools to reduce to 2k or 1k and compute Mipmaps.

But don't forget to rebuild the layout.json after, otherwise you won't see them in FS24.

Edited October 29Oct 29 by roland_lfor

thanks

Thanks @Wise87 appreciated! I had originally 1 and 2 and 3 installed and so removed 2 and 3- appreciated!

C

I was just about to reinstall FSLTL, as I haven't used it since moving to MSFS2024. Thanks for the heads-up.

Is applying the PUSHBACK modification (changing the value from 1 to 0) recommended for the v1.7.0 models ? I did a quick check after installing v1.7.0 and I did not see any A/C movement (KJFK).

On 10/29/2026 at 12:48 PM, roland_lfor said:

No but you can use Ordenator or other tools to reduce to 2k or 1k and compute Mipmaps.

But don't forget to rebuild the layout.json after, otherwise you won't see them in FS24.

I used textureoptimizer and Compressonator yesterday to reduce the textures down to 1k and then I did a flight with version 1.7.0 of the files and everything went well. I used option 3 for the VMR and all liveries appeared fine at both airports.

1 hour ago, xsever said:

I used textureoptimizer and Compressonator yesterday to reduce the textures down to 1k and then I did a flight with version 1.7.0 of the files and everything went well. I used option 3 for the VMR and all liveries appeared fine at both airports.

I reduce mine to 2k, do you notice any performance improvement by reducing them to 1k instead of 2k?