2 hours ago, flyingscampi said:

Because I reduce texture sizes, I usually remove the folder from packages and re-install,but there should be a base package update option.

From discord:

FSLTL Base Models 1.5 available in FBW installer (please close MSFS before updating)

• Added A321F (3 liveries)
• Added A343 (8 liveries)
• Added BCS1 (5 liveries)
• Added SF34/SF34F (11 liveries)
• Almost 80+ new or improved liveries across our existing models (approx 2200 now!)
• Refreshed .vmr file for VATSIM
  • Added F27 to VMR generator (@Andro)
• Config file fixes:
  • Changes to ensure the correct CXA livery is used for live traffic instead of CXA VA
  • Modified DH8D wingspan value to match DH8C to assist in scenery parking design
  • Multiple parking code changes to cover parent/operator scenarios
• Model changes & fixes:
  • Various model tweaks and improvements (LOD settings on A346, animation updates to AT75/AT76, etc)
• Sounds:
  • Removed tire touchdown sound due to issues in MSFS2024 and BATC

(livery list on the website will be updated soon) NOTE: If the update process is taking too long, some people find doing an uninstall and reinstall may be faster as Base Models is downloaded as one large file before decompressing, but YMMV.

Awesome list of updates.

After reading your comments, I decided to try something crazy: I reduced the textures to 512!!! And I have to say I'm amazed. Considering the distance at which I see the planes while taxiing, the quality it's more than enough. But the best part is how much the VRAM drops, even using FBW 320. I've got KSEA and LEMD at fullest like I've never seen since the FS9 days. And my VRAM is at 85-90% with hardly any drop in frame rate. Note: I have LossLess Scale adaptive and AutoFPS (with LOD set to 100).

thank you so much!

3 hours ago, flyingscampi said:

Fair enough! I'm reducing mine to 2K now.

That's what I always do too.

I’ve never done this (didn’t know about it). Currently running it down to 2k for mine (I fly in 4k normally and I mainly use FSLTL models on vatsim and avoid using it normally due to performance.  Tempted to try 512 but will see how 2k goes first! 

4 hours ago, jcomm said:

Wonder if their installer has an option for 2k or even 1k textures?

 

FSLTL developer is radically against reducing texture size, because he values realism above anything else, including performance.

Edited March 14, 20251 yr by edu2703

Delete

Edited March 14, 20251 yr by edu2703

45 minutes ago, edu2703 said:

FSLTL developer is radically against reducing texture size, because he values realism above anything else, including performance.

Well, I don't notice any difference visually between the 4k textures and the 2k, so don't know what's that realism they are talking about. 

9 minutes ago, Alvega said:

Well, I don't notice any difference visually between the 4k textures and the 2k, so don't know what's that realism they are talking about. 

Is the impact of going to 2K all VRAM related, or if not what is the impact on CPU utilization or frame rate if you can tell?  I never get that close to 24Gb of VRAM in use so would not bother to look into the switch unless performance was being impacted at least say 5%.

3 minutes ago, Noel said:

Is the impact of going to 2K all VRAM related, or if not what is the impact on CPU utilization or frame rate if you can tell?  I never get that close to 24Gb of VRAM in use so would not bother to look into the switch unless performance was being impacted at least say 5%.

I started resizing them a couple years ago on MSFS 2020 when I still had my old 4790k with a 2060 Super and it impacted VRAM, FPS and loading times. So I kept resizing them in 2024 when I got a new PC but didn't measure the impact. 

Just finished the resizing, the FSLTL folder was 45.4GB and is now 19GB after resizing to 2k.

By the way, I had to update the layout.json in the FSLTL folder with MSFS Layout Generator after resizing or the traffic wouldn't show up.

3 hours ago, Noel said:

Is the impact of going to 2K all VRAM related, or if not what is the impact on CPU utilization or frame rate if you can tell?  I never get that close to 24Gb of VRAM in use so would not bother to look into the switch unless performance was being impacted at least say 5%.

I was just going to ask the same question. If there’s tangible performance improvements besides VRAM, I’d look into downscaling to 2K.

6 minutes ago, Cpt_Piett said:

I was just going to ask the same question. If there’s tangible performance improvements besides VRAM, I’d look into downscaling to 2K.

I nominate you to carry out the experiment and report back @Cpt_Piett  ... 😉

Hmm need to test the new version. But I think the visibility of other planes and contrails when in cruise , is issue of Msfs24 not FSTL or AIG models. It is Asobo that needs to increase draw distance of other traffic from those 8 nm or less to at least 20 nm like in Msfs20.

1 hour ago, Alvega said:

By the way, I had to update the layout.json in the FSLTL folder with MSFS Layout Generator after resizing or the traffic wouldn't show up.

Not in my case. I reduced them to 512 and it worked correctly without update the .json. Do you move the original files to other folder and renamedthe rescaled ones?