when I enter renderdevice.renderaheadlimit in the console it says renderdevice.renderaheadlimit int32, what does the int32 mean . All I want to do is make it renderahead 3. And it says that even though I have made a user.cfg file and put renderdevice.renderaheadlimit 3, when I enter the game and type this command it always says renderdevice.renderaheadlimit int32
I think for BF4 it’s
RenderDevice.ForceRenderAheadLimit 3
that value should be set to “-1” by default. i haven’t seen a value of “int32” ever.
are you using the 32-bit executable version of BF4?
- your command line is correct, in BF4, it’s “RenderDevice.RenderAheadLimit”
int32 means it expects a 32 bit integer which means it is a number.
-1 is the default? and I wonder why the 3 is not sticking in the user. cfg file because I have the fps command on and it works. I have never heard of a negative # being used to renderaheadlimit. I think I’m running the 64bit version . I have win7 64 version
You would find the “bf4_x86.exe” if it would run with 32 but. But since you have a 64 bit system it whould start the “bf4.exe” … if that’s not the case just right cklick your BF4 on origin and change it so that BF4 starts with 64 bit.
yea I have run it in the x86.exe and the 64 it also . really didn’t see any difference. the render aheadlimit set to 3 gives me the best gameplay but it will not stay even with a user.cfg file and that command entered there “renderdevice.renderaheadlimit 3” without quotes.
the negative value, if it’s actually that, just means the renderaheadlimit is set to use the driver’s default values; this was how it worked in BF3, i don’t suppose BF4 should be any different. the renderaheadlimit is also know as “maximum pre-rendered frames” (nvidia) or the flip queue size (for AMD).
did you already try RenderDevice.ForceRenderAheadLimit 3 ? because I believe it’s the one for BF4
no I haven’t tried the force renderaheadlimit 3 yet because that doesn’t come up in the console but it’'s worth a try , will try that
just do this, type “RenderDevice” in console and it will list ALL commands that start with “RenderDevice.”
Int 32 means a 32 character integer it doesn’t imply 32bit vs 64bit. Just means that value can be up to 32 characters long and has to be a number…
well when you type renderdevice at the console the renderdevice.renderaheadlimit int32 comes up and I don’t understand why it says int32. it should say 3 like I entered in the user.cfg. Is that not right?
are u pressing your enter key and then looking @ the value?
type “RenderDevice.RenderAheadLimit” then hit “Enter”
that should give you the value it’s set to
*"are u pressing your enter key and then looking @ the value?
type “RenderDevice.RenderAheadLimit” then hit “Enter”
that should give you the value it’s set to"
*
when I do that it says “win32 result 3” without the quotes . so I suppose it is set to 3, thanks . I wonder why it say win 32 instead of win64?
This value is usually forced by your graphics control application or control panel.. If you look there, you’ll find where to change the value rather than on the software calling program side.. typically it is set from 0 to 3.. however, 0 & 1 are not recommended by either Nvidia or AMD …
2 may show you some improvement in bullet lag as what you see on the screen will be more “real” time vs having been pre-rendered …
and to specifically answer your question;
renderdevice.renderaheadlimit int32
is a program variable which expects a value of Integer(-1 to 3)
What a let down, I went from 75FPS with dual R 280x’s to 44fps with Mantle update. I tried -1 through 3 with renderaheadlimit and i was able tto successfully hit 14 fps. Yes, 1-4.