#88 Lighting code is messed up for MGA on Heretic II...

critical
open
Frank C. Earl
mga (37)
9
2000-12-11
2000-12-11
Frank C. Earl
No

See Heretic II for examples.

Fireball effect should just highlight certain polys as it flies by. On the G200, it paints blacked out portions, and on the G400, it's the same in indirect and produces spectacular technicolor effects in direct.

There are other notable examples (incl. some occasional lighing screw-ups on the screen- poly's having light on them when they should really be in shadow, etc.) within this app.

Discussion

  • Frank C. Earl
    Frank C. Earl
    2000-12-11

    • priority: 5 --> 9
    • assigned_to: nobody --> svartalf
     
  • Frank C. Earl
    Frank C. Earl
    2001-01-23

    Conducted an interesting experiment. I set nohw = 1 and ran the Heretic II demo. After dealing with some serious pain with waiting for the software rendering to get going, the screen's texture rendering and shading was all messed up. Software mode does NOT seem to be working 100% correct for the screens- Corvus is rendered correctly and anything where the light level is way up there is rendered correctly. Anything shaded at lower light levels is toast to varying degrees and the shading's definitely being interpreted wrong. I'll be testing this with raw Mesa if Heretic will let me shortly to see if it's Mesa 3.2.1 that's doing this or if it's our infrastructure.

     
  • Frank C. Earl
    Frank C. Earl
    2001-01-23

    Mesa rendered it beautifully (well, as beautifully as non-anti-aliased/non-mip-mapped rendering can be... :-)

    It's my understanding that "nohw=1" should be equivalent to running pure Mesa except that it's being pushed through the GLX pathway instead of directly to a software renderer. It's NOT doing that. My suspicion is that there's some thing seriously amiss with the GLX pathway or our "version" of the software server (from which everything must pass partially through to provide fallbacks for things...).