instant swap problems

RSM72 · Post by **RSM72** » Wed Jan 12, 2011 4:28 am

Did you update anything on build 5326 two days ago (monday 10.01.) because that day the 5326 build started giving me graphics errors as described above in crowed areas, no #132 crashes yet. I noticed that gfx card memory usage has gone up in those areas. Turning vsync off and on again for the affected client seems to fix it.

I tries rolling forward to 5354 but that seems to make it worse (problems starting after fewer character switches)

Post by **Lax** » Wed Jan 12, 2011 11:03 am

Build 5326 is build 5326, any changes I make go into the dev build not the live build. In other words there have been zero changes to 5326, it is identical to what it was the day before you started having new problems.

Your issues all point to a problem with your video card, I would try replacing it with another one if drivers don't help.

mastrrob · Post by **mastrrob** » Wed Jan 12, 2011 4:28 pm

I am very new to IS, so i dont know how much help i can be...

I was getting the same symptoms last night while 5 boxing EQ1. 3 out of 5 of my sessions would switch fine to the main window, but my last 2 sessions would switch to the main session but they were a solid image only running at 25%.

The two "frozen" sessions would still accept broadcast keystrokes, but would never refresh from the stuck image.

Im using dual monitor setup with 1 fullscreen client for the main, and the other 4 clients are all 25% usage on screen 2.

RSM72 · Post by **RSM72** » Wed Jan 12, 2011 4:45 pm

Thats weird. Last thing I changed on the system was upgrading the video driver but that was 5 days befre the problems started. Will be downgrading to the driver I used before and see if that helps. I already replaced the video card, I can reproduce the problems with IS dev builds with my current gtx 580 and two different gtx 480s which all work fine in other games.

Going to try replacing my RAM next if the older driver wont fix it.

Post by **Lax** » Wed Jan 12, 2011 7:02 pm

mastrrob wrote:I am very new to IS, so i dont know how much help i can be...

I was getting the same symptoms last night while 5 boxing EQ1. 3 out of 5 of my sessions would switch fine to the main window, but my last 2 sessions would switch to the main session but they were a solid image only running at 25%.

The two "frozen" sessions would still accept broadcast keystrokes, but would never refresh from the stuck image.

Im using dual monitor setup with 1 fullscreen client for the main, and the other 4 clients are all 25% usage on screen 2.

That's a different, and EQ1-specific, issue

mastrrob · Post by **mastrrob** » Wed Jan 12, 2011 10:34 pm

Lax wrote:
mastrrob wrote:I am very new to IS, so i dont know how much help i can be...

I was getting the same symptoms last night while 5 boxing EQ1. 3 out of 5 of my sessions would switch fine to the main window, but my last 2 sessions would switch to the main session but they were a solid image only running at 25%.

The two "frozen" sessions would still accept broadcast keystrokes, but would never refresh from the stuck image.

Im using dual monitor setup with 1 fullscreen client for the main, and the other 4 clients are all 25% usage on screen 2.
That's a different, and EQ1-specific, issue

sorry... seemed like it was the same symptoms.

RSM72 · Post by **RSM72** » Fri Jan 14, 2011 7:56 am

Did some further testing with dev builds and discovered something today: setup was IS 5354 and dx9 mode - every time one instance gets "stuck" the first client in the list (first slot) gets hit by heavy interface flickering. Switching vsync off and on removes the flickering and makes the stuck client work again. Sometimes the first slot starts flickering without noticeable problems on other clients. Tried that with several teams and its always the first slot that starts flickering independent of the character in that slot.

RSM72 · Post by **RSM72** » Thu Feb 03, 2011 4:17 am

I replaced the systems memory (went from 6x2 to 3x4 to ease load on the memory controller too) and finally managed to get the 580 replaced by the retailer but that does not solve the problem. Did some testing yesterday with the current dev build 5365 and the "client stuck in still image" effect after swapping clients is still there and it happens alot more in DX11 mode compared to running in DX9. I did not notice other weird graphics problems yet.