v1.5.1

Pre-release. Two fixes for reports on v1.5.0, verified on a GeForce RTX 5090; both editions carry them. It becomes the stable release once it has proven itself in use; the stable release stays v1.5.0 until then.
预发布版：v1.5.0 的两个问题修复，已在 RTX 5090 上验证；确认无问题后再转为正式版，在此之前正式版仍是 v1.5.0。

Which file to download / 下载哪个文件

Graphics card / 显卡	File / 文件
NVIDIA GeForce RTX 20 / 30 / 40 / 50	VRChatDLSS5Cam-win64.zip
AMD Radeon RX 7000 / 9000	VRChatDLSS5Cam-win64-amd.zip (Radeon edition / Radeon 版)

The Radeon edition fetches DLSS-NR-on-AMD's installer for you at the first start (nothing of the port is bundled; it is downloaded from its own release page https://github.com/danielblnc/DLSS-NR-on-AMD/releases). What to expect on Radeon is listed in the README under AMD Radeon cards.
Radeon 版会在首次启动时为你下载 DLSS-NR-on-AMD 的安装器（不捆绑该项目的任何文件，只从其自己的发布页下载）；Radeon 上的预期表现见 README 的 AMD Radeon 显卡 一节。

Fixed in v1.5.1

• A video exported without sound. An iPhone MOV carries two audio tracks: Apple's spatial audio (four channels, which Windows cannot decode) listed first, and the stereo AAC track second. The program took the first track only, could not decode it, and wrote the video silent (log.txt: "the audio stream cannot be decoded"). It now uses the first audio track that decodes; log.txt lists the tracks of the file and the one taken. Verified with that MOV on the RTX 5090: the export carries the AAC track at the same level as the source.
• The graphics device was lost on a live stream. On an RTX 4080 SUPER, a 1080p live stream upscaled to 4K on a card fully loaded for 12.7 minutes while VRChat rendered on the same card ended in a driver reset (log.txt: "Device removed", DXGI_ERROR_DEVICE_HUNG) and a modal "graphics device was lost" message. The driver resets every program on the card at that moment; nothing in this program precedes it. The program now starts again by itself once the driver is back, tells you so in a notice, and keeps the log of the lost session as log-device-loss.txt next to log.txt. If the device is lost again within a minute of such a restart, or in a scripted run (--process, --headless, --exit-after), the message is shown and the program exits with code 2 as before. If it repeats on your card, lower the load: a processing rate cap, a lower Neural pass resolution or a maximum-resolution cap, the neural upscaling to the custom resolution off, or a frame rate limit in VRChat; a newer graphics driver is worth a try (README, Troubleshooting).
• Video memory in the log. The Perf: line every 15 s and the device-removed entry carry the video memory this process uses and the budget the system grants it, so a loss under load can be read from the log.
• README (four languages): troubleshooting entries for the lost graphics device and for the silent export. COMMAND_LINE.md: exit code 2 after a device loss and the automatic restart (--after-device-loss is added to the arguments of the restarted instance).

简体中文

• 导出的视频没有声音。 iPhone 的 MOV 有两条音轨：排在前面的是 Apple 空间音频（四声道，Windows 无法解码），其后才是立体声 AAC。程序以前只取第一条，解码失败后把视频写成了无声（log.txt："the audio stream cannot be decoded"）。现在改为使用第一条能解码的音轨，log.txt 会列出文件的各条音轨及所采用的那条。已在 RTX 5090 上用该 MOV 验证：导出带有 AAC 音轨，音量与源文件一致。
• 实时串流时图形设备丢失。 一台 RTX 4080 SUPER 上，1080p 实时串流放大到 4K、显卡连续满载 12.7 分钟且 VRChat 在同一张卡上渲染，最终驱动重置（log.txt："Device removed"，DXGI_ERROR_DEVICE_HUNG），程序弹出"图形设备已丢失"后退出。驱动重置时显卡上的所有程序都会受影响，程序日志里在此之前没有任何异常。现在程序会在驱动恢复后自动重新启动并弹出提示，丢失前那次会话的日志保留为 log.txt 旁边的 log-device-loss.txt。若重启后一分钟内再次丢失，或是脚本化运行（--process、--headless、--exit-after），则仍显示提示并以退出码 2 结束。若在你的显卡上反复出现，请降低负载：设置处理帧率上限、调低神经渲染分辨率或限制最大分辨率、关闭神经上采样到自定义分辨率，或在 VRChat 里限制帧率；也值得试试更新显卡驱动（见 README 常见问题）。
• 日志中的显存占用。 每 15 秒一行的 Perf: 和设备丢失记录现在带有本进程占用的显存和系统分配的预算，方便从日志判断满载时的情况。
• README（四种语言）： 新增"图形设备已丢失"和"导出的视频没有声音"两条常见问题。COMMAND_LINE.md：设备丢失后的退出码 2 和自动重启（重启的实例参数里会多出 --after-device-loss）。