1 minute ago, MammyJammy said:

Only -source and -resolution are required.  All other have defaults that are listed in the User guide.

Ok, thanks. 👍

@AlvegaAny idea where the engine heat blur textures are?

Unless they are compiled in those ALL.dds files in the texture folder.

I want to remove them, I'm over seeing it. Way too exaggerated.

Edited October 17, 20223 yr by blueshark747

2 hours ago, toby23 said:

more the 4k and 8k freeware and payware addon textures, that don't follow the official guidelines and that, as a result, can cause random crashes that I'm more concerned about

Do you have a known offender?  If so I can download it and try.  Dusting off this Texture Optimizer from a few years ago and making it work for MSFS has resulted in a pretty good debugging suite to spot offending textures and work out optimization techniques on 'em.  So far I'm run through FSLTL and most of the AIG airline packages I use (most international carriers, large regionals, and smaller euro/US feeders) successfully.

2 hours ago, toby23 said:

I didn't change any of the default settings. Mipping set to auto by default I believe.

Do you have to add the mipmaps option after the following:

so: textureoptimizer -source "D:/MSFS/Community/fsltl-traffic-base" -resolution 2048

Would become: textureoptimizer -source "D:/MSFS/Community/fsltl-traffic-base" -resolution 2048 -mipmaps auto         

Edited October 17, 20223 yr by RJC68

I don’t know if this is related to this add- on or not, but i took off with 60 fps and about 1-1.5 hours later my fps were cut in half. Flying without traffic at all and still 60 fps an hour later on the same flight. 

9 minutes ago, RJC68 said:

Do you have to add the mipmaps option after the following:

so: textureoptimizer -source "D:/MSFS/Community/fsltl-traffic-base" -resolution 2048

Would become: textureoptimizer -source "D:/MSFS/Community/fsltl-traffic-base" -resolution 2048 -mipmaps auto 

With named parameters, order doesn't matter.  Only that the proper value follows the parameter name.  These are syntactically identical when the optimizer runs:

textureoptimizer -source "D:/MSFS/Community/fsltl-traffic-base" -resolution 2048 -mipmaps auto 

textureoptimizer -mipmaps auto -resolution 2048 -source "D:/MSFS/Community/fsltl-traffic-base"

The default value for mipmaps and dxt is auto. Read the user guide for how the optimizer determines whether it should create mipmaps.  You only need to explicitly specify if you want to force mipmaps on or off, or force a particular DXT format (which may have odd effects with alpha channels for DXT1 and DXT3).

1 hour ago, blueshark747 said:

@AlvegaAny idea where the engine heat blur textures are?

Unless they are compiled in those ALL.dds files in the texture folder.

I want to remove them, I'm over seeing it. Way too exaggerated.

Sorry, no idea.

21 minutes ago, MammyJammy said:

With named parameters, order doesn't matter.  Only that the proper value follows the parameter name.  These are syntactically identical when the optimizer runs:

textureoptimizer -source "D:/MSFS/Community/fsltl-traffic-base" -resolution 2048 -mipmaps auto 

textureoptimizer -mipmaps auto -resolution 2048 -source "D:/MSFS/Community/fsltl-traffic-base"

The default value for mipmaps and dxt is auto. Read the user guide for how the optimizer determines whether it should create mipmaps.  You only need to explicitly specify if you want to force mipmaps on or off, or force a particular DXT format (which may have odd effects with alpha channels for DXT1 and DXT3).

Thank you Sir,

I was just doing a test run while I walked the dog and I see from the finished output log that DXT & MIP MAPS were both on Auto

1 hour ago, blueshark747 said:

@AlvegaAny idea where the engine heat blur textures are?

Unless they are compiled in those ALL.dds files in the texture folder.

I want to remove them, I'm over seeing it. Way too exaggerated.

In each aircraft model folder there is an aircraft.cfg file

For example Airplanes/FSLTL/A20N

I opened the aircraft.cfg with with notepad++ and saw the following

