Keith Whitwell wrote: > Roland Scheidegger wrote: >> Currently, fog in vertex programs doesn't work when using >> per-vertex fog, since the fog factor computation is not done in the >> tnl pipeline. I think the most elegant solution to this problem >> would be to just move the (slightly changed) fog pipeline stage to >> after the various vertex prog extensions. Is it safe to move >> pipeline stages around? I think it should be as long as a stage >> doesn't need the output of another one. It seems to work (only >> tested with arb_vp), but I might miss some pitfalls... (obviously, >> hw drivers using their own pipelines would need to change the order >> too). > > Yes, that seems like it should be ok. The alternative is to append > the fog computation to the vertex program, but that's obviously more > complex. It wouldn't be that complex (just call compute_fog_blend_factors there), but would need to be done for all of NV_vp, ARB_vp and ARB_vs.
> This will interact badly with the programs generated by t_vs_build.c, > though. At the moment I don't think any of the drivers pass those > into the software tnl pipeline though. Ahhh. I just knew I forgot something... That said, I'm not sure passing the t_vp_build.c generated programs through the default tnl pipeline would work currently at all, since all pipeline stages decide if they get run by VertexProgram._Enabled, which is not set in that case - so all stages would run (before the arb_vertex_program stage though) anyway. Roland ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
