ติดตั้ง 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 (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
กฎและแนวทางปฏิบัติในกระดานสนทนา
รายงานโพสต์นี้
Yeah I ended up doing that very thing. So it can't be that my drivers have installed thru windows 10. I am very aware that it does this by default. :)
This could be absolutely funny if that is indeed the source of my issues right now.
First of all, it really does not matter what reference material you use if your understanding is limited to user configuration propagating in reverse up the chain of configuration files and into the base configuration. It doesn't work that way, those files are immutable. You have yet to explain to me where these values that I am supposedly corrupting are being saved, the only claim you have made, which is verifiabily incorrect is the one I just mentioned. If you could point me to design specifications that discuss the game re-cooking itself when values are out of range as you are claiming, then I will happily concede.
Furthmore, I've never badmouthed Rocksteady. I've made some tongue-in-cheek comments, but I thought that was pretty well understood. I've criticized design problems that I have encountered while analyzing their work, but if you examine any bridge you are going to find cracks -- I can either choose to ignore them because that somehow makes me more of a saint or I can mention them and temporarily plug them. I will chose the latter option whenever it's within my capability to do so.
If they read this thread, they will see what they are doing wrong. I make a point to spell out every little minutiae of effort I put into this stuff. You need only scroll back maybe 2-3 pages to see my latest development, which is to workaround some faulty logic where they are selecting DXGI Adapter 00 always. It's leading to 0.0 MiB of reported VRAM on Hybrid GPU systems. My work is documented and the source code will be available by the end of the week.
This tool's source code and development are also thoroughly documented throughout this thread - but you have to dig through a lot of troll posts from Jesus/Toothbrush/King Charles/Batman/<Whatever He Calls Himself 5 Minutes From Now> and yourself. Searching this thread is a veritable goldmine of information, as is the source code repository. I have never claimed to be the only person capable of identifying issues in this game, that is some ridiculous notion that both you and Batman came to on your own and I have no idea why; you both behave very similarly and if I did not know any better I would swear you are the same person.
This last statement is on my mind and have been paranoid ever since. Whenever the other troll comes into this thread HooksGuru is no where to be seen. They are never on at the same time from my obsverations. I have noticed this and gets me really paranoid.
To boot didn't King Charles 2nd finally state he had the very background that HooksGuru claims to have. But at same time HooksGuru has helped me plenty of times. Right now I am pinpointing what could be my main issue with this game is right now.
This is true :) I have seen you spout against him. Also I am at the moment trying to install Logitech's latest drivers to see if that fixes some issues. Windows 10 can be a pain in the arse to deal with lol.
There's not a whole lot new here, but you can safely experiment with some of the settings on the patched version of the game now. I don't have any solid performance data to back up the 3 streaming profiles (they are the same values as before the patch), so play with them a little and don't be afraid to use the Default profile.
I took the little asterisk off the Default profile because the default configuration is pretty stable now -- performance I cannot vouch for, but stability I can ;)
I am not planning to add an Adaptive VSYNC option to the main dialog, if you want it, it's buried in the NVIDIA Driver Tweaks sub-tool. Setting it there overrides the in-game setting and allows you to do 1/2, 1/3 or 1/4 refresh adaptive VSYNC (1/2 refresh Adaptive VSYNC is useful for frame pacing on 120 Hz monitors capped to 60 FPS).
---
I still have not had time to play with the 3 new texture streaming parameters; sorry. If anyone is bored, fiddling with the following settings (BmSystemSettings.ini) and reporting back would be helpful:
One would expect reducing those numbers to reduce hitching (very big problem with this patch) at the cost of pop-in (which I find non-existent). I would suggest trying changes to those values using either the Default or Balanced profiles to get a good measure.
---
PhysX Level will be coming out in a future release. It serves no purpose, the game engine either switches the low 3-bits of that number on (if either Interactive PhysX effect is on) or off (no Interactive PhysX). So it's always 0 (Low) or some multiple of 7 (Ultra) after the game exits.
I will also be getting rid of the Misc. Tweaks section unless anyone can tell me what "DX10 Features" does :P That section was full of community tweaks that I don't know anything about.
Last, the Framerate Hacks section is going away too. The only people who need to change MaxDeltaTime know why they need to change it and can do it by hand.
With all that stuff gone I'll be able to fit the new post-processing options.
Is it released yet? I am ready to try it since my Stuttering is horrendious atm with the newest patch and 100% fresh reinstall of Batman Arkham Knight. I have somehow managed to now reach single digits in cutscenes. Don't know how but I did.
Oh, and I get the joy of re-writing the software manual now =P This thing's gone on way too long, I never expected to have to keep the software limping along 3 months in :-\
Not quite sure if it's still your memory problems, but the answer here might clear things up a bit for you:
https://superuser.com/questions/500057/does-64bit-windows-8-low-memory-warning-have-same-limits-as-in-windows-7-x64/501498#501498
Here is the thing. I noticed by putting higher pagefile I get more of my system ram used in the end. I know for a fact that system is allocating my system memory. I even went as far as using poolmon.exe to find what drivers was causing the memory leak. Thats how people found out that their memory was being used. I tried starving my memory to 2048GB. That is when I get the low memory error. From the bahavior I have noticed from Win 10 is that the committed memory in any application if reaches above 8GB causes my game to have massive fps drops and stuttering. Before patch my vram was used 100% and went to 4GB and system memory kept flushing out.
But after fresh install of game and lowering the settings. My VRAM didn't go above 3GB in usage and my system memory was around 3 to 4GB and pagefile reached no higher than 8GB. In GTA V if this is the scenario the game runs flawless 60 fps. But moment I go above 8GB of pagefile and VRAM goes past 3.5GB my game starts to stutter and fps drops a lot due to using my hdd more. My HDD light is constantly flashing while running games. I mean almost solid.
With Metal Gear Solid V it is as of right now the perfect game working. Running it at 1440p with TRSSA 4x forced and hitting almost constant 60fps with only a few drops in fps here and there. Doesn't use more than 3GB of my VRAM. Pagefile stays at around 8GB. System memory is around at 2.5GB.
But right now Batman AK is showing the same behavior in memory usage as in MGSV. But in this case the game drops to single digits in fps. I do not understand why this is happening. It normally ran solid 60fps when my resources were at these levels. I have lowered settings to normal which is why the game isn't using more than 3GB of VRAM during initial cutscene. Pre-Patch when my memory were at these levels game ran almost perfect without any stuttering or hitching. But that isn't the case with post-patch. Its is horrible. I can't even watch the first game cutscene without it being a mess in stuttering.
http://i.imgur.com/56XPjJi.png
I should point out I had Chrome running in background. Without Chrome running my memory is at like 1.7GB.
Also now that the game has proper 60fps if I put it locked at 30 it really is much worse. Pre-Patch 30fps felt like 60fps. Which was amazing b/c it was fluid and pretty much epic when it didn't past the memory limits. But now the game runs proper 60fps by limiting it to 30 fps it does the exact slow motion blur / ghosting effect that witcher 3 does when you limit it to 30fps or GTA V to 30fps. 30FPS now is extremely slow and hurts my eyes a lot more.
Now just simply turning my head it goes from 60 to 20 in an instant and stays there until I stop moving my head in circles.
Consider switching from Chrome to Firefox if you're having memory trouble.
I did a paper a few years back on real-time memory management and found jemalloc (the allocator Firefox uses) is the best all-around allocator on Windows (best on almost all platforms tested). It'll definitely perform better and consume less memory on a system that's already low on memory.