If it were "hard" errors.. i.e. cfg syntax,
or physically non-present textures,
it would manifest itself on all computers.
Sorry but that's an inaccurate supposition.
If it were "hard" errors.. i.e. cfg syntax,
or physically non-present textures,
it would manifest itself on all computers.
[/url]
Hi FolksIf it were "hard" errors.. i.e. cfg syntax,
or physically non-present textures,
it would manifest itself on all computers.

Boikat -
Forgot to explicitly mention -
Issue may also occur if a texture is of a non-DXT format.
Although the file extension may be .dds,
the file's content itself might not be.
To identify the filename of missing textures, (simobject or scenery),
add the following lines to your fsx.CFG into the section titled [SCENERY].
Code:[SCENERY]
// To show alerts or areas, set to = 1
// To hide alerts or areas, set to = 0
// Alert for missing textures
ShowMissingTextureAlert=1
), and they were all there, so I replaced them from the 737-800 main texture folder, and it's happy now. 












Regarding the original post (animated parts askew);
it is most definately a hardware problem,
and almost always a graphics card issue.
If your hardware (and drivers) are up to the task, they render properly.
[/url]
Please explain why all these are HARDWARE problems.
and how your HARDWARE has suddenly healed itself ?





Hi FolksIf it were "hard" errors.. i.e. cfg syntax,
or physically non-present textures,
it would manifest itself on all computers.




Return to Flight Simulator X (FSX) and Steam
Users browsing this forum: No registered users and 421 guests