From f679592add7210b73d1740eb2bf6f430cb671be9 Mon Sep 17 00:00:00 2001
From: Amit Prakash <amit.prakash@amd.com>
Date: Wed, 15 May 2019 13:48:45 -0400
Subject: [PATCH] Fix incorrect loop over counters

* This issue was causing additional entries to counter result data
leading to incorrect display in the perfcounter viewer.
---
 renderdoc/driver/d3d12/d3d12_counters.cpp | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/renderdoc/driver/d3d12/d3d12_counters.cpp b/renderdoc/driver/d3d12/d3d12_counters.cpp
index 41cfa0f10..254a7accd 100644
--- a/renderdoc/driver/d3d12/d3d12_counters.cpp
+++ b/renderdoc/driver/d3d12/d3d12_counters.cpp
@@ -628,14 +628,14 @@ vector<CounterResult> D3D12Replay::FetchCounters(const vector<GPUCounter> &count
       occlusion++;
     }
 
-    for(size_t c = 0; c < counters.size(); c++)
+    for(size_t c = 0; c < d3dCounters.size(); c++)
     {
       CounterResult result;
 
       result.eventId = cb.m_Results[i].first;
-      result.counter = counters[c];
+      result.counter = d3dCounters[c];
 
-      switch(counters[c])
+      switch(d3dCounters[c])
       {
         case GPUCounter::EventGPUDuration:
         {