• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Rift - your setup and average FPS

pandemonium

Golden Member
I'm just curious how many people here are able to play Rift with full settings and what your setups are?

Currently I'm using 2x4830 1GB's and I get ~40FPS with medium-high settings (custom). I'm considering upgrading since the game is gorgeous at full settings, but 15FPS is unplayable. My budget GPU setup may have reached their end for my use.

Would be nice if reviews/benchmarks for new cards included more MMOs other than WoW (being it's a very lax engine compared to many, many others out there 😛) Not to mention FFXIV, which although dead, is incredibly taxing on systems (it's free btw; no excuse reviewers can't use this one).
 
I have a Phenom II 955 3.2 quad core, 8GB RAM, GeForce 570.

The thing that is annoying me at the moment is that despite having a good framerate (60fps in places) I get a constant hitching/juddering when moving around that is very annoying. If I turn the settings down to their lowest point the hitching goes away but to be honest trying to find the point at which the hitching starts makes me lose the will to live.
 
I have a Phenom II 955 3.2 quad core, 8GB RAM, GeForce 570.

The thing that is annoying me at the moment is that despite having a good framerate (60fps in places) I get a constant hitching/juddering when moving around that is very annoying. If I turn the settings down to their lowest point the hitching goes away but to be honest trying to find the point at which the hitching starts makes me lose the will to live.

I also noticed this and although I was getting a constant 40+ FPS was wondering how that was accurate. Through some testing of the settings in specific I found that object distance was the culprit. It may be a bug in the engine...not sure. I'm also not sure exactly what this setting affects since "objects" drawn at zero distance are definitely not shown at zero distance while I'm playing... I see objects much further than this. *shrug*
 
If you want some free FPS without losing image quality, use your video drivers to enable AF and disable it in game. I saw a pretty significant difference, as did several of my friends who made the same change.
 
For anyone still interested in this I managed to fix my stuttering issue:

On a whim I downloaded a CPU temp monitor and it turns out that my Phenom II was running at 65 degrees under load. Which is very bad.

I took off the heatstink, cleaned out the fan, scraped off the thermal paste and put some new gunk on. Bingo! Under load it is now running at about 51 degrees and Rift stutters no more!
 
Sony CW laptop with a 230M 512mb and 2.1ghz Core 2 Duo. 1680x1050 run in a window with all low settings but 4x aniso. The driver is set to high performance filtering optimization. I get mid 20s in Sanctum. Framerate drops way down in rift battles.

If I run it at 1920x1200, framerate is about 15 in Sanctum.

Edit: BTW I use the -dx9 command line switch.
 
Last edited:
I'm using the system posted below running at 1920x1200, settings I run everything at max except for the anti aliasing I select the one in the middle can't go super sample or else the FPS drops to mid 20's. Playable sure, but not ideal. With my settings I generally get in the 30FPS range on average. I can see this game worries more about your CPU then GPU most of the time.
 
I run the rig in sig with everything maxed and no image problems. Of course, that's at 1440x900. My new 24" 1920x1080 LCD arrives today so I think I'm going to have to turn the settings way down for my 4830 to be able to keep up.
 
I will have to check here shortly, since I will have two numbers.

First number will be on a :

AMD 945 3.2ghz (OC'd), 8gigs DDR3 1333, GTX260 on a 23.6" ASUS

Second number will be:

AMD 945 3.2ghz (OC'd), 8gigs DDR3 1333, ATI 6970 on a 23.6" ASUS

Stand by...
 
I get 40 min in Meridan (usually closer to 60) in the outdoor areas. I get anywhere from the mid 80s up into the low triple digits (115-120) in our door areas when I'm alone (depending on the terrain and such). I have almost everything maxed with clutter and clutter radius turned down a bit. I don't use game AA... and I have shadows on env only.

I'm forced to run radeon pro to use AFR to get xfire to work... and it appears that i'm CPU limited in crowded areas as my video cards sit at 50-60% usage in meridian.

I enjoy the game... but I expected better performance with my rig (in sig). I would be happy if I could cap vsync everywhere... but it doesn't seam possible in crowded areas.
 
E-350 based DM1Z netbook, 3GB RAM, 2X1.6ghz cores, Radeon 6310
1366X768 Resolution Low Quality Renderer, All Minimums
14-20 fps
 
I don't think crossfire actually works in this game, I know some people with AMD 6XXX hardware were having issues as well but not 5XXX hardware.
 
So I got my new 24" 1920x1080 monitor today and fired up Rift. Yea, I had to turn the video down to "High" in order to average 30 fps. Time to start putting money aside for a new video card.
 
I don't think crossfire actually works in this game, I know some people with AMD 6XXX hardware were having issues as well but not 5XXX hardware.

That reminds me. I tried it with my work laptop, a Dell XPS 1730 with SLI 8700GT M graphics and a 2.6ghz C2D. I got about the same framerates. I think the game has issues with SLI.
 
I have a Phenom II 955 3.2 quad core, 8GB RAM, GeForce 570.

The thing that is annoying me at the moment is that despite having a good framerate (60fps in places) I get a constant hitching/juddering when moving around that is very annoying. If I turn the settings down to their lowest point the hitching goes away but to be honest trying to find the point at which the hitching starts makes me lose the will to live.

if you turned your settings down then the problem is on the gpu side of the code. Card maybe too hot? Running out of vram maybe?
 
if you turned your settings down then the problem is on the gpu side of the code. Card maybe too hot? Running out of vram maybe?

I reposted saying how I fixed it - clean out the CPU fan, whacked some new thermal gunk on, hey presto!

Instant performance boost.
 
Back
Top