Rust

Rust Dev Tracker




09 Sep

Comment

Originally posted by JellyfishRave

[QoL] (sort of) Massive fps hit (~30) when taking out a torch in the dark. High hardware usage, which makes recording extremely difficult. Old settings that used to be able to record at 48-60fps max out the encoder instantly (cpu and gpu), and much much lower settings still have stuttering issues in the output video. Hitting trees tends to cause a moderate stutter (possibly related to the xs). FPS is WAY up across the board though without recording/torches. Seems like a promising update!

We just released an update to address this issue. Please give it a try.

Comment

Originally posted by amayze010

I own a R9 290 4GB and used to play with 100 FPS, now since the new ''Performance update'' I get really bad FPS while pvping, or even lighting a bloody Torch I get 15 fps.. what the heck.. please fix this as I cannot play the game anymore.

We just released an update to address this issue. Please give it a try.

Comment

Originally posted by Naga22

[BUG]PC: I7 6700k R9390 16 gigs of ddr4. After the new patch when a torch is out, or even on around me/inside someones base, my fps tanks to around half. Usually at 100 fps then it drops to 50

We just released an update to address this issue. Please give it a try.

Comment

Originally posted by makatic

[BUG] before the update i had stable 90fps (fps limit) with drops to 70 min which werent even noticable and was having no performance issues at all, now just turning on the torch makes me go from 90 to 50, when the night comes(combined with lights) its even worse(around 30fps), when somebody shoots at me it drops as well, its just unplayable for me since the update, doesnt feel smooth at all, i have win 10 64bit, i5 6600k OCed to 4.1ghz, 16gb 3000mhz ram, r9 390 8gb (i already updated driver, which didnt help), 240gb intel ssd with 40gb free space, i tried disabling all the setting and turning everything as low as it goes but nothing helps, i noticed somebody else with r9 series amd gpu had the same issue

We just released an update to address this issue. Please give it a try.