C drive ... D drive ... F drive and Hard Drive / GPU Slowness

[The Riddler]

Hey everyone - hoping you can help...

I've got a pretty good system (3.8 ghz CPU, 16 gig RAM, Nvidia 1070 GPU) but R6 Siege kind of chugs on it. Other more challenging games run smooth as butter, but load times for maps in Siege take a long time, and the frame rate will simply not go over 50 or so (average). I've got most settings up high, but textures is only on "high" and the GPU is only using 2.5 gig out of 8 gig available.

So I fire up the Task Manager and the GPU is never going past about 30 to 40% capacity. But the hard drive is melting at 100% whenever a new map is loading.

The C drive (windows) is an SSD where I only keep the OS and a few other system applications. Everything else is on my physical F drive. The copy of R6 I use is installed on the F drive in the Steam 'common' directory.

Task manager says that F drive and the D drive (which is some sort of self-created partition for windows) are at 100% during a map load. No idea why that drive is involved because there's nothing related to R6 in it.

Any ideas? I know other people who have much faster map loads with systems that aren't as good on paper as mine, and they have older graphics cards that are giving them 100+ FPS on the game easily while mine is stuck below 60.

[Glennard]

just as a note, saying your cpu is 3.8 ghz doesnt tell us anything

[The Riddler]

No one has any ideas?

[Lep]

Originally posted by Falkbeer:

just as a note, saying your cpu is 3.8 ghz doesnt tell us anything

[Allan]

do you have r6 in the same hard drive uplay is?

[The Riddler]

It's an i7-3820 CPU, if that matters at all.

My Steam directory is in the F: drive where everything gets installed ... except Uplay - of course - which installed itself in the C drive when Siege loaded the first time. So no, Uplay and Siege are not in the same directory (the C drive is an SSD and the F drive is hdd). Can't install Siege on the C drive anyway because it is only 200 gb and it runs windows so there's no more space.

[The Riddler]

Digging around seems to be suggesting that my CPU is probably the culprit. It may be 3.8 Ghz, but it's still a 2012 Ivy Bridge in a socket 2011 board operating at 22 nm and a 4100 mhz clock. May simply not have the grunt to get past 50-60 fps no matter what I do.

[Edutaker]

dont think the cpu is the problem, had a i5 2400 running at 80 ~ fps on a 1060 on ultra

[Allan]

i had the same problem when uplay and siege were in different directory, try installing again uplay in f:

[The Riddler]

Originally posted by Allandance:

i had the same problem when uplay and siege were in different directory, try installing again uplay in f:

The problem is that UPlay installed itself when I loaded up Siege from Steam the first time. The program never asked me what directory to install UPlay ... it just crammed it on the C drive and I had no choice in the matter.

Is there a way you can bypass that process when Siege loads up and install UPlay in the directory/drive of your choice? If this is a known problem, then you'd think they would allow the user to direct where UPlay installs. :(

[The Riddler]

So I uninstalled UPlay from the C Drive and did a fresh install on the F drive where the game files are all located. That didn't make anything any better.

I played a couple rounds with Task Manager running and noted some interesting trends.

1. The CPU never goes above about 30%. It is a 3.8 ghz chip, but it seems to always stay under a third of its maximum use. Maybe there's some sort of CPU throttling going on somewhere?

2. The GPU never goes above about 40-50%, so there's plenty of GPU room that isn't being occupied.

This is just puzzling me to no end. I'm not finding any obvious reasons why the frames are so low. By the math I should be getting double or even triple the frames I'm getting now.

[MooP]

Originally posted by ← Leprechaun→:

Originally posted by Falkbeer:

just as a note, saying your cpu is 3.8 ghz doesnt tell us anything

Dual core? i5? i7? AMD? CPU speed isn't everything buddy... Core count is another HUGE factor...

[The Riddler]

See above. Your question was already answered. I7 3820.

For those who may have experienced a similar issue ... it is not the Motherboard. It is not the graphic card. It is not that the directory for Uplay is in the C drive while the game is in the F drive.

The problem was that the motherboard BIOS was throttling the CPU to only 1.2 ghz instead of allowing it to use the full capacity. I'm not sure exactly what limiter was in place that was causing that problem, but I flashed the BIOS to the newest version (it was only 1 version behind) and it reset a bunch of values ... one of which seems to have been the one that was causing the problem.

After the CPU was no longer being strangled down to one third of its capacity, the problem with Siege's frame rates was resolved. The game now has a solid, constant 60 FPS average with max rates that can go up to the 190 level in the benchmark. Online rounds were constant 60 FPS.

Long story short ... if you're getting bad frames and your CPU & GPU are pretty good, then run the Task Manager on the Resource tab and check to see if your CPU is hitting some sort of artificial ceiling that is way below the total ghz capacity of the chip. You might be the victim of some stupid internal setting that is throttling down your CPU ... which in turn chokes your frame rate.

[Annihilator]

You have ssd? And hd texture installed? If not have ssd test to disable hd texture.


If you still have a issue idk.Maybe have something problem in your computer.

[Hollow]

decrease the graphics settings man

[Plague]

Originally posted by The Riddler:

Hey everyone - hoping you can help...

I've got a pretty good system (3.8 ghz CPU, 16 gig RAM, Nvidia 1070 GPU) but R6 Siege kind of chugs on it. Other more challenging games run smooth as butter, but load times for maps in Siege take a long time, and the frame rate will simply not go over 50 or so (average). I've got most settings up high, but textures is only on "high" and the GPU is only using 2.5 gig out of 8 gig available.

So I fire up the Task Manager and the GPU is never going past about 30 to 40% capacity. But the hard drive is melting at 100% whenever a new map is loading.

The C drive (windows) is an SSD where I only keep the OS and a few other system applications. Everything else is on my physical F drive. The copy of R6 I use is installed on the F drive in the Steam 'common' directory.

Task manager says that F drive and the D drive (which is some sort of self-created partition for windows) are at 100% during a map load. No idea why that drive is involved because there's nothing related to R6 in it.

Any ideas? I know other people who have much faster map loads with systems that aren't as good on paper as mine, and they have older graphics cards that are giving them 100+ FPS on the game easily while mine is stuck below 60.

100%??? time to replace that hdd than