Page MenuHomeFeedback Tracker

Renderer stroke and massive fps drop - Experimental -
Closed, ResolvedPublic

Description

Downloaded Exp 0.54 (23.02.2015) to check it out, Hoping to have some fun and test the changes, played for about 10min with no issues untill everything went full potato on the screen, massive drop of fps, Lara Crofts style of polygones on everything, insides of buildings wont show, textures gone to pixel-land and so on.

The problem solves for a limited period of time ranging from 10-20min if i change the render resolution, Vsync or so. Not to mention closing and opening back the game.

  • No other programs running on background -

Details

Legacy ID
3794029121
Severity
None
Resolution
Duplicate
Reproducibility
Always
Category
General
Steps To Reproduce
  • Go in experimental server
  • Play normally for a period of time superior to 10min.
  • Character and surroundings goes full polygon, like the first generation of 3D games; And massive drop of fps.

Event Timeline

BrainlessZombie set Category to General.
BrainlessZombie set Reproducibility to Always.
BrainlessZombie set Severity to None.
BrainlessZombie set Resolution to Duplicate.
BrainlessZombie set Legacy ID to 3794029121.May 8 2016, 9:35 PM
Bohemia added a subscriber: Carlo.Feb 23 2015, 12:17 AM

Check your launch options, clearing mine out fix it, not sure which one was to blame... See 0021812

Lorax added a subscriber: Lorax.May 8 2016, 9:35 PM
Lorax added a comment.Feb 23 2015, 5:44 AM

Same thing happens to me, even changing video settings will clear it up for a few secs to only have it drop again. I deleted all launch options and it solved it. I too haven't determine which launch option it was.

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

Same here. For me it looks like this:
http://abload.de/img/2iqors.jpg

Also I only get 1 or MAX 2 FPS for about a minute.

The game reloads all textures since this 1.4MB update.

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

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