search

misyltoad / d9vk

A Direct3D9 to Vulkan layer using the DXVK backend. [Upstreamed to DXVK]
https://github.com/doitsujin/dxvk
zlib License
833 stars 42 forks source link

GuildWars 2 Black Screen & Crash #21

Closed ronoverdrive closed 5 years ago

ronoverdrive commented 5 years ago

On Windows 10 the 64bit client gets stuck on a black screen while on WINE it gets to the character select screen and crashes. The 32bit client was not tested.

Software information

GuildWars 2 64-bit client

System information

Apitrace file(s)

Log files

Dante4 commented 5 years ago

Per the README:

As you could notice it sais "No support for Windows drivers", so why did you linked it? And here i thought ppl can read before link something...

misyltoad commented 5 years ago

Upstream may not care about supporting Windows building/drivers -- but I do.

Either way, the recommended driver version for Linux is at least going to apply to Windows too for obvious reasons.

GloriousEggroll commented 5 years ago

Per the README:

As you could notice it sais "No support for Windows drivers", so why did you linked it? And here i thought ppl can read before link something...

If you were capable of reading you would've seen "No support for Windows drivers" before even posting, and it would not have taken someone telling you FOUR TIMES to update your drivers before actually getting something unsupported to even work.

But hey, please by all means keep shitposting. Even though "Unsupported. Any issues that are exclusive to Windows will be ignored."

I guess you can't read that either. Dipshit.

I'm so tired of stupid people with pompous fucking attitudes thinking they are entitled to the fucking world for nothing.

-You come in, and make a bug report on an issue that is unsupported, before reading any of the documentation -You then get an attitude with ME when I report what is properly working, on a properly supported setup -You then make assumptions about what is known on the bug report vs what you found on reddit. -You then complain about drivers, which you would have already seen in the documentation is unsupported for windows, had you read it -You then argue with the developer instead of updating your drivers after being told FOUR fucking times -You then claim there is no documentation on drivers, which as mentioned, already existed, and would have immediately told you your use case was unsupported. -You then call me an idiot because I linked said documentation that you should have read in the first place that would have avoided this whole stupid conversation. Yes, I called you an idiot first, because you gave me a smart ass sarcastic attitude when I NICELY reported what was working and gave you the documentation you thought did not exist.

"Here's my special use case that's unsupported, your documentation should have explicit wording just for me because I'm an idiot that can't fucking read and will probably ignore the documentation anyway."

You might want to rethink your attitude and the way you approach things, because you definitely fucked up this one.