Skip to content

[dxvk] Do not engage CPU frame rate limiter if present timing is used #7378

[dxvk] Do not engage CPU frame rate limiter if present timing is used

[dxvk] Do not engage CPU frame rate limiter if present timing is used #7378

Triggered via push May 19, 2026 18:32
Status Success
Total duration 14m 18s
Artifacts 1
build-set-windows
14m 13s
build-set-windows
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
build-set-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-set-windows
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
dxvk-present-timing-v2-4a3783f477ebd6868f31813fa5bf408326132283-msvc-output
20 MB
sha256:015c97f1df445b072fedcb4a7ae029521f0e230443efaa598c02de1f5ccc00ae