安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
Just so you know ... this fix wasn't created in a few days :) The original problem was identified and I wrote my tweak guide in about a week from launch, but it took over a month to develop it into the software you see now.
I suppose you could call me a "random stranger". But really, it takes someone with at least some familiarity with rendering to spot this bottleneck and fix it. By the same token, there should have been half a dozen people just as qualified as myself on staff that could have done the same thing, so I'm perpetually baffled by how this whole thing ever happened :P
Great to hear. Windows 10 is taking most of the spotlight these days though, for many people it can do what my tweaks do slightly more effectively. If you combine both of them together, that might make the game even more playable.
Nevertheless, it does fix some things. Enough to make the software something you'd recognize as a game on many systems :P
Here's the most recent.
http://i.imgur.com/LtsB3oi.jpg
Guess I'm waiting for the real patch, now. :(
He created the BMT tool himself and due to the community coming into this thread to post many results to figure out which ini tweaks were best, he was able to make this program that can do the ini tweaks and nvidia driver tweaks. One of the beginning issues when first did ini file tweaks was that because the files were timestamped the same the game would break the tweaks and revert them back.
So in the end he made the tool to synchronize all 3 of the files with same timestamp so that the game would think it was done ingame. If it wasn't for the entire community coming in here and stating their results we probably wouldn't have gotten as far with the tweaks created. It was a huge combined effort. Kaldaein has some major background in this area of expertise so its amazing that he took some time to create this tool for everyone to use :).
Those Unreal error messages are beginning to annoy the living hell out of me. Where it would usually say a function name in those DLLs, it just gives an address and "Filename not found". I really wish I could help you diagnose this, but it's not giving enough information.
That said, I managed to hit Apex and PhysX errors that I'd never seen before a few days ago when I was messing with the different driver versions available on Windows 10. You appear to be hitting the very same issue I was.
I don't remember how I resolved it, sadly. It was a combination of fiddling with my overclocking software, re-installing 353.63 and tuning PhysX memory and level with the tool. Neither one of those things worked individually, but in some combination they fixed it. When this was happening to me, I noticed my GPU was being underclocked - its nominal clock is 1.2 GHz, ordinarily it gets bumped up to 1.4 GHz during gameplay, but it was down at 540 MHz framerate was in the gutters and after about 5 minutes PhysX stuff was crashing.
Can you post a screenshot of the tool window with all of your used settings? Including driver tweaks on the side.
In the tool check mark hardware disabled Physx. That way it will be disabled and won't touch your Physx Card. By default the game has that hardware physx support disabled. Though I wouldn't even touch Gamework options on my end at all. I realized its the cause of many quick drops in my game performance.
Also setting Physx to low with gamework options turned on will be a bad combo. Its supposed to be on high with any of gameworks options turned on. If they are off then put physx to low. :) Hopefully this advice helps.
How you know they are resetting? Are the blue borders showing around your options. Also make sure your files aren't set to read-only. On side note once you use the tool do not touch ingame settings video options. It will reset everything back. I have seen it happen just by clicking on video options and loading it.
That's no longer an issue. The software strips the read-only flag before writing and applies it again after writing is finished now. It sort of works around any read-only files it encounters.
Only settings in the XML file (like resolution, GameWorks settings, etc.) can be modified by the game. The INI and all specialized performance tweaks are read-only.
Can you open the debug utilities menu and paste a screenshot of it? (See Appendix A). I'm particularly interested in seeing the timestamps for the Backup and Restore buttons.
Oh didn't realize that you fixed that particular issue. Well at least now I can tweak those ingame settings such as resolution and Gameworks options in game without worry that my game tweaks will break. Though doesn't ini files change as well when you change those settings ingame? Not just the XML is touched from what I remember.