FPS Drop When Looking at Mountains

[hansangb]

By the way, pagefile should *absolutely* go on the SSD. pagefile is nothing more than "memory on disk" Since HDs are several orders of magnitude slower than RAM, pagefile should go on the SSD. (being that SSDs are so much faster than magnetic HDs).

 

hsb

[Ultra]

So I disabled Crossfire and tried it again. FPS performance was neither better nor worse than with Crossfire. Obviously there are some problems on that front illustrated here:

http://forums.eagle.ru/showthread.php?t=149180&highlight=SLI

 

GPU usage at 99%. VRAM and Temp were fine. The Pagefile usage went down ever so slightly without Crossfire, but is still hovering constantly around 8G's which seems really high to me. My RAM had only 5-6G's being used. Another weird thing is that Afterburner is only recognizing my system as having RAM=8G's I think. Also Pagefile didn't change at all when I tried manual editing it before, Afterburner was reading its max available space as 8G's as well. Lots of strange-ness.

 

By the way, pagefile should *absolutely* go on the SSD. pagefile is nothing more than "memory on disk" Since HDs are several orders of magnitude slower than RAM, pagefile should go on the SSD. (being that SSDs are so much faster than magnetic HDs)./QUOTE]

 

People online said it causes extra wear on the SSD. Do you think it's worth it/not a big deal?

 

 

EDIT: Turned on ARMA 3 to compare. It ran with a Pagefile usage of around 7.2G's consistently, so maybe DCS is running normal in that respect.

Edited November 6, 2015 by Ultra

[hansangb]

Modern SSDs will last a long time. Besides, most laptops are SSD only these days. Where do these users put there pagefile? And finally, regular drives are far more prone to failure.

 

hsb

[kontiuka]

Disable shadows (or use flat only)

I'm not sure flat shadows are working properly: http://forums.eagle.ru/showthread.php?t=151785 Edited November 6, 2015 by kontiuka

[Ultra]

Ok, thanks for the input, hansangb.

When I referenced that thread above I only read the first page or so, but upon further reading the solution to my problems might actually be in there. I'll try it tomorrow, hopefully that's it.

[hansangb]

Good luck. And because of you (pointing me the thread) I just ordered another GTX980! :) LOL. It looks promising enough, and I figure Rift DK2 may not use it, but CV1 (or other VR solutions) will eventually use it.

 

hsb

Edited November 6, 2015 by hansangb

[Decibel dB]

Ok a couple of things.

I ran the same scenario checking MSI Afterburner. My Pagefile was maxed out the whole time! Memory usage was high, but not so much to be problematic. Also in MSI Afterburner you select the GPU you want to monitor in settings right? But then it also shows you the GPU2 usage at the same time? Cause I was seeing my GPU1 readings at 99, but my GPU2 readings stay between 0 and 30%.

 

So what's going on here?

 

Hi Ultra do you LALT + Enter on the main screen menu to force fullscreen and X-fire? Even if you tick the fullscreen box in setting it goes into borderless mode and your second GPU don't work

 

Try it out. A good way for me to know was that with X-fire engage, the model visibility have to be off otherwise you will have the frame freeze bug on the 1.5.

[Ultra]

Good luck. And because of you (pointing me the thread) I just ordered another GTX980! :) LOL. It looks promising enough, and I figure Rift DK2 may not use it, but CV1 (or other VR solutions) will eventually use it.

 

hsb

 

Very nice! I'm going to try to hold out for a while before I upgrade, to save money, but I don't know how long I'll make it. :D

 

Hi Ultra do you LALT + Enter on the main screen menu to force fullscreen and X-fire? Even if you tick the fullscreen box in setting it goes into borderless mode and your second GPU don't work

 

Try it out. A good way for me to know was that with X-fire engage, the model visibility have to be off otherwise you will have the frame freeze bug on the 1.5.

 

Yes, that's what I was planning on trying today. Hopefully it's the magic bullet.

[Decibel dB]

Don't forget to turn off the model visibility :)

[Ultra]

Well, the full screen mode worked but it was for nought. Putting it in full screen kicked in my crossfire, but no matter what settings I changed it wouldn't stop stuttering and flickering. I tried setting profiles for DCS with alternate Crossfire rendering modes, but none of them worked. Turning model visibility off didn't change anything either. I guess I'll just run one card on lower settings until this is fixed. :cry:

 

Thanks for the help everyone. Even though I couldn't get it working correctly, I did learn a thing or two along the way.

[dburne]

Perhaps they still have some optimizing to do for Crossfire, maybe the next hotfix will show some improvement.

 

Btw, I flew some training missions in the Ka-50 earlier today, monitored my page file usage in Afternburner, and it stayed around 7.3-7.4 gb...