Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
The more important way; By default G-Sync can cap your framerate to your screen refresh rate. So if you run a lightweight test that can run faster than, say, 144fps, and you have 144hz and G-Sync on, your score will be lower than it could be since framerate never goes over 144. Yes, you can force G-Sync to operate so there is no cap and so framerate can go over screen refresh rate, but last I checked that is not true by default. When playing games, there is no real benefit for going above screen refresh rate (unless you want to eke out every single millisecond of responsiveness out of a game, think "pro CS:GO players") so it makes sense for gaming, but throws off the result for a benchmark that bases the score on the framerate of the test.
The less important but subtle way: Exact same system, exact same hardware, running a test that does not go anywhere near the refresh rate of the screen (say, Time Spy running around 30-45fps) still exhibits *slight* performance penalty for enabling G-Sync. Our theory is that this is due to additional graphics driver overhead. The effect is small - at most a few percent - but can be noticed especially on DX11 tests. You can usually ignore this if you are just looking for a ballpark figure on the performance, but in all honesty, if you want to make an accurate comparison against another system that does not have G-Sync present, the recommendation is to temporarily disable it when benchmarking to take this small extra overhead out of the equation.
https://www.3dmark.com/spy/2926563
vs
https://www.3dmark.com/spy/2926672