I tested it with VirtualGL, and it produces the same frame rate as the Unix viewer on the same hardware.
On Mar 10, 2011, at 1:06 PM, Martin Koegler <mkoeg...@auto.tuwien.ac.at> wrote: > On Thu, Mar 10, 2011 at 04:23:10AM -0600, DRC wrote: >> Now, as far as the Windows refresh issue, I did some digging. For >> starters, I don't think the Windows TigerVNC viewer is doing the right >> thing by waiting to send a new FB update request until the WM_PAINT >> message is received. It should really be doing what the Unix viewer >> does, and what the TurboVNC viewers do, which is to send a new FB update >> request as soon as an FB update is received. I implemented that in >> r4351. Then, I applied Martin's previous suggestion for re-ordering the >> messages in r4352, and the combination of the two seems to have the >> Windows viewer performing just like the Unix viewer now. > > To get your expected frame rate on the screen, are you sure, that you > don't need to call UpdateWindow > (http://msdn.microsoft.com/en-us/library/dd145167(v=vs.85).aspx) > regulary to force to send a WM_PAINT message? > My workaround still allows update starvation. > > I don't have any such demaning application in my windows test setup, > so I can't tell you for sure. > > Regards, > Martin Kögler ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
