If you don't repaint.. Learn!

[BLAZE]

I'm here to tell ya.. If I can do it ANYONE CAN!

[Hagar]

All you need to do this, is download a free copy of a (.bmp converter) I'm not sure
where to get one now-a-days, the one I used seems to be 'not available' anymore
but i'm sure you will find one out there somewhere.

DXTBmp by Martin Wright. Get the latest version here --> http://www.mwgfx.co.uk/programs/dxtbmp.htm

[Strategic Retreat]

I mean no disrespect but... I thought this was a old-as-dirt mod for FS9... I remember it being quite the discovery back in 2005~2006, when graphic cards were still not up to withstand some of the heavier textures on graphic intensive add-ons or even default parts of the simulated world, and the various planes liveries blurred something ugly most of the times...

I guess it's time for a re-discovery, as often happens.

[garryrussell]

Don't use DXT3 for main airframe unless you have to as it is a compressed format.

32bit 888-8 is much better and that difference can often be seen in detailed paints especially fine subtle effects with gradient fades like dirt and wear.

As here




On the left is 32bit 888-8 and the right the same texture DXT3...the compression uses less steps so the fine gradient becomes blotchy as values are combined due the less information a compressed file contains.

[Strategic Retreat]

the compression uses less steps so the fine gradient becomes blotchy as values are combined due the less information a compressed file contains.

DHT3 is not THE FINAL SOLUTION to the problem, but sure as hell is a solution for 90% of the liveries. The info loss is felt only on some liveries, in others there's almost no quality drop.

The correct suggestion may then be to try and compress the liveries and then see if they are still good BEFORE to get rid of the source uncompressed 32Bit textures. If the quality drop barely registers, then OK. On the other hand, should the compressed texture be visibly compromised instead, better find another solution.

[garryrussell]

The difference is always there and can be found although it doesn't always spoil things too much

As to keeping the 32 bit...The layered doc should of course be kept which serves as an original and most people would copy the HQ BMP from their project file into the aircraft folder so there shouldn't be a danger of overwriting the original with a compressed file

DXT3 was necessary in the days of struggling machines but not really need now.

[BLAZE]

Thanks Mr. Hagar for putting the hyper link up there.

Yeah guys, I am using an old dinosaur. I guess this method is out of date
these days. :-/

I'm using an '04 sony computer. I can't afford a new PC. I got carried away
by the visual improvement over what it was like. BLAAAAACHH!:P

It's a shame cause the computer I'm using to write this is only a year old.
I wish I could use this one.

Yeah I would love to use 32 bit but it kills the frame rate. Like for instance
these awesome new releases from Vitavia/Alpha, 'get this' I'm rolling out the
door at a whopping (4-FPS) Ahhh.. good times!

It gives me a good idea of how many panels are used on the fuse, as I watch
the aircraft being built every time I switch to spotter mode. 

[garryrussell]

The whole point is to maintain the highest quality you can hence the 32bit, however sometimes you just can't and DXT3 helps out.

Mostly you won't see it unless you look.  I always compromise by just compressing detail and interior maps that don't show much change, nothing visible and leave the main airframe maps in 32 bit.

But needs must and DXT3 will keep you moving just as long as the mips are removed as most cards don't need them and it causes problems...having said that I know of one person who has jagged aircraft unless the mips are on, but that is rare now.