[EFFECTS]
wake = fx_wake
water = fx_spray
dirt = FX_ASOBO_TOUCHDIRT_BIG
concrete = FX_ASOBO_TOUCHCONCRETE_BIG
touchdown = FX_ASOBO_TouchDown_Big, 1
contrail = FX_ASOBO_CONTRAIL_BIG
effect.0 = FX_EXHAUST_LEFT#(A:GENERAL ENG COMBUSTION:1, boolean)#FX_ASOBO_HEAT_BIG
effect.1 = FX_EXHAUST_RIGHT#(A:GENERAL ENG COMBUSTION:2, boolean)#FX_ASOBO_HEAT_BIG

I am however not sure if you can just comment the relevant lines out. I will have to give it a go

Looks like you would need to edit the aircraft.cfg for each aircraft type (Not all the folders with liveries) 

@MammyJammy I don't quite understand the log.

I used resolution 2048 and I get RESIZED OUTPUT LARGER THAN SOURCE - (153), doesn't this mean these 153 textures were 1024 resolution (or less) that were converted to 2048? I wouldn't want that because they can get blurry, or I am wrong? I just wanted to convert the ones that are more than 2048 to 2048.

I also get MISSING MIPMAPS ADDED TO IMAGE - MIPMAPS SETTING: AUTO - (266), does this mean that mipmaps were added only to 266 textures?

Thanks.

2 minutes ago, Alvega said:

I used resolution 2048 and I get RESIZED OUTPUT LARGER THAN SOURCE - (153), doesn't this mean these 153 textures were 1024 resolution (or less) that were converted to 2048? I wouldn't want that because they can get blurry, or I am wrong? I just wanted to convert the ones that are more than 2048 to 2048

That means the output file size was larger than the source.  Likely because of a different compression format or that mipmaps were added.

2 minutes ago, Alvega said:

I also get MISSING MIPMAPS ADDED TO IMAGE - MIPMAPS SETTING: AUTO - (266), does this mean that mipmaps were added only to 266 textures

No, this means that there were 266 images that the Optimizer create mipmaps for where the source images did not have mipmaps at all, yet based on the criteria the optimizer will use to create mipmaps, should have had 'em.  Any other source images that had mipmaps would have them rebuilt when processed calculating out the appropriate number of mipmaps levels based on your chosen resolution size.

2 minutes ago, MammyJammy said:

That means the output file size was larger than the source.  Likely because of a different compression format or that mipmaps were added.

No, this means that there were 266 images that the Optimizer create mipmaps for where the source images did not have mipmaps at all, yet based on the criteria the optimizer will use to create mipmaps, should have had 'em.  Any other source images that had mipmaps would have them rebuilt when processed calculating out the appropriate number of mipmaps levels based on your chosen resolution size.

I see. So everything ok with my log, right?

Thanks.

1 minute ago, Alvega said:

I see. So everything ok with my log, right?

Thanks.

Yup.

I added those warnings simply to provide more info as to what images had some extra manipulation beyond resizing (and some other fiddly adjustments to make sure alpha channels, texture flipping, and compression are done correctly).

1 hour ago, RJC68 said:

In each aircraft model folder there is an aircraft.cfg file

For example Airplanes/FSLTL/A20N

I opened the aircraft.cfg with with notepad++ and saw the following

[EFFECTS]
wake = fx_wake
water = fx_spray
dirt = FX_ASOBO_TOUCHDIRT_BIG
concrete = FX_ASOBO_TOUCHCONCRETE_BIG
touchdown = FX_ASOBO_TouchDown_Big, 1
contrail = FX_ASOBO_CONTRAIL_BIG
effect.0 = FX_EXHAUST_LEFT#(A:GENERAL ENG COMBUSTION:1, boolean)#FX_ASOBO_HEAT_BIG
effect.1 = FX_EXHAUST_RIGHT#(A:GENERAL ENG COMBUSTION:2, boolean)#FX_ASOBO_HEAT_BIG

I am however not sure if you can just comment the relevant lines out. I will have to give it a go

Looks like you would need to edit the aircraft.cfg for each aircraft type (Not all the folders with liveries) 

Thank you sir!🍻

3 hours ago, RobJC said:

I don’t know if this is related to this add- on or not, but i took off with 60 fps and about 1-1.5 hours later my fps were cut in half. Flying without traffic at all and still 60 fps an hour later on the same flight. 

Okay three hours later and fps still at 60. So AI is messed up. Might not be specific to FSLTL.