pwnSource is where players and developers come together
This website is updated regularly. Features here are under construction and will constantly be improving.
Please share your Feedback with us and the Community, or you can Contact Us privately
Counter-Strike: Global Offensive
Crossfire and SLI not working since previous update
Ticket Status Category Type Severity Version Created
1610 Open Matchmaking Defect Blocks Playability 2013-08-21 23:26:12
Ticket Priority
  • 35
  • 1
  • 0

Written By king 256 Hits Last Updated 2013-10-02 01:11:22

Steps to Reproduce the Problem:
1. turn on sli or crossfire
2. open game
3. check fps with and without crossfire or SLI enabled

Expected or Desired Behavior: Before the latest update, SLI or crossfire would give a big boost in fps. After the update, having it enabled drops performance/fps by more then 50%.

Additional Relevant Information that could be helpful to address this issue:
(Examples: Operating System, Processor, Video Card.): Any nvidia or AMD card in SLI/crossfire

you moderate pwnSource tickets

The Community maintains the accuracy and quality of ticket information.
Please update tickets as things change, keep pwnSource up to date and organized!

DISCUSSION: debate game mechanics, balance, etc.

QUESTION & ANSWER HELP EXCHANGE: ask great questions, get great answers

FEATURE REQUESTS: propose your own ideas and solutions

DEFECT REPORT: alert developers of specific issues

OPEN: this is the default status when a ticket is created

IN PROGRESS: when Developers acknlowedge the issue, or power users propose solutions

VERIFYING: a solution has been found, and needs to be confirmed by other users

CLOSED: the ticket has reached its end of life

DUPLICATE: there is a better written version of this ticket

UNCLEAR: this ticket has insufficient detail

LOW, WISHLIST Tickets do not impact the gameplay directly

POOR EXPERIENCE Tickets are used to describe the quality of the gameplay

BLOCKS GAMEPLAY Tickets describe conditions that render the game unplayable

Comment
Ticket Changes
Comment Popularity, Appreciation, and Reputation
User Appreciation and Reputation
    • 1
    • 0
    • 0
      • c0de
      • 1
      • 0
    confirmed. I was running two HD Radeon 6670's in a Crossfire-X setup and only getting around 100 FPS on some maps (if I was lucky), where I normally had around 200 to 240 stable FPS.

    Disabling one card gave me a bump in performance, but nowhere near the performance I had with two cards pre-update
    • 0
    • 0
    • 0
      • jzderf
      • 0
      • 0
    I set my fps_max to 60 due to monitor issues. I'm running 2 ATI 5670s in Crossfire. Was (obviously) able to be rock solid at 60 always before. After Arms Deal, was instantly at about 25fps. Disable crossfire (only change I made) instantly fixed the issue.
    • 0
    • 0
    • 0
      • oktnxbai
      • 0
      • 0
    I have nVidia GT650M SLI and pre-Arms Deal patch I used to get 200~250 FPS.

    After Arms Deal, 50~100 FPS. Disabling one card will result to 120~150.

    After 8/22 patch, notes said to try 326.80 drivers. I installed it and re-enabled SLI, no improvement at all.
    • 0
    • 0
    • 0
      • enzor
      • 0
      • 0
    I'm using 2x6870s and I went from around 200 fps pre-arms deal to 50-70fps after. Disabling crossfire nets me around 120 fps but the one GPU runs at around 80C. Before the update both cards maxed around 65C so it was much quieter.
    • 0
    • 0
    • 0
      • fallschirmjager
      • 0
      • 0
    Problem is very severe in my opinion, blocking playability, as I've been running two 5850's that at near max settings (8x/16xAA @1080, win7-64bit, 8g DDR3, Intel QuadCore) gain ~300fps generally stable. Since the patch I'm operating around 60-70 fps with drops to 30-45, that's not playable.

    I've tried a few things, in the AMD catalyst suite, as mentioned only disabling Crossfire shows any noticeable change. Presuming these settings are working as intended, one card is running the game in the area of 150-230 fps.
    • 0
    • 0
    • 0
      • godsmack
      • 0
      • 0
    Same problem here.