Page 1 of 1

Arty-farty-facts!

PostPosted: Tue Dec 16, 2008 6:35 am
by Fozzer
Hello Chums...

FS 2004... :-*...!

Win XP Pro SP2

A rather annoying problem I have, with these "artefacts" constantly appearing in my clouds as I fly, for months/years now!

The flights starts of normally and the artefacts appear over time and can only be cleared by "Refreshing" the screen...(IE: calling up the FS Navigator screen, then returning back again to the flight).

It always occurs with Default FS 2004 Custom Weather Clouds, or Real Weather Clouds.
No problem with "Clear Skies", obviously!

I have had this problem with my previous Card; AGP nVidia 6600 128 MB...
...and now with my present Card; AGP nVidia 7800GS 256 MB.

No Over-clocking involved anywhere, and no problems with overheating, loads of well lubricated fans, no dust, biscuit crumbs, Spiders, Mouse Poo, everything running cool, and no obstructions to air flow.... :)...!

Specs:

Desktop (Table-top) Computer Case...(Not a Tower!), so all the cards are plugged vertically for better airflow over all of them!

Win XP Pro SP2
AMD Socket A, Athlon Thoroughbred, 2600+ (2.1 GHz).
Winfast AGP nVidia 7800GS 256 MB.
750Watt PSU.

I can cope with it, but it is rather annoying....
...by the way is there a key-press in FS 2004 which will automatically "Refresh" the screen whilst flying?

...any ideas, ring a bell, Chums?

Image

Image

Image

The clouds illustrated in the above pics are "Oscar Clouds", but the same fault occurs with the FS 2004 Default Clouds!

F...on Cloud #9 in between times... ;D...!

PS...Pics: In my lovely Cessna 150_V2 Aerobat... :-*...!

P.P.S. The same fault often appears in the Prop animation, and is cured by "refreshing" the screen!

Re: Arty-farty-facts!

PostPosted: Tue Dec 16, 2008 8:07 am
by C
Paul, I've no idea, but it appears some hoody's nicked your yoke! :)

Re: Arty-farty-facts!

PostPosted: Tue Dec 16, 2008 8:15 am
by Fozzer
Paul, I've no idea, but it appears some hoody's nicked your yoke! :)


...LOL... ;D...!

...another one of those annoying "Teenagers" who persist in giving me so much grief... >:(...!

LOL... ;D...!

F.....it's no Yoke Joke!!.. :(... ;D...!

Re: Arty-farty-facts!

PostPosted: Tue Dec 16, 2008 9:23 am
by Wii
Does this happen only in cumulus clouds? If so it sounds like your cumulus01.bmp or cumulus02.bmp is corrupt and might try a different cloud and then try oscar clouds again...or maybe try a lower resolution of oscar clouds. 512x512 is acceptable. I run the 128x128 clouds and they look just fine without touching my frames. :)

( ;D Yoke...joke.... ;D ;D)

Re: Arty-farty-facts!

PostPosted: Tue Dec 16, 2008 2:23 pm
by Fozzer
Does this happen only in cumulus clouds? If so it sounds like your cumulus01.bmp or cumulus02.bmp is corrupt and might try a different cloud and then try oscar clouds again...or maybe try a lower resolution of oscar clouds. 512x512 is acceptable. I run the 128x128 clouds and they look just fine without touching my frames. :)

( ;D Yoke...joke.... ;D ;D)


Nah, Wii...

Its a funny old do...
I use a wide collection of Default Cloud types in various densities, and the same anomaly occurs with all the different types... :'(...!

I've even recently re-installed a new copy of my FS 2004 on a new Hard Drive, (together with my Win XP Pro SP2 Operating System), and I still experience the same problem....
...very strange...
Once the artefacts appear on the screen, they can only be removed with a complete refresh of the whole scene, just spinning the view round will not clear them!
Once a refresh is done, they will appear again, some time later.
Screen Artefacts are normally associated with Graphics Card overheating/over-clocking problems, but not so in my case.

Computer cooling is more than adequate, and the ambient temperature is normally quite low...(Winter at the mo'... :(...)...!

F....its a (Arte) Fact!... ;)... ;D...!

P.S....It may have nothing to do with the problem, but for years, every time I close the FS 2004 Sim down it always ends with the error report; "Weather.dll"...and then restarts the Sim again..!
Browsed the 'Net for this Microsoft error report, and its quite common, generally with no known cures!