Author Topic: problem with shaders (Read 17302 times)

Rally · June 03, 2017, 12:58:25 AM

Ah yes, another reason to append to the ever-growing list of why it was totally worth scrapping maps and interiors

Ad Bot · Advertisement

torin� · June 07, 2017, 04:17:20 AM

have this exact problem rn, worked fine earlier until i updated windows 10

Rolfey95 · June 07, 2017, 05:49:20 AM

Quote from: Rally on June 03, 2017, 12:58:25 AM

-snip-

Ah yes, another reason to append to the ever-growing list of why it was totally worth scrapping maps and interiors

Quote from: torin� on June 07, 2017, 04:17:20 AM

have this exact problem rn, worked fine earlier until i updated windows 10

As far as I know it has nothing to do with windows 10, and in fact has to do with the latest NVIDIA driver/s. It's happened to me and many others, rendering shaders either unusable or usable to only a certain point (this is what happened to me, i can't go higher then minimum).

Currently the only way to resolve it is to downgrade your drivers. There is a really good tutorial on how to do so if you just do a quick search. (Though admittedly it didn't completely fix it as said previously above).

Hope this helps.

Rolfey95 · June 07, 2017, 05:50:30 AM

Also Blockland isn't the only game to be affected, many other games such as Terraria, some other Indi games and a few AAA's have also been affected.

Conan · June 07, 2017, 12:22:18 PM

Quote from: Rally on June 03, 2017, 12:58:25 AM

[img width=400 ]http://i.imgur.com/W3XusfD.png[/img]

Ah yes, another reason to append to the ever-growing list of why it was totally worth scrapping maps and interiors

tbh would blame nvidia more than badspot, for dropping backwards compatibility. you can depreciate functions but totally breaking them is really bad form

Zeblote · June 07, 2017, 12:54:54 PM

We aren't blaming badspot for it breaking, bugs happen. What's unacceptable is not even responding to the bug report after several months.

torin� · June 07, 2017, 12:55:45 PM

Quote from: Rolfey95 on June 07, 2017, 05:49:20 AM

As far as I know it has nothing to do with windows 10, and in fact has to do with the latest NVIDIA driver/s. It's happened to me and many others, rendering shaders either unusable or usable to only a certain point (this is what happened to me, i can't go higher then minimum).

Currently the only way to resolve it is to downgrade your drivers. There is a really good tutorial on how to do so if you just do a quick search. (Though admittedly it didn't completely fix it as said previously above).

Hope this helps.

i checked last night and i wasnt able to roll back, i uninstalled them and restarted. hopefully it works

Rolfey95 · June 07, 2017, 03:40:32 PM

Quote from: torin� on June 07, 2017, 12:55:45 PM

i checked last night and i wasnt able to roll back, i uninstalled them and restarted. hopefully it works

https://m.youtube.com/watch?v=3ulQYC_HP9s

I should've got this link sooner, I hope this is what you did cause doing it wrong can damage your graphics card/GPU.

lilpaladin21 · June 08, 2017, 07:48:21 PM

I am having this exact problem. Going to downgrade.

Blockteen · June 08, 2017, 10:07:23 PM

assuming that these driver dates are correct, and information on the forums, the bad nvidia driver version is 381.65. The version that would make Blockland shaders work again is 378.92. Hopefully I saved some people a lot of time. The attached image was taken on my iPad.

Zeblote · June 09, 2017, 02:38:35 PM

The latest driver, 382.53, has fixed the problem.

phflack · June 09, 2017, 04:20:00 PM

yay we get shadows again
now we can all live in the dark

Blockteen · June 09, 2017, 11:59:54 PM

Quote from: Zeblote on June 09, 2017, 02:38:35 PM

The latest driver, 382.53, has fixed the problem.

damn it, and I've been going through the trouble of doing a clean install of the old version when it worked before April 6th... welp, now I got to install GeForce Experience so I can stay up-to-date

Rolfey95 · June 10, 2017, 03:06:50 AM

Quote from: Zeblote on June 09, 2017, 02:38:35 PM

The latest driver, 382.53, has fixed the problem.

about time

Trogtor · June 10, 2017, 05:01:56 AM

Quote from: Zeblote on June 09, 2017, 02:38:35 PM

The latest driver, 382.53, has fixed the problem.

REJOICE!