I must stop saying I've fixed things - as this problem still continues since
migrating to Win2000. :0(
Have run latest nvidia drivers 41.09, have reverted to 28.32 (having used
the 2832 Win9x version with WinMe equiv with no problems)...have run with
Directx8 through 9 - no difference - they all do it!!
I'm not using texture sharpening (where offered).
I am using AA and Mipmapping.
What causes this black square over scenery objects, a/craft nav lights
etc.... it isn't there when the sim starts, but can come on if I task switch
to another window, then go back to FS2002.
Hope someone can help as I'm (once again) beginning to think I've got to
return to WinME to get a decent sim session - and that surely is saying
something pretty desperate!!! :-(
Thanks in advance,
Graham.
> What causes this black square over scenery objects, a/craft nav lights
> etc.... it isn't there when the sim starts, but can come on if I task switch
> to another window, then go back to FS2002.
Try hitting Alt-Enter twice and see if they disappear. Works for me.
I had the same problem and I'm on Win2K.
But I noticed that it never occurs in window mode, even if maximized.
And as this is a requirement for flying on-line with Squackbox, it's
not a problem anymore.
Give it a try.
Manu
Try to set anisotropic Filtering at 4x under your display properties.
That should do the trix.
--
Martin
Do you ever wonder what life would be like if you'd had enough oxygen at birth?
Too many drivers installed, clean the system, the latest 4x.xx ones
seem to leave bits and pieces when you revert to previous ones. Once
you're back to the W2k defaults install the 30.82 and try them with
their default settings...
(I'm back and I hope mid-summer comes soon <g>)
---
All the Best
Katy P.
Hi,
Do you have any Win2k service pack installed???
I had problem like you have before SP2 and after SP3. SP2 worked fine
for me.
I still use SP2 and sometimes still have the thing you discribe, but
that only becuase I swaped too much between photoshop and fullscreen
FS2002(seems that FS2002 doens`t like that).
Bob
What do I have to do to "clean" the system under Win2000?
Each time I have reverted to a baseline of 41.09 - which was the original
drivers loaded when Win2000 was newly loaded - so *hopefully* I don't have
driver garbage left behind (but who knows for sure). When I changed drivers
I always used the add/remove, rebooted (and had to select VGA start option
from the F8 menu otherwise Win2000 would not restart completely).
Then I would reselect a different driver, and reboot.
I would be happy to check and clean, but not sure how to under Win2000 -
your help is sought once again :0)
Look forward to hearing from you.
Thanks,
Graham.
"Katy Pluta" <katy...@hotmail.com> wrote in message
news:p21p4vk4m0cejbnvq...@4ax.com...
I must say that I do not know for sure, the usual detonator destroyers
software and others I heard of work for W9x/ME... I would look on the
relevant forums on http://www.guru3d.com and ask there if there is a
tool or an easy way for W2k. Removing the drivers, using W2k built
ones and manually checking the hard drive files and registry for any
NVIDIA files and calls, to remove them is what I would do...
I have spent hrs on fs2002 tonight trying to get it to fail following my
most recent re-load of the drive image (puts it back to DirectX8.0a (as
supplied with the sim) and the 41.09s - no problems so far, despite intense
task switching etc. So I'm now wondering if I remembered the sequence of
events correctly. :(
I will leave it running when I go to bed and see what it looks like
tomorrow - well later on this morning actually!!! I have the sneakiest of
suspicions that DX9 *may* have be playing a part in this on the Win2000
platform - but cannot say for sure. DX9 was certainly good on Me and gave
better performance.
If the problem doesn't recur, I won't move to the 30.82 drivers (which I
have now downloaded) until the d/destroyer becomes available. So if the
problem persists, I will dual-boot to my Me partition and run fs2002 from
there.
Thanks once again - and hope you feel warmer soon :)
Regards,
Graham.
"Graham N" <grnicol@nospam> wrote in message news:3e4d...@news.simflight.com...
My Ansio thingy is set to "off" at the moment.
If the problem comes back I will try it and report back :0) Many Thanks for
your help on this - I'm just trying one thing at a time as I did so much
over the last few days , most at ungodly hours in the morning, whilst
muttering "just one last try".... :)
Graham.
"Martin.V." <mar...@nospamplakaten.dk> wrote in message
news:3e4dc40b$1...@news.simflight.com...
"Graham N" <grnicol@nospam> wrote in message news:3e4e...@news.simflight.com...
"The Guardian" <the_gu...@wanadoo.nl> wrote in message
news:3E4CB769...@wanadoo.nl...
I had the same problems when I first got my Ti4600. Simply turn down the
anistropic from 8x to 4x and you should be fine. If that doesn't work, try
playing around with the anti-aliasing slider as well.
Regards,
David Liu