well, unless i read qhue wrong (which is very possible, his reply wasnt worded very well) he wasnt referring to clip plane problems in a sense of saying "turn your clip plane down morons!".
what i got out of that was that some zones, even when you minimize your clip plane, and can see the fog, the engine is still rendering past your sight. if this is the case, whoever designed the zone needs beaten severely. though, it seems thats already in line for whoever did PoWater...
certain zones have pre-set max clip planes (think gfay, ponightmare, etc). maybe PoWater has a non existant value for this entry, and its interfering with clip plane adjustment, and no matter what you adjust, its not only rendering out to what the standard max is, but the actual entire zone on every refresh.
Not sure though, all speculation.
Quote:
|
Runs fine for me. Perhaps you need to upgrade that Pentium II and TNT2 card?
|
id bet $50 that this person has only seen PoWater through an emulator. and yah, i bet it did run fine for him. ive been in powater on the emulator before and it does run just as smooth as any other zone.
however, on the emulator they do NOT have the values set for zone specific clip planes (that i mentioned earlier) and i believe it is set to default every zone to 'standard' ie. max clip plane exists where the end of the clip plane bar can move to. this does make me think that there is some kind of erroneous value for that field in PoWater thats foricng the entire zone to render. If thats the case, its an easy as fix, and shouldve been noticed a long ass time ago, but hey! Beta testing, and even in house testing owns.