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
1) Edit user.settings
Navigate to C:\Users\YOURUSERNAMEHERE\Documents\The Witcher 3 and open user.settings with notepad++ or notepad.
Navigate to line
MovieFramerate=30
and change 30 to 60. Save, and exit.
Yes I know very late to this discussion but it saved me a lot of time and trial and error!
So anyone else not convinced that this may solve your cutscene crash issues, I would strongly suggest you try it.
Crash Issue - when?
On entering the hut where Ciri is located a cutscene begins, but no immediate crash for me. However, after Geralt sits on the bed and begins to hug what appears to be the lifeless body of Ciri, Ciri suddenly responds after the Firefly spell touches her forehead and begins hugging Geralt back - at this point the game plays a flashback clip of sorts and this always resulted in an immediate CTD with no error reported
Background
I got to this point in the game (first playthrough) and never experienced CTD's in cutscenes at all until the one described above.
It irks me to say the least when some people read possible solutions and make ill advised and misguided comments without knowing how a change like this could actually solve a problem because they have some knowledge but not complete understanding.
I have worked in the game industry for almost 25yrs and know that sometimes things work even when at first glance it appear that they shouldn't. Thats the truth right there. In order to fully understand why something works you would need to have the source game code and only then you might have a chance at unraveling the complexities of the issue/bug.
Sir Arthur Conan Doyle was a genius
In the late 19th century this writer knew what people in the 21st century have still failed to grasp!
How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth?
The Sign of the Four 1890
We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth
The Adventure of the Bruce-Partington Plans 1908
That is the case as it appears to the police, and improbable as it is, all other explanations are more improbable still
The Memoirs of Sherlock Holmes 1892
The Adventure of the Beryl Coronet 1892
It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth.
After all these years and updates, this one worked for me, too. Thank you very much.
Sadly this didnt work for me, I'm about to give up because I've looked up every fix for this and there's just nothing that works, It's quite annoying. I used to play this game with no issues.
This works on DX11 !!
So old game and still issues like this. Fcking joke