Advertisement

reflections

Started by November 22, 2002 10:08 AM
83 comments, last by Crispy 22 years, 2 months ago
Okay, I feel a little reluctant to start a new thread because of this, but regarding the reflections, I did some browsing around in my prog using the good old TNT2 and this is what I came across:

A close-up of the water surface:


A panoramic view of the world:


Yet another panoramic view:


The question is - what''s the difference between screenshots 2 and 3? Took me a moment to realize, but the difference is that in screenshot 3 the FOV completely encapsulates the water surface while in screenshot 2 a teeny weeny little corner is left outside of the screen. This effect is true no matter from what angle I''m looking at the water or how much of it is inside/outside of the screen. Does anybody have a clue what might be causing this?

Crispy
"Literally, it means that Bob is everything you can think of, but not dead; i.e., Bob is a purple-spotted, yellow-striped bumblebee/dragon/pterodactyl hybrid with a voracious addiction to Twix candy bars, but not dead."- kSquared
quote:
Does anybody have a clue what might be causing this?

First thought : driver bug. (99.99% chances)
Second thought : very special case. (0.01% chances)

If you can run your program on another computer (in fact, another graphics card) you''ll quickly see if it''s a driver issue.
Advertisement
Tried it with several drivers on the TNT (inc. the latest); and it works just fine on a GF2, so I personally don''t see it as a driver issue... IMHO it''s either the GPU itself or there''s still something missing in the code... Either way, I''ve no clue as to what it might be...

Crispy
"Literally, it means that Bob is everything you can think of, but not dead; i.e., Bob is a purple-spotted, yellow-striped bumblebee/dragon/pterodactyl hybrid with a voracious addiction to Twix candy bars, but not dead."- kSquared
You may have made an assumption somewhere -> if you didnt explicitly define something you may face an issue where the default setting in a later version may be different from an earlier version -> im talking about OGL if you didnt catch my drift but a spoof like this is not limited to OGL.
Checking with several versions of a driver for the same card does not necessarily help, because even the latest driver release is not meant to be 100% bug-free.

You could contact developers relations at nvidia.com and report the bug. I think there''s people that will have a more convincing answer

This topic is closed to new replies.

Advertisement