Indeed. A .exe is really just a self-injecting .dll, so it's actively changing the memory of the game. This just enters console commands.
Printable View
I do not know why but when I use this my FPS drops from 150 to 20 and makes the game unplayable.
Nice work :)
after the latest update, this doesn't work any more. could you please update this too?
Thanks for the tut
Code:GameTime.MaxVariableFps 59.000000 or 119.000000 (120Hz monitor)
PerfOverlay.DrawFps 0
PerfOverlay.DrawGraph 0
PerfOverlay.Enable 1
Render.DrawScreenInfo 0
RenderDevice.Dx11Enable 0
RenderDevice.Dx11Dot1Enable 0
RenderDevice.Dx11Dot1RuntimeEnable 0
RenderDevice.TripleBufferingEnable 0
RenderDevice.vsyncenable 0
RenderDevice.ForceRenderAheadLimit 0
Screenshot.Format jpg
UI.DrawEnable 1
WorldRender.DxDeferredCsPathEnable 0
WorldRender.TransparencyShadowmapsEnable 0
WorldRender.MotionBlurEnable 0
WorldRender.MotionBlurForceOn 0
WorldRender.MotionBlurFixedShutterTime 0
WorldRender.MotionBlurMax 0
WorldRender.MotionBlurQuality 0
WorldRender.MotionBlurMaxSampleCount 0
WorldRender.SpotLightShadowmapEnable 0
WorldRender.SpotLightShadowmapResolution 256
WorldRender.LightTileCsPathEnable 0
PostProcess.DynamicAOEnable 0
PerfOverlay.DrawFps 1
WorldRender.PlanarReflectionEnable 0
PostProcess.DynamicAOEnable 0
GstRender.Thread.MaxProcessorCount 8
Thread.MaxProcessorCount (amount of physical + virtual code you have. in numbers)
this is my config file
also set in nvidia control panel so that maximum pre rendered frame = 1
Set in game, all settings to LOW (except for big maps, put MESH ON ULTRA)
Set in game also for "fov scaling when ADS" for MORE ZOOM WITH OPTICS
the game will look like crap, but soldiers are rendered AFTER objects, meaning that you can sometimes see what's behind a decoration w/o wallhack
^ Is this still working?
Thanks!
Awesome. Just made this account now to post this. It worked and like Scotia said, it is not bannable ! (:
~Snoop
Last I had heard of, you need to remove the UI.DrawEnable 1 command from the config because it is causing the game to crash on startup. A member of DICE posted this this on Battlelog. The thread on battlelog where they said that is called "PC crashing issue workaround 25/02" and it is in the Battlefield 4 PC forum on battlelog. Other than that all of the other stuff in the config works just fine, I still use it.
Bumping to say that this works as of the latest update.
->Yellow 13
How do I calc this?
Thread.MaxProcessorCount (amount of physical + virtual code you have. in numbers)
my system:
win7 64
i7-4770 at 3.50 GHz
32 GB ram
2-2GB GTX 760 in SLI
actually, don't put that command in
it's invalid