Installera Steam
logga in
|
språk
简体中文 (förenklad kinesiska)
繁體中文 (traditionell kinesiska)
日本語 (japanska)
한국어 (koreanska)
ไทย (thailändska)
Български (bulgariska)
Čeština (tjeckiska)
Dansk (danska)
Deutsch (tyska)
English (engelska)
Español - España (Spanska - Spanien)
Español - Latinoamérica (Spanska - Latinamerika)
Ελληνικά (grekiska)
Français (franska)
Italiano (italienska)
Bahasa Indonesia (indonesiska)
Magyar (ungerska)
Nederlands (nederländska)
Norsk (norska)
Polski (polska)
Português (Portugisiska – Portugal)
Português - Brasil (Portugisiska - Brasilien)
Română (rumänska)
Русский (ryska)
Suomi (finska)
Türkçe (turkiska)
Tiếng Việt (vietnamesiska)
Українська (Ukrainska)
Rapportera problem med översättningen
I did read that 1.2 supports regular SSDs as well which may improve load times in the future if more games start supporting it, don´t know if I understood that correctly.
But yes with Win11 updated to 22H2, you should have DirectStorage v1.2, which added support for SATA SSDs and HDDs.
You can clarify that you meet/exceed the DirectStorage Requirements by bringing up Xbox GameBar > Click Settings > Click Game Features. If WINKEY+G does not have it pop-up on top of whatever you have loaded up, such as a Game, you might need to enable Xbox GameBar in Windows via Settings > Gaming.
Many new games feel broken due to CPU bottleneck partly caused by heavy data streaming. Direct Storage shifts that work from CPU to GPU.
Doesn't say anything about that in the news from Microsoft themselves.
While it does work with SATA SSDs/HDDs; it is more preferred that you use an NVME SSD to get better results.
Kind of pointless; since it's not that hard to simply shift your games around easily and simply put games you are playing now and that benefit, onto an NVME SSD.
People act like they have to have MANY NVME SSDs in their systems; not true if you learn how all of this works, even if you are not or can't use DirectStorage.
That said, until recently my system couldn't do DirectStorage BypassIo due to an incompatibility with the Malwarebytes Anti-Ransomware driver, but a beta of Malwarebytes fixed this as of March 30.