#performance on 0.3.1.0 is bad [solved?] - noticeably increased input delay - possibly 0.3.0.3 too
1 messages · Page 1 of 1 (latest)
i mean what is that heppening on the graph https://www.youtube.com/live/3blRj0lX7To?feature=shared&t=24507
alle th way up to tbc when gpu drops to 50% utilization https://www.youtube.com/live/3blRj0lX7To?feature=shared&t=17487
and so on and so forth, for me 0.3.1.0 is stutter and input delay
man if you are having these micro stutters, whats my RTX 4060 and i5-9400f going to think of the game😂
it's only on experimental in that extent, on live build it was occasional / limited
I see your system started to compile shaders and used resources on that. can that be the reason for the performance decrease you are mentioning ?
at what timestamp at video
Just playing the game while trying to break it as much as i can.I usually don't usually use microphone other than to communicate within the game but You will...
and overall i did not have such severe issues on live build, althought i was not at MS / TBC yet tho
shader compilation lasts as long as the icon / indicator is on the screen
you can also tell that shaders are compiling by cpu utilization going to 100%
i will give the game today another spin with freshly restarted system
but if you don't see the same stuttering in the live environment its definitively something that needs to be looked into
but i had such issues also on preview / experimental and live - just not that severe, now i can't basically play at bigegr poi's - can at fn tho...
overall performance seems better to me now (both regular and experimental), compared to 0.2 and especially compared to 0.1
POIs like TB still make my PC suffer but no worse than before
Ryzen 7 5700 RX7800XT 32gb ddr4
yes it's 'better' when it's not stuttering and introducing input lag
or here, it starts after opening inventory https://www.youtube.com/live/3blRj0lX7To?feature=shared&t=3938
but here comes the funny part, i was able to 'fix' it temporary by droping weapon on the ground https://www.youtube.com/live/3blRj0lX7To?feature=shared&t=3938
but only till reloading main https://www.youtube.com/live/3blRj0lX7To?feature=shared&t=3963
so yea, something is fundamentally broken
same results every time you do the same steps?
out of curiosity, any of the tactical devices turned on, IR or something ?
Basically is the game "rendering" a laser beam interacting with the enviornment and we don't see it ?
yeah, maybe some other interaction with the rifle - ADS, tac device, cant....
even if you do same steps but with dropping the handgun instead of rifle? (in case its specific item or item type related for whatever reason)
with and without, random - only common is that it happens near or within the big poi's imho
you might have not clicked around my youtube channel but i basically stream or record every GZW session and i do have PC to run it - so it's a thing specific to some settings or hw setup - that means when i'm making a ticket i've noticved some change / regression
well you have certainly did not click any of the videos description since there is a hw listed there 😉
i was somehow able to "break" nvidia reflex by changing presets from all maxed to all low, at some point the reflex setting was just gone
the shader compilation process [first boot and menu screen] in current prod build takes MUCH LONGER [experimental like a minute and prod takes five] than in the experimental build
i don't even understand what's happening there https://www.youtube.com/live/Kvti9117nEw?feature=shared&t=416 those are 'lowest possible settings' and just by standing i have fps fluctuation from ~118 to ~82
rolled back drivers to 576.28-desktop-win10-win11-64bit-international-dch-whql still no luck
ok scratch that i guess - driver rollback is the way to go
576.28
and 576.52 on all low
well should be with nods on but still you can see the fps difference
SOLUTION: downgrade NVIDIA Drivers to 576.28-desktop-win10-win11-64bit-international-dch-whql
ok nvm issue is back :DDDDD
came back to same space after game crash when restarting it https://discord.com/channels/1166365362158313522/1377328980440518746 and it is ok for long time already
I'm running on a RTX 3070 + Ryzen 7 5800x undervolted + 32GB RAM@3466MT/s + Medium Preset. On the live server I get some relatively random crashes after 30m to 1h of gameplay. Specially when returning to base via helicopter.
0.3.1.0 is much more stable on my end. But I also notice a small performance reduction, I think I went from 90fps to 80fps on average. I have not checked Tiger Bay, so I'll take a look how it goes, but so far no input lag or stutter.
Both Live and 0.3.1.0 have this strange black flickering, like UE5 is trying to regenerate the world lighting, looks like blinking to be honest.
somehow i dont know how i've fixed it doing many things like rolling back and instaling latest, verification and compiling shaders multiple times durring that
but there is some small imput delay added
performance on 0.3.1.0 is bad [solved?] - noticeably increased input delay
there is somehtign wierd going on with this game 😄
this screenshots were taken 80 seconds apart
first
than
there are some wierd stutters at random moments https://www.youtube.com/live/vSQrUZP35qE?feature=shared&t=5874
HMMMM I legit did not see any stutter, could be just me to be honest... but it is pretty interesting how the load is handled when you open menus.
look at the graph
last version that played ok for me was 0.3.0.1
performance on 0.3.1.0 is bad [solved?] - noticeably increased input delay - possibly 0.3.0.3 too
it feels like game is not utilizing all resources as it usually did with some 'process' running in the engine in the background constantly limiting it from performing at max hardware specs
since that's the performance i get at doom the dark ages on all settings maxed and with dlaa i don't think that's my pc issue 🙂
yep, all looks the same on my end and keeps happening on 0.3.1
@dire flare i think my game is not using dlss4 😉
at that time it was in tiger bay, 16gb card, still uses shared memory, the higher the shared memory usage, the higher the fps drop
but the vram used by the process was nowhere near maxed out
so it should be just allocation for later rather than actively needing it
so in the end the more I check the parameters while running there the less I understand whats going on xD
set both textures and effects detail to low, restarted the game and went to tiger bay
the VRAM usage didnt go above 8gb, RAM usage didnt go above 27gb (so much less than 32gb)
the frames still dropped from 160 to 80
same i have with dlss
turn variable rate shading completely off in game settings, re-compile all shaders, keep the setting off and go to TBC / MSH and test. It appears to have fixed it for me and GPU usage stays high at 90-95% and fps are high and stable.
will do that scenario
Yeah can agree with this 1000% game was running way better on previous hotfix. Getting terrible fps drops, stutter imput delays. Feels like the servers again. I'm in Oceania. Ngl I hadn't been able to play the game at all for the first week, get that last patch, all fixed and running fine, the next day they drop this latest patch, game runs like poo intermittently. So bloody annoying. Roll back to last hotfix. Pls pls pls🙏
yes that could be server side issue as well
i got stutter still when getting close to tb from juliet to side
even vorse at ybl for some reason
and few minutes ago it looked ok
might be multiple things goin on at the same time then
couz on my end for TB atleast that variable rate shading deffo did something as I went from ~80 fps back to 120-140 when inside TBC but some stutter might be still present but I wrote if off as new stuff loading in as it was usually the case in 0.2, will pay attention to it once Im in YBL