siefex

Ditto! I am on the fence about upgrading my two 6950s to a single GTX 680 (preferably the classified 4GB edition to be released this June by EVGA). Your results will play a significant role in my decision-making process.

Well, that's a lot of stuff to learn! However, it all sounds fascinating, EXCEPT to master the CDU. I hate the CDU. I know how to use it for basic functions, but the CDU and I often get into heated arguments! Well, I guess I'll just have to give my manual / DCS Bible's section on the CDU a good read through again and I should be better. Thanks for the words of encouragement all! I really could not have made it over the huge learning curve of this game without the support of this community.

...I did a cold startup, took-off, contacted JTAC to receive attack coordinates, setup my SPI using my TAD, prepared all weapon systems for attack, navigated to attack point, blew up the tanks, used the divert page in the CDU to find my base airfield, and landed! Wow, that is a lot of stuff I had to learn how to do over the course of the last 3-4 months! But damn, is it rewarding! A word of encouragement to those just starting this sim and feeling daunted - hang in there. What helped me learn this sim was to think about it in steps. I spent one weekend just figuring out JTAC and weapon systems for example while, another weekend, I worked on my landing. Then, it all started to come together. This is also my first real flight simulator so hopefully other simulators I play like ROF will not require such a tremendously long time to learn. Just wanted to share. No one in my RL can relate to how much of an accomplishment it is to overcome the learning curve of this sim!

Hahaha - Got a good laugh out of this.

Do you think that will actually make a difference in the frame rates I'm getting in DCS compared to what I'm getting now? I'm getting like 45-50 FPS on the ground (with MFCDs exporting to helios), and then a little over 60 when I'm over mountains. I don't want to blow $100+ on RAM just to get 2 FPS difference. Plus, I'm still wondering if my computer is just getting faulty information within CPU-Z from 2 of my RAM sticks when in fact they are running at the correct settings. Thoughts?

Just found this thread by a similar person who ran into my problem. Looks like Corsair is selling very similar-looking memory modules; yet they are in fact different from one another... http://forum.corsair.com/v3/showthread.php?t=82227 So what do you guys think I should do? Toss out the old pair and buy another new pair which will match the latest kit I bought? Or, should I just get a brand-new 8 GB set so that I buy all my modules in the same package? Will doing this increase my performance in DCS in any way?

Ok all, here are my CPU-Z screens as promised. Please take note of three problems as made clear by the below images: 1.) Dimms# 1 and 2 are clocked at 667Mhz while Dimms# 3 and 4 are clocked at only 533Mhz. 2.) Dimms# 1 and 2's timings are 9-9-9-24 while dimms# 3 and 4 are 9-9-9-26. Is this significant? 3.) All dimms should be running at 1.6v; yet CPU-Z indicates they are only running at 1.5v even though I have specified the correct voltage setting in the BIOS. Thank you to everyone for helping me to figure out this confusing issue. Here are the images. If they don't pop-up right away, simply right-click and save the URL then open it in your browser:

Question for everyone reading this thread: when you look at all four of your Dimm pages within CPU-Z, are the EXACT same numbers displayed on each page for your memory's timings and frequency? Just curious. Still at work, going to get home in the next few hours and get my CPU-Z pages posted.

When I get home tonight, I will post my CPU-Z tables. I'll get back to you guys soon. Mine definitely do not look like what you just posted.

Thanks for your suggesttion bumfire. If this is similar to what you are suggestiong, I have tried running my RAM on "AUTO" settings within my BIOS. However, that causes my RAM to run at frequencies which are significantly off from its standard settings. Also, the voltage is set to 1.5 in that circumstance. Where do you usually find this XMP profile? Could it be named something else? I'm running the below RAM: Corsair XMS3 1333Mhz 9-9-9-24. Newegg Link: http://www.newegg.com/Product/Product.aspx?Item=N82E16820145198&cm_re=xms3_4gb_ddr3-1333-_-20-145-198-_-Product

I thought the same exact thing. My BIOS is all configured as it should be, yet I'm noticing in both 3DMark and Cpu-Z that 2 out of 4 of my sticks of RAM are at a different frequency. I will assume that you guys are right about this; however, just to be on the safe side, I'll throw a post up on my motherboard's website and see if others have encountered this issue. Please feel free to offer additional suggestions, thanks!

Hi all, After running a 3dMark 11 test today, I noticed that my RAM is running at different frequencies to my surprise since I have already correctly set my timings and associated frequency in my BIOS. Regardless, here's the situation. I have four sticks of 2GB per-stick DDR3 1333 Mhz RAM. Two sticks are running at the correct 1333 Mhz freq and are using the correct timings I specified of 9-9-9-24. However, the remaining two sticks are running at 1066 Mhz with an incorrect freq of 9-9-9-26. Does anyone know how to correct this problem? In case it is helpful, my motherboard is an ASUS M4A78T-E. Another issue to mention is that CPU-Z states that my RAM is only running at 1.5v when it should be running at 1.6v. Now, I have already set in the BIOS for the RAM to run at 1.6v; yet CPU-Z does not reflect this fact. I would also add that AMD Overdrive does display that the RAM is correctly running at 1.6v so, is there just a problem with CPU-Z here or do you guys think my RAM is really running at 1.5v? Thanks for all the help!

Nope, this happens also with 11.2 CCC drivers.

I have this also. Just happened with 1.1.0.7. I'm running CCC 11.2.

!!!??? Dude, that will be awesome! Normal landing is boring. I want to land with no landing gear at all! Although, I don't think I"d want to do that in real life, ha!