Page MenuHomeFeedback Tracker

Massive FPS drop after a short while in the game (experimental 0.54)
Closed, ResolvedPublic

Description

I have a Quad Core i5 and a Geforce 670. I may not have a creme de la creme computer but I never had issues with any previous Day-Z version. I always used to have 25-85 FPS (depending on graphic details, cities etc.) Once trying out the experimental the frames drop and polygons get reduced. Almost like the game is trying to render the whole world (or as if my computer turned in to a peasant console).

I uploaded a video on youtube where you can see the symptoms.
https://www.youtube.com/watch?v=9asTWB1bNqk

Details

Legacy ID
3110333709
Severity
None
Resolution
Duplicate
Reproducibility
Always
Category
Performance
Steps To Reproduce

Start playing the game, within minutes the frames and polygons drop.

Additional Information

Event Timeline

dannodon edited Additional Information. (Show Details)
dannodon set Category to Performance.
dannodon set Reproducibility to Always.
dannodon set Severity to None.
dannodon set Resolution to Duplicate.
dannodon set Legacy ID to 3110333709.May 8 2016, 9:35 PM
Carlo added a subscriber: Carlo.May 8 2016, 9:35 PM
Carlo added a comment.Feb 23 2015, 1:23 PM

Confirmed! I have the exact same problem since EXP 0.54 02/18. Stable 0.53 works fine. I use a FX-6300, R9 270, 8GB Ram, Win7-64bit

Edit: delete the launch options. Worked for me

Same here. Huge FPS drop (from 50 to 7 FPS) and buildings stops rendering. Cache verifying doesn't help (all files validated successfully). 0.53 pdate works fine. I am using AMD R9 280 3GB graphics card, I5 2500k CPU, 8GB RAM, WIN 7 64-bit. All drivers are up to date.

Bohemia added a subscriber: Bohemia.May 8 2016, 9:35 PM

Try removing your launch options. It worked for me.

I will try removing launch options after work. If I have time I may try removing one launch-option setting at the time and see witch one is faulty.

Geez added a comment.Feb 23 2015, 1:42 PM

Thank you for the report dannodon.
We are aware of this issue #0017013 and it has been scheduled for a fix.
Regards,
Geez