Issues, Workarounds & Localization

I have the same problem, whole system locks up when using DX11 and docking at minmatar stations. My system doesn't recover (After 10 mins). R9 280x using driver ver 16.8.2 (latest right now).

Did some tests...

- Using 'medium' shaders works fine.
- Changing 'medium' shaders to 'high' when already inside the station is fine, and you can undock without problems.
- Immediate re-dock locks system up again.
- Timing of lockup varies slightly. Sometimes the fade in had just begun (and things appear to have rendered ok, although still very faded), other times its just a plain black screen, but always happens within 0.5 seconds of mouse pointer changing to initial game pointer.
- No problems in space
- If I log in with char already inside the station it will lockup every time until I change to DX9/DX11 Medium shaders.
- DX9 works whatever settings.


Good luck

o7

Hi folks,

Thanks again for all the feedback, its all been incredibly useful. So we believe we have identified what might be causing the issue with entering a Minmatar hangar and a potential fix for the crash is now on our Singularity server.

In order to ensure that this fix works correctly, I would like to ask those of you who are suffering this crash to attempt to reproduce the issue on Singularity. Again please do let us know if you're still seeing this on Singularity so we can follow up on the fix if needed.

Shipwreck ThunderStar - your crashes appear to be a little different to the one that's only occurring in the Minmatar hangar for AMD users, but the fix on Singularity may correct your problem too. Please do get in touch if you're still getting this though.

My apologies, I was half way through writing a comment to you about this same problem on your thread before being called away from my desk. A work around for now that has reportedly worked for most users is to reduce your shader settings to 'MED'. Hopefully that will allow you to continue playing with no crashes before the fix heads over to Tranquility.

Hmmm. It is probably too early to celebrate, but poking around on Singularity for a while and so far, no crash. Again, I'm on minimum settings. However, to push things, I turned the settings up to almost max, no HDR, Shader at Medium, and so far so good.

Thanks to all who helped diagnose and develop a fix.

(Note: first time on Singularity ... I'll be using it more often now for fitting, etc)

I just wanted to add myself to the list of those having problems with this bug. It initially was only affecting one of my accounts then began affecting this account. I might have had different settings on the other account but am not sure. I usually run with high settings as well.

My video card is an AMD R7 200 series 2GB VRAM. Thankfully, running the clients under DirectX 9 works.

I run 4 clients on 4 monitors windowed mode.

This began as a crash on one client when entering Minmatar hangars. Later the problem affected all clients. Reducing "Interior Effects" to medium seemed to fix this.

After a few days without issues the second problem started. One of the clients would go black for a few seconds then recover. This would happen randomly a few times on different clients ( I couldn't see a pattern to it ) and eventually one or more client would crash. One one occasion it actually crashed the PC to a reboot, and that's unusual on W10. I am also getting a lot of periods of unresponsiveness, eg. when my ship says it is in warp but just sits there for 20 or 30 seconds.

Typical W10 notification for the event is "application exefile.exe has been blocked from accessing graphics hardware"

Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release_inmarket.160819-1924)
AMD Phenom(tm) II X4 955 Processor (4 CPUs), ~3.2GHz
16384MB RAM
DirectX 12
AMD Radeon HD 7800 Series
Driver File Version: 8.17.0010.1474 (English)
Driver Version: 16.300.2511.1001

Been getting this a lot in the Minmatar Stations. AMD R9 200s here.

Just wanted to mention it did happen once coming out of a gate jump as well...in one of the lowsec systems directly between rens and jita iirc (minmatar space?)

Glad it sounds like there is a fix in the works.

Side note question. With support for DX9 on the chopping block eventually/soon, what will be used as a viable workaround to some issues that, to date, have used the 'switch to DX9' workaround? As they've been a combination of crash, socket closed, game client freezing types of problems at times, what fallback will we have once DX9 gets the big CCP boot outta here??

>Mikk

Oh wow, I was just browsing the forums because I am in the process of reinstalling the game because I thought that might fix it... then I see that its not just me.

my setup:
R9 270 2GB
Win 10

When it starts to blink the black screen the thing I've done that has worked 4/5 times to keep the game playing has been to click once every few seconds and every other second click and drag the mouse a tiny bit. Like click and drag a centimeter or two. Sometimes it pops back and plays like normal until next time I decide to enter the station.
If it does not then use CTRL SHIFT ESC to bring up the task manager and end the task and restart game.


This might be useful info:
I've found was that it does NOT happen while I'm flying my Procurer mining ship but it does on my Vexor and VNI and a couple other ships.

Found this thread on google.

I have AMD gpu and crash at minmatar station on "quality optimization" setting. I have to go to performance if I don't want to crash.