Chris H wrote:If memory serves I started investigating and started to draw some conclusions (believe it or not) based on what program you use to do the conversions, I'm rather hazy and I'll try and dig up the tests I completed but it was something to do with DXTBmp and mips as opposed to Imagetool and mips.
That's also very interesting...I've always used Imagetool although I do have DXTBmp as well :think:
I would be very interested to hear of anything you find out
On occassions I've used Imagetool, a texture has been reported as having no mips despite it seeming to have one in the sim :o Resaving through DXTBmp has removed whatever was lurking making the same texture sharp throughout. I gave up on Imagetool for that reason though many swear by it
I always used to use DXTBmp but made the swap to Imagetool since I can't get DXTBmp .dds textures to play ball in FSX at all even though others have no problems.
Once again very intriguing, I'll will see if I can dig up what I found out, although I'm beginning to wonder if there aren't multiple versions of DXTBmp floating around.
There are indeed multiple versions of DXTBmp floating around. I had a problem with a texture last year some time and GarryR explained what to do with it in DXTBmp.. thing is, I didn't have the option he was telling me about in the version I had!! :o Turns out my version was an earlier one :roll: The latest I know of and the one I use now is 4.00.79 which has dds support ;-)
Peter I understand what you are saying re no mips on DXT1 images, my question is is there a program that will look at the texture folders in FS and batch convert all dxt1 images to have mips? if not what is the best way of finding those that do not have them?? I worry it means a manual search which could take forever?
cheers Tony
AMD Phenom II X4 BE 965 @ 3.80GHz
nVidia GTX 560 TI 448 Cores
It is very difficult I know, but Holger Sandmann recommends locating the Scenery item that causes the blurries in the area in question, by a process of illimination...It seems that the best way to do this is by UNticking areas in the vicinity, in the Scenery Library. By restarting FS after doing this each time, you should eventually find ONE that causes blurries when it is ticked and not when unticked. Naturally, this is by no means the end of the story as you now have to search that particular package for its offending article. I'm afraid I know of no Batch file or application that can automate this search and it can certainly take some time opening Textures one by one in Imagetool to look for a DXT1 with no mips...However, Holger is adamant that whenever he has fixed one of these things, it has always been one rogue DXT1 with no mips that has caused the problem.
Would be a wonderful little application to have..."Search and Eliminate DXT1s with NO Mips!"...An excellent opening for a programmer :think:
I think you may be talking about a very effective Batch file by David Maltby that changes his 32 bit textures to DXT3 with or without Mips. It is not really applicable as the culprit texture would be in scenery rather than an aircraft folder. However, it is possible for an aircraft with certain textures to create blurries in the scenery near the aircraft, but here we are talking about severe blurries only occuring in specific scenery areas with ANY aircraft.
BTW David's Batch file syntax has proved very useful to me when making my own Batch files, some of which you have
