Hi all!
I am not sure if this message is correctly posted in this particular ng.
However, as Moray3.3 now supports OpenGL, and as I suppose that many Moray
users also use Leveller, this might be of interest here.
The problem is this:
The 3D view of Leveller always worked fine until I used it on a new PC with
a NVidia GeForce2 video card. This now shows ugly jaggies whenever I use a
visible water level .
I discussed the problem with Ray Gardener, the maker of Leveller, and he
told me it "looks like a classic case of low OpenGL Z-buffer precision".
After some extra trials, he came with an intriguing answer where the video
card might be involved:
Quote:
"Hmm... the nVidia card is interesting. My system where I work at EA has an
nVidia GeForce and it exhibits some unusual intermittent problems with
Leveller. I don't know if it's the video card, but the problems don't occur
on other systems, and they're also rendering related. While flying, the
sampling rate can suddenly change to 64 x 64. I suspect the render settings
are getting corrupted, and in your case it's the backplace distance instead
of the sampling rate (same root problem, but different symptoms)."

Does anyone have the same experiences?
Does anyone have a bright idea about this?
Ray Gardener and I would be extremely interested indeed!

Sincere excuses for the somewhat lengthy mail, but difficult to shorten...

Thanks!

Thomas

Post a reply to this message

On Sat, 24 Feb 2001 09:25:53 +0100 Thomas de Groot wrote:

>The 3D view of Leveller always worked fine until I used it on a new PC with
>a NVidia GeForce2 video card. This now shows ugly jaggies whenever I use a
>visible water level .

  Uh,oh. A friend of mine just ordered the optional 64mb NVidia GeForce2
card for his brand new Athlon box. If there is a problem with the drivers I
hope a fix will be forthcoming.

-- 
Alan - ako### [at] povrayorg - a k o n g <at> p o v r a y <dot> o r g
http://www.povray.org - Home of the Persistence of Vision Ray Tracer

Post a reply to this message

the problem may have to do with the drivers supplied by your card
maker.  sometimes, card-specific drivers aren't as good as nvidia's. 
that's one reason why some card makers win awards and good reviews while
others that use the same chipset don't.  all geforce cards aren't
created equal even though the chips are.  i'd look into drivers if i
were you.  see if your card maker has a new one and also grab nvidia's
reference driver.  try out one and then the other and see which works
best for you.

Thomas de Groot wrote:
> 
> Hi all!
> I am not sure if this message is correctly posted in this particular ng.
> However, as Moray3.3 now supports OpenGL, and as I suppose that many Moray
> users also use Leveller, this might be of interest here.
> The problem is this:
> The 3D view of Leveller always worked fine until I used it on a new PC with
> a NVidia GeForce2 video card. This now shows ugly jaggies whenever I use a
> visible water level .
> I discussed the problem with Ray Gardener, the maker of Leveller, and he
> told me it "looks like a classic case of low OpenGL Z-buffer precision".
> After some extra trials, he came with an intriguing answer where the video
> card might be involved:
> Quote:
> "Hmm... the nVidia card is interesting. My system where I work at EA has an
> nVidia GeForce and it exhibits some unusual intermittent problems with
> Leveller. I don't know if it's the video card, but the problems don't occur
> on other systems, and they're also rendering related. While flying, the
> sampling rate can suddenly change to 64 x 64. I suspect the render settings
> are getting corrupted, and in your case it's the backplace distance instead
> of the sampling rate (same root problem, but different symptoms)."
> 
> Does anyone have the same experiences?
> Does anyone have a bright idea about this?
> Ray Gardener and I would be extremely interested indeed!
> 
> Sincere excuses for the somewhat lengthy mail, but difficult to shorten...
> 
> Thanks!
> 
> Thomas

Post a reply to this message

Thanks Alan and Ryan!
I think there is a serious possibility there indeed. I shall try
something... Compaq is probably the card maker (they don't refer to anybody
else, so...) and I'll visit nvidia's site.
Thanks for the good thinking!
Thomas

"Ryan Constantine" <rcc### [at] ucdavisedu> schreef in bericht
news:3A9A8C34.35E2279C@ucdavis.edu...
> the problem may have to do with the drivers supplied by your card
> maker.  sometimes, card-specific drivers aren't as good as nvidia's.
> that's one reason why some card makers win awards and good reviews while
> others that use the same chipset don't.  all geforce cards aren't
> created equal even though the chips are.  i'd look into drivers if i
> were you.  see if your card maker has a new one and also grab nvidia's
> reference driver.  try out one and then the other and see which works
> best for you.
>

Post a reply to this message

I had a similar problem with Terragen, after installing a newer version
of NVidia drivers.
    My problem has been solved after I changed the color depth.

"Thomas de Groot" <t.d### [at] internlnet> wrote in message
news:3a9f537a@news.povray.org...
> Thanks Alan and Ryan!
> I think there is a serious possibility there indeed. I shall try
> something... Compaq is probably the card maker (they don't refer to
anybody
> else, so...) and I'll visit nvidia's site.
> Thanks for the good thinking!
> Thomas

Post a reply to this message

Hi All!
Well, I solved the problem at last by installing the latest adapter driver
that I got from the nvidia site. It got me almost a heart attack ;-} as in
first instance I thought I had lost the adapter. But reinstalling the update
turned everything OK.
So it seems that for each user there is a different approach....!?

The ways of PC's are strange and full of surprises....

Thomas


"SWIFT ETEBA" <swi### [at] etebagr> schreef in bericht
news:3a9fa82d@news.povray.org...
>     I had a similar problem with Terragen, after installing a newer
version
> of NVidia drivers.
>     My problem has been solved after I changed the color depth.
>

Post a reply to this message