Forums » Bugs

Freeze and screen corruption.

Jan 16, 2016 abortretryfail link
This happened right after exploding in Sedina D-2 and respawning in D-14.

Linux 4.4.0
Renderer: Gallium 0.4 on AMD BARTS (DRM 2.43.0, LLVM 3.9.0)
Version: 3.0 Mesa 11.2.0-devel (git-e976860)

Jan 16, 2016 abortretryfail link
It keeps doing this every time I respawn in Sedina D-14.
Jan 16, 2016 abortretryfail link
Re-homed at Sedina L-2 and it doesn't happen. Must be something up with D-14.
Jan 16, 2016 lazypc link
I am also having this problem on a WIndows 10 machine with a AMD FX-something processor, AMD R9 280 and 8 GB of RAM
Jan 16, 2016 lazypc link
To further expand I can confirm this happens to me in Sedina D-14 but not L-2, also, if I turn off multithreaded via the config.ini I don't have any problems. This testing was done with no addons of course.
Jan 16, 2016 raybondo link
You're both having the screen clipped off and offset like that?
What VO video driver settings are you both using? I am unable to replicate the problem on my linux VM with GL Reference and GL4 drivers with multithreaded=1
Jan 17, 2016 lazypc link
Each crash is a little different, I have had the offset screen clip a couple times, once with the logo and once just a part of the background, more often I just get stuck at a loading screen, once it finally loaded after 5-8 minutes, most of the time I just force close it.

But I am on a windows 10 system with the DX 11 driver.
Jan 17, 2016 abortretryfail link
It clipped the loading screen and hung there like that every time i died and respawned in Sedina D-14. The screen it froze on wasn't always exactly the same, but it was some combination of black and a chuunk of the loading screen and chat window.

It's worth noting that every time it happened,, i had the chat box open typing after dying.

Linux 64bit GL4 with multithread on.
Jan 17, 2016 jordanmorgan14f link
Same here, except it freezes at the loading screen and I have to kill VO and restart
Jan 17, 2016 raybondo link
New client patch 1.8.367.3 is released that should fix the problem. The bug was related to shadows and multi-threaded rendering.