I have been following the chromium issue 422000, where v38 was reported as busting vsync. The Google engineer post made yesterday: [quote:1m21dlhp]We have landed a bunch of changes which fix things around this area but to fundamentally get this totally finished we need the following things fixed / finished;
* (done) Actually use the time from BeginFrame information rather than random "Now()" value.
* (in progress) Unified Begin Frame (make all renderers using the same single source and enable filtering)
* (in progress) Display Scheduler (provide better scheduling of frames)
* (unstarted) Back pressure API which means we cleanly drop to 30 fps (see discussion on scheduler dev mailing list).
* (unstarted) Get better sources of vsync information on individual platforms (see proposal about how to get a really good vsync value on Windows).
We also need to come up with better testing and metrics to prevent any regressions of this problem in the future. I've been discussing with the ChromeOS and input latency testing group on how we can reuse their work to also measure the actual real world experience people are getting.
In summary, "Some progress but still lots to do. We want to solve this properly and for good."
Which means we still have a long wait for a fully fixed version of NW to come out. NW v12.0 seems very good if not perfect, so this plugin is well timed and sounds excellent. MadSpy is using the delay in receiving a response from Scirra to add even more features, so I have mixed feelings about them taking back ownership! :p