From: O.Sezer <se...@gm...> - 2005-04-30 16:39:38
|
Hi Hiroshi, >>> Were the triangles correct with -DGLIDE_TRI_CULLING=1 with >>> previous libraries and does this happen with the debug or >>> release build? Could you post some screen shots again? >> >> >> Snapshot from 04-23/24 used to do it correctly both with debug >> and release builds. This time I used the release build (in fact >> I forgot the DEBUG=1) and this happened. > > > Hmm, could you check out gdraw.c ddgump.c gaa.c guclip.c before > 04-25 and see if it does it correctly? You will need to remove > __declspec(naked) from grDrawTriangle() in gdraw.c to build. I re-tested the 2005-04-25 snapshot: With DEBUG=1, it is fine, without it, the clipping errors (shots uploaded to http://uhexen2.sourceforge.net/tmp1/) Will go back to -04-23 to see if the release build was really fine. (Give me some more time for that ;) >>>> The optimized version seem to build, but I couldn't get any >>>> picture with it. Didn't try hard and tried it only once, >>>> though. >>> >>> >>> >>> The Linux triangle dispatch code is probably broken for the >>> optimized version. Could you try replacing the lines between >>> #if defined( __linux__ ) #endif of grDrawTriangle() in gdraw.c >>> with the following; >>> GR_BEGIN_NOFIFOCHECK("grDrawTriangle",92); >>> GR_CHECK_F(myName, !a || !b || !c, "NULL pointer passed"); >>> TRISETUP(a, b, c); >>> GR_END(); Actually, the optimized build is broken for release builds: xtexdl.asm:231: error: symbol `checkPtr' undefined texdl.asm:283: error: symbol `checkPtr' undefined texdl.asm:333: error: phase error detected at end of assembly. Therefore I can't build what you suggested (GR_CHECK_F requires debug, as I can see.) Will post more later with the clipping stuff. Ozkan PS: The V2 card I use is a 12Mb Gainward board, but its FCC-ID isn't listed on the fcc site (ICUVGA-GW803N). Funny that my 8Mb Creative card gives at least 2-3 fps more than this one. Probably a slower ram? |