I tested different values for the RenderDevice.RenderAheadLimit in the in game console to see what it would do to the fps. Not sure what the range of values could be or what the default value is. As the nvidia control panel setting goes from 1-4. I assume in the console it would be similar. Either 1 to 4, 0 to 3 or even -1 to 3 as another thread has suggested.
-1 no change
0 no change
1 massive fps drop!
2 no change
3 5 frame increase
4 no change.
I suggest trying this out for yourselves, as you definitely don’t wan’t it set to a value that cause an fps drop.
With people having different results with the the render ahead limit, it makes me wonder what BF1’s default value is? and would it adjust to suite your specs if you used the auto graphics setting?
Well, if I’m correct in my assumptions, renderahead determins how many frames your CPU prepares before sending it to your GPU. This theoretically makes the game smoother as it helps cut the time to render through GPU.
That being said if you have a good cpu (I7-4XXX etc) it won’t help if you have a bad GPU, on the other hand if you have a bad CPU but good GPU then it may help (as it reduces load on CPU)
This won’t improve your framerate dude, if this is doing something, is avoiding some sutter, and even it doesn’t work in every scenario. And adds input lag, not very good idea in a competitive shooter
Considering the affect it can have on fps and that it can have a different affect on different cpu gpu setups. You would think it would be in the graphics settings rather than hidden in the console.
-1 is default value - therefore means “use driver default”, or if the driver says “use game default” ends up being set to 2.
0 You can’t have 0 pre-rendered frames. You need to pre-render at least 1 frame by the CPU otherwise the GPU doesn’t know what to render ;-). Setting to zero just means “bypass” of the command (i.e sets it back to default)a bit like when you set gametime.maxvariablefps to 0, it disables the fps limiter.
1 - having just 1 pre-rendered frame cuts input lag in half, but also unless you have an absolute beast rig in a hugely well optimised or very old game, then it’s pointless since it also will tank your frame, which, guess what - increases input lag as well as looks like crap. therefore cancelling out any advantage. If you’re running BF3 on a Titan X and can get 300+ fps and only have a 60hz monitor, set it to 1, otherwise avoid.
2 - Same as default value. happy medium with CPU pre-renderring enough frames to buffer the GPU, but without excessive input delay.
3- Some argue this can slightly even out frame cadance, but in theory at least would add a bit of extra input delay.
4- Seems to be ignored by the engine, probably just sets it back to 2 or 3. In fact, you can change it 5,6,7,8,9, or any number, and it doesn’t do anything different.
Render Ahead limit 1 actually works great for me on my i5 6500 gtx 1060. Dropped my cpu usage down to 60-80% and I’m at a smooth 60 fps on every map besides Empires edge which drops down to 55.
Probably already answered but RenderAheadLimit it the amount of frames being queued to CPU. This might add more frames but at the cost of adding more latency.
Lowering will also reduce CPU load and also reduce stuff like stutter.
0 is not a real option! it just defaults back to 3... Think about it if 1 is bad then 0 would be even worst.
1 massive frame hit your frames will pretty much cut in half.
2 you will lose about 20fps but IMO if you can afford it is best it really cuts down on latency this also results in lower frames generally feel smoother.
3 This is the default setting: IMO too much latency.
4 adds no benefits in frames but adds lot more latency
Default settings I was at a constant 100% cpu usage with stuttering throughout. I’ve got my resolution scaling set to 125. I do wish the game was more gpu intensive as it’s only using 40-60% at a time but I’m happy with my performance as of now.
Can confirm 1 gives me 20 less fps and 15% less CPU usage.
I’m going to stick with 1. When I use anything other than 1, I get more fps but I notice a sort of timing issue that annoys my eyes e ven with freesync.
