安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
It's nice that the community has come up with these tweaks though, since as standard the PC version seems pretty much the same as the console versions just with the option for higher resolutions and frame rates for those with the hardware. And considering the game runs quite nicely on PC, it's good we've got these tweaks to enhance the visuals.
Hopefully we'll find a few more along the way. I'm kind of interested to know if we can alter the exhaust heat-haze effect, as in its current state it seems a bit blocky perhaps, and maybe it's too wide-spread as well. I've also noticed that it looks to always be centred, so for aircraft with widely spaced engines (like the F-14 and A-10) it's a bit strange, though I doubt that's the kind of thing that could be fixed with some configuration commands.
Look in the root of C:\
Have you tried the settings posted earlier in the thread? Ghosting is super minimal, I can't really even notice it. UE4 implementation of TAA is top notch. Try it if you haven't yet, before dismissing it entirely.
MSAA won't work at all, not with the deferred lighting path they've used in this game (as with most AAA games these days, not just UE4 specifically). SMAA you could probably inject pretty easily with ReShade, but careful with that because if they ever add anti-cheat it might get flagged.
https://i.imgur.com/IVJpy8z.png
So open the "Engine" file up (it'll probably open in Notepad or WordPad but either will do) and add those lines. Once you've done that it should look something like this, then save it and you should see the changes in game:
[Core.System]
Paths=../../../Engine/Content
Paths=%GAMEDIR%Content
Paths=../../../Engine/Plugins/Wwise/Content
Paths=../../../Engine/Plugins/2D/Paper2D/Content
Paths=../../../Engine/Plugins/Media/MediaCompositing/Content
Paths=../../../Engine/Plugins/Runtime/CriWare/CriWare/Content
Paths=../../../Engine/Plugins/TrueSkyPlugin/Content
[/script/engine.renderersettings]
r.ViewDistanceScale=5
r.SkeletalMeshLODBias=-2
r.StaticMeshLODDistanceScale=0.25
r.Streaming.HLODStrategy=2
As for SMAA, you could try ReShade, but unless it's been updated in the last half a week it probably won't work, since I tried it and it had no effect at the time.
The second thing is back to draw distances. Whilst testing the TAA exhaust effect with afterburners on (on Mission 02 free flight again) I noticed that actually there is a bit more pop-in at long distances with r.ViewDistanceScale=5 than I had originally observed. Perhaps the greater speed makes this more obvious. I even upped the value to 6 and it was still there a bit, just going up the side and onto the tops of distant hills. I doubt it would be noticeable in normal gameplay, but still, it's worth noting for those who demand the best quality.
Out of curiosity I tried sg.ViewDistanceQuality=4 in the GameUserSettings.ini instead, and it seems as if this eliminates that pop-in entirely, though I'd want to do a video comparison to be totally sure. I also ran a timed benchmark on both r.ViewDistanceScale=6 and sg.ViewDistanceQuality=4, and the latter came out with an average and low of just 1 FPS less than the former. So if my observation is correct that sg.ViewDistanceQuality=4 removes pop-in entirely, then I would recommend that it is used rather than r.ViewDistanceScale values of 6 and above.