My rig (now) has the following drives, letters were the same before except as noted:ĭ - Windows 10 (Old SATA Kingston "SSD formerly known as C)į - Sim Drive (500GB SSD [S drive on old Windows) I didn’t want to be out of action for a week while I re-install everything though. So my best course of action was a fresh install. I also read (but cannot technically verify) that the bootloader gets different drivers for Nvme/PCIE storage than SATA.
Yes you can - but from what I read, there are many times this doesn’t work. Time for some real SSDs, and I picked my new motheboard specifically to handle two NVme’s without axing a SATA port. To note, my C drive is an older Kingston SSD Now - these are cheap and from my experience - durable SSDs but the performance is what you pay for - less than $100 for 256GB if I recall correctly, and that was back in 2014 or so. C drive average response time hit over 4 seconds. However, every time Windows was working and accessing C, the game paused. Since 2.5.5 came out, I have been having numerous “micro-pauses” in DCS that last upward of 5-10 seconds (enough to turn a cat launch into a swim).Īnalyzing my system with the performance monitor up showed that my 32GB of RAM had plenty free, my i9-9900k could take a lot more work before being overburdened, and the SSD for DCS was doing rightfully doing nothing, as everything was loaded into RAM. I recently went and bought two WD Black SN750 500GB Nvme drives for the purpose of replacing my C drive and the one hosting my DCS installation.
0 kommentar(er)
