Getting a disco effect with anger mtx using 64-bit client, just standing in hideout. Started happening randomly, then disappeared when i switched to another zone. Didn't take a screenshot, but it looks similar to other posts in this thread.
|
Posted byBorgese#0974on Nov 25, 2016, 11:28:38 AM
|
"
Insomnius85 wrote:
"
Harest wrote:
Edit² : No issue so far with --noasync (several hours played since).
I tried this out as well. I encountered a puppet master ;)
However, I did not have the time to do a long test in order to see if it got better or anything changed.
Damn, i hoped it could fix the problem for more people than just me. Sorry to hear that.
|
Posted byHarest#1598on Nov 25, 2016, 3:37:53 PM
|
Same thing to me, amd radeon r9 390 series.
EDIT: dx11 version only
Last edited by j0hansson#7804 on Nov 25, 2016, 4:45:58 PM
|
Posted byj0hansson#7804on Nov 25, 2016, 4:45:27 PM
|
DX11 x64 version
Same problem. It looks like a slowly progressing memory corruption. For example 1 - 4 hours, game works without glitches. And then after few hours, I see some small random artefacts on maps (or in my own hideout), it maybe light sources, or some shader effects on monsters, or even 3d model of main character becomes a big problem. All glitches so random, and in rare cases, game almost unplayable, because all visible screen, I see as big mess of blinking polygons.
Conf:
CPU: Core i7 3770k
RAM: 4x AMD memory (16GB total)
Mboard: Asus P8Z77-V Pro
GPU: Radeon HD6950 1GB
Windows 7 x64 (Pro)
DX9 works without gfx glitches.
|
|
I knew someone that got the same issue and i told him to try to add the launch parameter --noasync (cf. my previous posts). It works for him too.
So if more people with the issue could try it. The main drawback you'll have with it is that loadings will take more time so until it's fixed, it depends on what you prefer (aka slower loadings vs glitches) if this works for you and fix these textures glitches.
Last edited by Harest#1598 on Nov 27, 2016, 9:14:15 PM
|
Posted byHarest#1598on Nov 27, 2016, 6:42:44 PM
|
Same problem here, but only AFTER THE LATEST 2.4.3c Patch !!
Frequent artifacts and my Amd 7870 rises to 70 degrees Celsius whereas in other games it's at about 50 degrees!
"Wealth in a game is measured by the amount of fun, joy and entertainment you can get out of it".
-Mythabril
|
Posted byEKTELESTES#1444on Nov 28, 2016, 7:21:30 PM
|
Following the update today, I'm also seeing artifacts when using the 64bit client.
I've been trying to recreate these oddities when using the 32 bit client, so far, unsuccessfully. By way of contrast, this issue manifests quite quickly when using the DX11 client.
Windows x64 - patched including platform update for DX11.1
AMD FX8320
AMD HD7870 - 16.11.4 drivers
From what I can see, it seems to be mostly Windows 7/AMD related?
|
Posted byKellog#5737on Nov 29, 2016, 9:41:48 AM
|
Just a little update : I've sent a pm to everyone who posted a message here (since it's hard to see answers to a thread on the forum) to see if --noasync could solve your issue.
Not many reports yet, but some said the patch 2.4.3c seemed to solve the issue for them.
For me, it doesn't so i'll stick to the --noasync despite longer loadings.
I just tried with --noasync deactivated and this is what i got in the first map i entered, Bog (because this map seems to be the perfect test considering how fast you can have this issue). This is the result :
|
Posted byHarest#1598on Nov 30, 2016, 12:40:02 PM
|
Well, I'm still seeing this bug in the latest version of the game. It comes and goes, ranging from a stray randomly colored ray to a full-blown purple (or other color) screen where you can't see anything. Leaving and re-entering the area seems to help so far.
|
Posted byBorgese#0974on Dec 1, 2016, 5:39:15 AM
|
Reporting back, I see less of this with the 2.4.3c, but it still happens.
Using --noasync seems to have fixed it, so that might be what people should try.
I personally get text corruption using --noasync though, so not optimal.
|
Posted byHeff#2778on Dec 1, 2016, 7:33:46 AM
|