Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thanks in advance, and thanks for all the efforts.
Here's the link in question:
http://steamcommunity.com/app/427190/discussions/2/350542145694301755/
I can now see the game's mouse cursor for a second or two longer before the game crashes. So something has changed, but the game still crashes, at least for me.
It still crashes after writing the line "MotionBlur=ON" into config.ini.
The team has various configurations low to high end PCs and so far none of them exhibited the problem some of you have reported. They'll keep looking into it though.
Couple of posters on the forum noted that turning off Windows compatibility mode (e.g., Windows XP) from the game executable properties fixed the problem for them. Might want to give that a try and see if that helps.
That didn't work because compatibility mode wasn't on when I went to check, I really can't wait for a patch any longer because I bought this on day one and the two weeks are almost up. Thanks for responding though, it's good that the team behind this knows about the bug. I'll keep looking at the forums for help though.
You're the third to report this (I can only suspect that the others who are affected are not as patient as we are, as *no one* has reported that this specific issue has been resolved).
Seemingly, the developers are changing little lines of code, then rolling out a patch, we try it out, it does not work. (The same seems to be true for other bugs like wrong music loops. Those can also easily be fixed with log files.)
I've been trying for two weeks now to convince support to produce a beta version that logs *where* the game crashes. That is a standard procedure in software development and testing.
That way, the error could be found and repaired. Takes less then a work day, heck, even less than an hour.
I have been provided with a version that was supposed to fix the black screen. It did not. And it did not produce a log file, so the programmers STILL cannot possibly know where the game crashes!
So it doesn't work, but it also doesn't help the devs fix the bug! I cannot imagine how they are supposed to find it if they practically force themselves to poke around in the dark.
So all we can expect for now is this continuation of trial-and-error. I cannot possibly imagine how they are supposed to find it if they are unable to reproduce it themselves AND fail to implement a log feedback procedure.
I'm really trying to be patient here, but seriously, this is Software Development 101. I'm expecting a little more from a big player like Capcom.
I'm willing to help repair this, but how can I do that if the programmers do not implement a feedback method for themselves what works and what does not? How is that supposed to work?
It's frustrating for those affected, but it's even more frustrating when you have experience in software engineering and testing, and you could easily fix this yourself but don't have the source code.
Sorry for venting, but seriously, I've suggested this two weeks ago. And it's something that is standard in software development.
We can probably expect a patch when the development cycle changes significantly. Other affected users have probably already refunded.