Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
Two totally different engine pipelines to start. Also, entirely seperate developer parties. All they have in common is the publisher.
EDIT: How do you feel DirectX 12 is going to add to your experience with the game? It's an API runtime; and honestly the game has enough performance issues as is. Even with high-end configurations.
Wildlands eats VRAM like there is no tomorrow. I have 1080Ti units in SLi (FTW3 v1), and I have seen as high as 8.7Gb allocated in video memory at 2560x1440 (Ultra preset). It is a very intensive game; even when compared to Snowdrop engine (The Division).
DirectX 12 will not help resolve this issue. That much I assure you.