Re: Performer 2.5 query

New Message Reply Date view Thread view Subject view Author view

From: Jason Daly (jdaly++at++ist.ucf.edu)
Date: 01/24/2002 07:46:18


On Mon, 21 Jan 2002, Rob Body wrote:

> Hi Performer Friends,
>
> One thing that I have noticed is that two of the Openflight databases that I
> have used on either an O2 running Performer 2.2.0 with Openflight Loader
> 15.4fi or an ONYX RE2 using Performer 2.1.0 with Openflight Loader 15.4b
> don't look the same as the PC using Performer 2.5 with Openflight Loader
> 15.4i. Both of the databases appear darker using 2.5, one of the databases
> doesn't display some of the textures properly or if it does they are very
> dark and the other database which on the O2/ONYX displayed fine when I have
> floodlighting being done at night, does not have the floodlighting appear at
> all using Performer 2.5
>
> GameGen II or Creator was used to produce the Openflight models in both
> cases.
>
> Does anyone know why I have these differences in how the databases are
> displayed. I think it is to do with the version that the files are being
> saved as but I would like some one to confirm this before I go too far down
> the wrong track.

Hi, we had a similar problem. On the IRIX machines, everything looks correct,
but when we move to the PC some models are very dark and certain surfaces
appear with the wrong colors. We resolved it by bringing up each of the
offending models in one of the MultiGen packages (we use MultiGen II
primarily), and calculating the shading as Dynamic instead of Gouraud or
Dynamic Gouraud. We also saved each file as version 14.2 instead of 15.4.
This seems to fix any problems with rendering too darkly or with incorrect
colors.

Hope this helps.

--"J"

"I'm a castaway stranded in a desolate land,
 I can see the footprints in the virtual sand."
        --Neil Peart


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Jan 24 2002 - 07:45:22 PST

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