For more information, feel free to browse the Texture Doctor Easily manage and convert your Flight Simulator textures with Texture Doctor! Texture Doctor is an easy to use tool for inspecting Flight Simulator textures and converting them between various formats. It supports FS2004 and FSX. Features: • Lists textures installed in Flight Simulator with name, format and texture size. • You can list textures contained in one particular texture folder, several texture folders (e.g. All aircraft textures), or all textures installed in FS.

Converting FS Default Textures For Google SketchUp (GSU) Items needed to Convert Textures: You will need either Flight Simulator 9 (FS9) or Flight Simulator X (FSX. Texture Convertor 2 (TC2) is an application that can automatically convert figure textures from one format (or figure) to another. By using a plugin system, texture. Free Pansat Bin Files Downloads. Addon Converter X resolves many of these problems on the fly. FS2004 models with textures converted to the DDS format should now work correctly with DirectX 10. Astrology Learning Book In Bengali Pdf on this page.

• Sort the list by various criteria (e.g. By format to find all textures that are not in the DXT format).

• Shows you a preview of the currently selected texture in the list. • Converts any number of textures between various formats. The formats supported are: BMP, DXT1, DXT3, DXT5, DDS. For example, you can sort the list by the texture format, select all BMP textures and convert them into the DXT3 format with just a few mouse clicks. Texture Doctor is a must have for every serious flight simmer. Texture Doctor uses the ImageTool program found in the Flight Simulator SDK.

If you have FSX Deluxe edition, the SDK is already included and installed. If you are using FS2004 or FSX Standard edition, please and install the FS2004 Terrain SDK which contains ImageTool. Note that Texture Doctor does not support the DDS format when used with the FS2004 SDK. Why convert textures? There are many reasons to convert textures into a different format. If you have legacy textures in the BMP or R8 format, converting them into DXT1 or DXT3 can both improve the image quality (greatly reduces jitter) and performance (the compressed texture takes less graphics memory and is natively supported by nearly all graphics cards).

You may want to convert a texture back into the BMP format, edit it with your favorite graphics editor and convert it back into the original format. Different graphics cards have varying performance with different texture formats. You may achieve better performance by converting the textures to another format. With FSX, you may be able to achieve better performance by converting textures to the corresponding DDS formats.

In this case, remember not to share the converted textures with any FS2004 users, because they would no longer work with FS2004. Texture Doctor makes it very easy to convert textures, so you can simply experiment. Using the built-in restore function, you can always go back to the original textures if you don't like the results.

Note: Texture Doctor will not resolve texture problems experienced by some FS2004 aircraft models in FSX SP2/Acceleration. Our product should be used for that.

Hi all,As discussed in the previous thread, here's version 1.03. This fixes the problem going above a few hundred textures. There is no limit now (and no memory leak).

As pointed out in the readme, you must have the latest version of Martin Wrights MWGfxDLL.exe package as can always be downloaded with this link:If possible and if any of you have a few minutes, I'd like to get definitive feedback that this indeed has no memory leak on systems besides mine that I've tested on. If no feedback can be had, I'll release it to AVSIM tomorrow sometime. For now, you can download it here:FS Texture Converter v1.03 (499KB)Thanks and sorry about the delay. Hi Misho,As long as you don't select type 2 as the output format (DXT1 with Alpha - NVIDIA Method), there is no problem with the NVIDIA bug as their code won't be used (it'll use Martins code instead for all other methods). If you do select the type 2 NVIDIA method, I have retained the workaround in the tool to sort-of handle the problem in v1.03. While some textures may not be converted properly using type 2 NVIDIA method, the tool will create a list of those that were not and move the successful ones to a separate path. Those and only those that could not be converted with the method will be left in the original Base folder.

That way, you can convert only the unconverted ones in a separate step with a different method, such as type 1 (DXT1 with Alpha - FS2K2 Method). Why anyone would want to do this (beyond testing) I don't know, but the option is there if needed. Details on how this is handled are in the readme.Otherwise, the tool should be complete for what one might use ImageTool for in regards to PhotoReal scenery. Unless, that is, you or others have a problem or need a new feature and say its not:-).Take care. Martin's original DLL set only had the Nvidia code for DXT1, as provided in one of their SDKs, at the beginning. When the bug with their code became apparent (only shows itself with some alpha masks, not opaque-only textures), he kindly wrote replacement code. While Nvidia's code is faster, Martin's is of course stable:-).Since his DLLs retain the older method as well as the newer (for backwards compatibility), I also retain the option to use the Nvidia method in my tool.