thebagsman

It can be as much, or as little as you want. The F/A-18's a bit over my head, but any of the Flaming Cliff planes, like the F-15, Su-27, A-10A, don't have fully clickable cockpits, so you'll have a realistic flight model and radar, but you don't have to mess around with the different modes and intricacies like you would have to if you were in the F-14/16/18 or A-10C modules. 
 
99% of my time in DCS is spend in the F-15C, it's awesome, especially for BVR stuff. 

it is. Its not as much a game per say, but more a work out style game that utilized boxing in VR very similar to Beat Saber

It's very easy to build in.  I put it together while taking a work call in about 30 minutes.  Some of the issues I found are that depending on the location of your on-board DP or HDMI, that may be blocked by the case frame.  I also wish that NZXT went the extra mile and built a USB hub on the back since you have to turn the case on it's side every time you want to plug something in.
 
However, NZXT builds quality cases.  They are well felt, fit together well, side panels are rugged and stay in place, plus their tool-less features are well thought out.  Built in a lot of cases, and the H1 and H710 are two of the best I've worked with.

I already have 2 1T HDDs at home

People have always said cache OCing doesn't matter, and have usually been wrong. "Cache" as it's labeled on current mobos, is just RING/Uncore on older stuff. Uncore being everything not the cores themselves, including the ringbus and such. On old chips it makes a very noticeable difference (they often run 1.8Ghz stock, but can easily do 3-3.6GHz when OCed), on newer chips it's less noticeable, but still can effect 1% lows and a little bit on the highs as well. It makes the chip overall snappier, reducing some latencies inside the CPU itself I assume. 

Here's a fellow LTTer's thread on how it affected their 9900K, which is a much more recent chip than the stuff I run: 
Higher scores at 4.9 core/4.7 uncore than at 5.0 core/4.3 uncore (which was the stock uncore I believe), so core speed isn't the only thing that matters. 

Manually OCing the RAM (if you just want XMP speeds) is easy since they print the XMP specs on the side of the DIMMs. Just slap the voltage, speed, and main timings from there in and leave all the other timings on auto. 

An AVX offset applies a negative multiplier offset when running AVX workloads. So say you ran 5GHz with an offset  of 2, your chip actually runs 4.8GHz under AVX workloads. I'd skip using an AVX offset, just find the speed your chip will pass any test you throw at it with, and leave it at that. 
 
Load Line Calibration is a vDroop counter. vDroop = voltage drop when under load (say you set 1.3v but it actually pulls 1.24v under load). LLC will counteract this by running a higher voltage than you set, so when vDroop happens it doesn't drop so low that your chip becomes unstable. It can be a bit of a balancing act to make sure it doesn't push too much voltage, but once you figure out what your motherboard does, it's pretty easy to work around. 
 
As far as tweaks for optimal OCs, on an 8700K that's just remembering to OC the cache too, it can lead to an improvement in 1% lows and overall snappiness of the chip. 

I agree but I am an anxious person by nature. As an update. The entire transfer went just fine. Had a great time doing it.

RAM is keyed, so it can only go in one way.... There is a notch on the side that you insert into the motherboard slot, and that notch is offset. This is the "key", line that up with the bump in the mobo slot, and your good to go.
 
As others have said, make sure you first "open" the clasps at the bottom and top of the motherboard slot. You have to open those, then when you pop the RAM in it will clasp them shut on its own.

Very true. And I've never stopped learning new things even when I'm not actively working on a build. In all likelihood I just need to slow down. Step-by-step like you said. I think I'm so nervous about getting it done to make sure it works that I stress myself out. I should just enjoy the process. And also probably not drink caffeine. 

* Thread cleaned *
 
If you're not going to help, then please, DO NOT reply.

I am sadly just another sad American.

AMD and Nvidia drivers notoriously hate each other. You pretty much have to entirely remove the drivers of one brand before using the other.

AMD and Nvidia drivers notoriously hate each other. You pretty much have to entirely remove the drivers of one brand before using the other.

I'm not sure what point your making here with this info.