On Fri, 17 Oct 2003 15:54:39 -0700 (PDT) Mike Mestnik <[EMAIL PROTECTED]> wrote:
> > --- Felix K_hling <[EMAIL PROTECTED]> wrote: > > On Fri, 17 Oct 2003 12:10:05 -0700 (PDT) > > Alex Deucher <[EMAIL PROTECTED]> wrote: > > > > > you need to change the DRI config settings: > > > > > > http://dri.sourceforge.net/cgi-bin/moin.cgi/ConfigurationInfrastructure > > > > > > perhaps we shouldn't make sync to refresh the default. > > > > IIRC there was a similar discussion after the texmem-0-0-1 merge. I was > > hoping that a well defined configuration system would finally allow us > > to make the default comply with the spec. The default setting should not > > affect the frame rate if it was below the vertical refresh rate without > > vsyncing. Only for benchmarks it is useful to disable vsync. For > > everyday work/game play you never need more than 75 or 80 Hz, do you? > > > > > > > > Alex > > > > Regards, > > Felix > > > There may be allot I don't know about OpenGL, but I do know video games. In games > you want to > hear/see the latesed info about game state that exists, this adds(subtracts) to your > hand eye > cordination(Things like network anticipation are great). You also want what you > hear to be > synched with what you see. It's important for these 2 reasons that OpenGL allways > present the user > with the most current data. I am familiar with the latency problem. However, let me explain what exactly the default setting (swap interval 1) does. It means that the time between two buffer swaps is at least one vertical refresh cycle. If rendering the frame took longer than that one refresh cycle then the buffer swap occurs immediately. This means no extra latency is introduced. Furthermore it means, if your game/application has a peak frame rate below the vertical refresh rate then this setting doesn't change anything. If your game had a peak frame rate above the vertical refresh rate then it will limit the frame rate to the vertical refresh rate introducing a maximum latency of 1/refresh rate (if rendering the frame took no time at all). In most cases I have seen games had a frame rate between 30 and 60 fps. If it was higher than that I would increase the resolution/geometrical detail/texture detail/whatever in order to improve the total visual quality. > > The way things should work is... > The card tells the game when the NEXT vsync should happen, deduced by Current + > RefreshRate. Then > the game should predict what things will look like and send that to the card to be > rendered. > > However things AFAICG work... > The game renderes as many FPS as the card can and the card draws the last one to the > sceen. Maby > not the best way but the most feasable with what(drivers) we have today. > > Thus synch to vblank ?may? make frames appere 1/RefreshRate of a seconds too late. > Thought for > most gamers this may be fine, I think my eyes are faster. <flamebait irony="on"> So you admit that the default setting is ok for most gamers? Then it is the correct choice for a default setting that makes most people happy. The configuration file is there to serve the needs of extraordinary people like you. ;o) </flaimbait> Cheers, Felix ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything [EMAIL PROTECTED] \___/ \___/ U at the same time. ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
