Re: Problem with model flickering in Performer 2.0

New Message Reply Date view Thread view Subject view Author view

Mario Veraart (rioj7++at++fel.tno.nl)
Mon, 7 Oct 1996 13:44:05 +0200 (MET DST)


Hello,

Sorry for the late reply because I'm a bit behind my email.

Just as already pointed out it could be fixed with a tweak of the
far and near plane values. Moving near plane away has a much better
effect than the far plane because the value far/near must be as smal as
possible.
If that still doesn't do the trick maybe a few lines of code might do.
The were mentioned on this list some time ago. They are

    pfdMakeShared((pfNode*)scene);
    /* compute an optimum scene geostate */
    pfdMakeSharedScene(scene);
    /* optimize pfLayer nodes via "DISPLACE POLYGON" */
    pfdCombineLayers((pfNode *)scene);

call them after loading the scene.

Mario
>
> I recently ported a virtual solar system modeler from Performer 1.2 to 2.0.
> I'm now having problems with flickering in many of my models. By flickering,
> I mean models which have texture maps and models which don't have texture maps
> have periodic changes of color. For example, Africa and other parts of the
> earth flicker between the approriate land colors and blue (the ocean). That
> model uses a texture map. With another model, a satellite, the colors flicker
> between what they're supposed to be and other colors. The satellite doesn't
> use texture maps. I've also checked for coplanar polygons, averaged vertices,
> etc. Coryphaeus has attempted to help me, but the problem seems to be
> Performer related, not a model problem. This conclusion is substantiated by
> the fact that I didn't have these problems in Performer 1.2. The problem is
> magnified as the viewing distance to the model is increased, i.e. up close the
> flickering isn't too bad or is nonexistent but it gets worse as you move away
> from the model. Some of the models use LOD and some don't. This doesn't seem
> to have any impact on the problem.
>
> Input from anyone experiencing this type of problem or from anyone who knows of
> a solution would be greatly appreciated. Does this sound like a Z-Buffer
> problem?
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:43 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.