And not a bug, but I finish him on MAXED... I can't do it w/o crosshair, but with it, now it feels far more easy than before HP fix.
Without healthkits and with one unused soda-pack, but I don't record title screen with difficulty(video record start with delay fuu...) and kill him again in second video.
I make 3 tries first time and ~4 second time. Vs more than hour before fix.
And it's seems like pistol model bug was gone... (I have not seen it for a week)
And title screen at end
sorry, I meant in general - not in the video
my current theory is that it might be the fillrate.. 🤔
do you play fullscreen on a 4K monitor?
are there any slowdowns for explo or the lightning in windowed? (like on a 1024x768 window)
and almost forgot: is there any difference with Anti Alias turned off?
No i am using 1920x1080, 4K feels too small detailed or too big sized for me.
I think my slow downs caused by CPU, or may be model/particle loading to GPU, but not a drawing on screen.
I remember slowdown even when i see bare wall without and structure behind. Show electro and flying lightnings and escaping or detonating dynamite. (But dynamite not slowdown itself, +1 to gibs/physics checks)
I playing with some random video settings only at beginning, and see no difference. My general settings fullHD+fixed60FPS+vsync+max-antialising+max-textures.
there goes the fillrate theory 😔
unfortunately the occlusion culling is basic.. not all bare walls obstruct things behind them 😔
if it was the CPU or the particle going to the gpu there should have been slowdowns on the war map too.. 🤔
the messages got a slowdown because it touched the HDD to run a script (on FreeHawk's machine at least)
but in this case the HDD is not touched at all 🤔
maybe its just a timing issue? .. but then it should happen more frequently 🤔
sorry just brainstorming .. in theory I should get slowdowns in the same places - especially on weaker comps 🤔
is there any area or map that is guaranteed to get a slow down? where it always happens?
Hmm, it's strange, I rechecked all places where I can remember mature freezes with cheated walkthrough(while I mostly use electro, and it cause me think about particles and CPU).
I enable stats and even recording video, but no any freezes and frame skips more than 2(like in war map)
My two random thoughts:
1) Now i just enter the game and fast checked, but most remembered freezes occurs when i playing game for 30+min
2) Same as first, but not just time and game problem, but my hardware, aka may be one of HDD in my mirrored-RAID gonna park heads. (But I can't remember this behavior when I play something from it, only small lag when long idle)
May be tomorrow, i try to play longer session from system SSD w/o raid.
I should also mention, that my slow downs could be due to having the game on my external hard drive, its a very good one but i thought i might mention it anyway just in case, i might stick it over on my HDD or M.2 stick, when i record E4 just to see if that is something that could be doing it. and if running it on SSD helped eliminate those random slow downs abnessor, let me know :D
With "stats" enabled I noticed periodical spikes >16ms for swap, and especially while electrocut someone on screen. (It's fun on RTX2060, but unfortunately, I don't have more potato, but 3d playable PC at current time)
It's gone if I disable vsync.
And even more fun: if i switch auto-fps(but still 60, I don't known what mean auto in this section) and vsync on/off multiple times, sometime swap consumes >14ms constantly.
I think I must walkthrough w/o vsync and try to catch freezes(if it still exists), but i have lack of time to it before weekend.
the 'auto' setting just means to skip frames if it takes too much time to draw them
swap is just for the buffer swap time (I pretty much just measure how long the windows SwapBuffers command takes)
unfortunately it's dependent on windows and nearly impossible to sync at 60fps
the workaround right now is to start without vsync in fullscreen and hope that the triple buffering on the gpu kicks in
(which there is no control over - it's all up to the gpu driver)
so don't worry about this one: I know the cause but i yet to find a solution (apart from making 30fps the default) 😔
