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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
2. nvidia has released 2 driver updates in the last few iterations to address some crash issues both for ark and for the 2000 series cards specifically.
3. D3D issues have been plaguing Unreal Engine 4 games for a very long time now and Epic keeps kiting fixes for it. You can see from their issues page here: https://issues.unrealengine.com/issue/UE-51650
4. Verifying file integrity is mostly a placebo that people throw out and mostly do so when they see it saying 1-3 files requiring fixes(its related to the dynamics with server listings actually).
And I could go on....
Suffice to say that while you feel your set of things is a "fix" its not, necessarily. At best its a work around that currently works for your rig set up that minimizes the d3d issue occurences but does not guarantee it from occurring for you in the future and certainly not for others with different hardware combinations.
This is the umpteenth post you've made in other people's threads. Post in your own thread and cite your Steam detected system information, mod use, 3rd party programs, ingame screen shot'd settings and more.
Ranting saying "Im crashing" in 5+ threads of others is silly.
What some people also don’t understand is, that you can have the same error as someone else, but caused by something totally different with a different solution as well. Saying something like “This will fix this error for everyone” would be very misleading.
For yours, start a new thread :-)
Again Epic, the maker of the game engine acknowledges this issue cannot be resolved and keeps kiting a true fix for it as I linked above just one jira about it.
My fix was turning on the swap file. Even though I had enough vram and ran to spare.