Fps Drop
- Thread starter Nazarick
- Start date
Nazarick
New Member
- Joined
- Jun 13, 2018
- Messages
- 18
- Reaction score
- 2
same result bot start walk fps drop 10-20. idle fps 150+ with turn off shadow
poe setting:
borderless_windowed_fullscreen=false
directx_version=9Ex
dx11_antialias_mode=0
dx9_antialias_mode=0
dynamic_resolution_fps=120
fullscreen=false
global_illumination_detail=0
light_quality=0
max_PS_shader_model=ps_3_0
max_VS_shader_model=vs_3_0
maximize_window=false
post_processing=false
resolution_height=639
resolution_width=1049
screen_shake=false
shadow_type=no_shadows
target_fps=120
texture_filtering=0
texture_quality=5
use_dynamic_resolution=false
vsync=false
water_detail=0
Last edited:
Change your NetworkingMode to Predictive and not Auto. It'll help avoid some issues botting if you're client is using lockstep, but if it's using predictive already, you won't notice a difference.
Frame time is affected by code the bot runs in a single frame. The more objects and effects on screen, the higher the normal client frame time is, and then the added effect of the bot having to process those objects is what leads to frame time spikes.
A large part of the performance impact of running the bot comes from using OldRoutine and running combat logic. If you were to run a simple follow bot, for example, you'll notice there's hardly any performance difference. This is because the bot isn't having to process a bunch of complex objects in game memory, which requires accessing a lot of underlying data to figure out what it can attack or can't. This adds up really fast and you start to see the frame overhead as it's a lot of CPU and memory reading going on.
This is just a limitation of how an external bot that has to sync with the client works. There's no way to not affect frame time and have EB work the way it does. The only way to really improve performance is to have the bot do less, not process objects as much, and things like that which create undesirable side effects.
Frame time is affected by code the bot runs in a single frame. The more objects and effects on screen, the higher the normal client frame time is, and then the added effect of the bot having to process those objects is what leads to frame time spikes.
A large part of the performance impact of running the bot comes from using OldRoutine and running combat logic. If you were to run a simple follow bot, for example, you'll notice there's hardly any performance difference. This is because the bot isn't having to process a bunch of complex objects in game memory, which requires accessing a lot of underlying data to figure out what it can attack or can't. This adds up really fast and you start to see the frame overhead as it's a lot of CPU and memory reading going on.
This is just a limitation of how an external bot that has to sync with the client works. There's no way to not affect frame time and have EB work the way it does. The only way to really improve performance is to have the bot do less, not process objects as much, and things like that which create undesirable side effects.
