c2a3 Poor Performance

gaddeath · November 25, 2018, 2:33am

POSSIBLE SPOILERS

The game’s been performing decent-ish (dips to 30FPS due to V-Sync every now and then like during the ice/fog parts or looking at radiation liquids) and everything was fine at this part of the level until I loaded it up lately to continue.

It’s the part where the assassin/stealth soldiers are first introduced when they kill the guard trying to relay a message. As I approach the hangar area where they’re all at, the game goes from 60, to 30, to 15, to 10 and below as I get near or into the hangar.

A few days before this started happening everything was fine, now recently it’s been acting up like this. I have tried lowering settings, turning off V-Sync and even did the affinity/priority Task Manager fix and it’s not doing anything.

PC Specs:
AMD Phenom II X4 970 BE Stock Clocks
Radeon HD 6870 OC at 930MHz Core Clock
8GB of DDR3 RAM at 1333MHz
2TB total space with HDDs in RAID
Windows 7 64-Bit
Playing on 1920x1080 resolution

lexa2 · November 25, 2018, 2:34am

Please follow the bug reporting guidelines fully and do post the screenshot for the problematic place with a budget panel open. This place is known to be bugged in a way that if you load up a save game placing you into that area you would have a huge FPS dropdown. To workaround you had either to wait staying and doing nothing for quite some time or to backtrack to a previous map and then return back to this place.

It’s hard to tell if you’re hitting this bug of some other without taking a look onto budget panel and without you trying the proposed workaround.

gaddeath · November 25, 2018, 2:34am

Sorry, I skimmed through it and failed to read the budget part. Here are some screenshots with different locations through the area. I’ll also try out the potential fix with re-entering the area.

Georges · November 25, 2018, 2:34am

Please see here to continue the discussion on this bug.

lexa2 · November 25, 2018, 2:34am

Yep, please use bugtracker for posting additional info. And if you read up sticky FAQ you would find a “config file magic” there that would allow you to workaround this bug and get a decent FPS at that place. It’s a yet another instance of the “dynamic lighting hogs CPU like mad” bug which could be workaround by executing “r_dynamic 0; r_dynamiclighting 0;” in console or by simply pressing U key if you use the proposed workaround config fix from FAQ.