Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
Clarify you don't have system settings interferring with capture, disable local AC, ideally test same setup on linux to see if it works natively there, if it does - it's your windows installation.
-
Use a capture card, and get used to alt-tab to refresh out of black captured insertion frame. You also need to enforce same resolution + refresh rate for game and os, to avoid unnecessary "black captures".
The second best method is something akin to network capture with rtmp, or any newer protocol doing the same thing - but it has higher cpu overhead. Window capture in general isn't very good because some games just don't like it, either due to the game or their AC software, driver related and so on.
As far as nvidia driver goes, you need to find one stable version, and stick to it. Which means you don't just update to newest version just because there's a newer version.
Im not update to with standards today today, but i did manage to get a 1000 fps timedemo capture with ql, which you can only do with network capture - think i used game capture in obs. But even just a few years ago, the stability of this was constantly unstable to stable from one version to the next of OBS.
None of the settings ingame should be any conflict to your recording - game's too old.
I should probably get around to set it up again, but i dont think window capture is any good, it's not universally designed and requires input. I prefer lazy capture setups.
You can go the route of making a setup for each game and so on, but imo that takes too much time that could be better spent elsewhere.
Upgrading to a 12 core CPU seemed to make any performance issues while recording go away but the lighting effects were either too bright or too dark.
Every video I recorded I had to add lighting and color to.
QUAKE LIVE uses open_GL and did not came to use Vulcan rendering, which QUAKE III ARENA did come around to use and support. This makes it somewhat more difficult to capture the open_GL directly, especially with over brights lightning commands, the game goes dark and lights up uncontrolled. In quake iii arena the command r_FBO 1 was brought onto it, it allows the rendering to be recorded directly, preserving coloring etc. However Quake Live doesn't support Vulcan, and r_FBO 1 doesn't exist or works there but I believe there is a command that will help:
r_floatingPointFBOs "1" takes win32 into account and continues the floating of system32
I don't have OBS currently not installed, cant test it, let us know if it worked