September 3, 200619 yr Author Commercial Member It seems (in my case anyway) that the bluriness is indeed a mip map issue. I opened the Baron's main texture (.dds) in DXTBmp and saved it as a 32 bit .bmp without mips. I then opened it in PhotoShop, flipped it vertically (thanks Bill), made some minor modifications to it, and saved it. Another save in DXTBmp (PhotoShop bitmaps crash FSX just as they did in FS9, BTW), followed by deleting the original .dds texture from the texture folder, and the blurries were gone. I also tried DXT 3 and DXT 5 with similar success and both looked great.I mentioned above that simply saving the .dds texture caused them to dissapear in the sim. This happened apparently because I had saved them without mip maps. Evidently .dds textures must have mips. I tried it again, this time including the mips and the textures worked fine.I experimented with the new texture.cfg feature by creating a new texture folder for the CRJ and dropping only a modified main texture bitmap into it. I then copied a texture.cfg specifying the main texture folder as the "fallback folder". It worked great, although I don't think the texture.cfg was really necessary in this case as it appears that by default the sim will fallback to the main texture folder for any missing textures without the help of the texture.cfg. It would apparently be necessary however if for some reason you wanted it to fallback to "texture.1" or "texture.2", etc. when missing textures were encountered, rather than simply "texture". I'm sure there are many more possibilities with the texture.cfg that I haven't discovered yet. This is a great improvement over FS9. Repaint downloads need now only include bitmaps that have been modified.The mirrored texture problem is also gone on the default aircraft I've looked at, so "inside out" N-numbers and lettering on one side of the fuselage should be a thing of the past. I predict that we'll see a lot more repaints and paintkits for the default aircraft in the libraries than we've ever seen in the past.OK, so that's one hurdle I've gotten over. Next...Jim
Create an account or sign in to comment