It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
No Man's SkyPatch 1.08(32 posts)(32 posts)
(32 posts)
Pages:
1
2
3
This is my favourite topic
Posted September 06, 2016
avatar
Wishbone: Here's a suggestion for the offline installers: Make them delete the contents of the SHADERCACHE folder. The last patch broke the game for me completely due to the fact that some of the new code was apparently incompatible with the shaders generated by the old code. The game crashed immediately, even before anything was shown on the screen. Fortunately I knew enough to just delete all the files in that folder and let the game regenerate them on its own, but I do think it is too much to expect all your customers to know that, and to have to do that every time a patch is released for that matter.
avatar
Socratatus: I did not have this issue.
Congratulations. I did.
avatar
Wishbone: Here's a suggestion for the offline installers: Make them delete the contents of the SHADERCACHE folder. The last patch broke the game for me completely due to the fact that some of the new code was apparently incompatible with the shaders generated by the old code. The game crashed immediately, even before anything was shown on the screen. Fortunately I knew enough to just delete all the files in that folder and let the game regenerate them on its own, but I do think it is too much to expect all your customers to know that, and to have to do that every time a patch is released for that matter.
avatar
JudasIscariot: That is ...odd. The reason I say that is because I've updated the game on my home install and nothing ever broke for me. Perhaps there was some corruption on your system in the cache directory? Not saying there was but I am just guessing as we have not heard of anything like this either via Support or our own tests in our QA lab.
It happened with the first offline patch as well, as far as I recall. I have seen others mention the same issue, which is how I knew to just delete the shadercache. I have no mods installed by the way, which is another thing I've seen mentioned which could cause the same problem.
avatar
JudasIscariot: edit: did you by any chance ever use Galaxy but then decided to update the game via one of our offline patches?
Nope. I've never even had Galaxy installed on my system.
Post edited September 06, 2016 by Wishbone
Posted September 06, 2016
avatar
Socratatus: I did not have this issue.
avatar
Wishbone: Congratulations. I did.
avatar
JudasIscariot: That is ...odd. The reason I say that is because I've updated the game on my home install and nothing ever broke for me. Perhaps there was some corruption on your system in the cache directory? Not saying there was but I am just guessing as we have not heard of anything like this either via Support or our own tests in our QA lab.
avatar
Wishbone: It happened with the first offline patch as well, as far as I recall. I have seen others mention the same issue, which is how I knew to just delete the shadercache. I have no mods installed by the way, which is another thing I've seen mentioned which could cause the same problem.
avatar
JudasIscariot: edit: did you by any chance ever use Galaxy but then decided to update the game via one of our offline patches?
avatar
Wishbone: Nope. I've never even had Galaxy installed on my system.
I've talked to our QA and they've never had to delete the shader cache directory, I've installed the game via Wine, both offline and using Galaxy, and I never had to delete the shader cache directory.

The only things I can think of may be either a driver issue as in the game somehow might use your graphics driver when generating the shader cache (just a guess) or there may be some other corruption going on maybe something on your disk? In any case, the next time we get a full update to NMS, we'll try to reproduce the issue, if possible.

Could I at least get some basic hardware/driver information from you such as what card you have and what driver version?
Posted September 06, 2016
avatar
Socratatus: I did not have this issue.
avatar
Wishbone: Congratulations. I did.
I`m just balancing the situation. It`s a fact. Sorry if it upsets you.
Posted September 06, 2016
avatar
JudasIscariot: I've talked to our QA and they've never had to delete the shader cache directory, I've installed the game via Wine, both offline and using Galaxy, and I never had to delete the shader cache directory.

The only things I can think of may be either a driver issue as in the game somehow might use your graphics driver when generating the shader cache (just a guess) or there may be some other corruption going on maybe something on your disk? In any case, the next time we get a full update to NMS, we'll try to reproduce the issue, if possible.

Could I at least get some basic hardware/driver information from you such as what card you have and what driver version?
Sure. What do you want? A DxDiag?

Edit: Mind you, it is just a suggestion. It's an easy fix for me, so the suggestion is more in the nature of saving you some unnecessary support cases from other customers.
avatar
JudasIscariot: That is ...odd. The reason I say that is because I've updated the game on my home install and nothing ever broke for me. Perhaps there was some corruption on your system in the cache directory? Not saying there was but I am just guessing as we have not heard of anything like this either via Support or our own tests in our QA lab.
Actually, Hello Games alluded to a similar issue in the patch notes to 1.04:
Framerate was initially stuttering due to shaders not being correctly cached by the GPU on some systems. We have replaced the GPU caching system. You may notice some stutter during the Galactic Map intro to the game (the very first time you run), but it should be smoother from then on. This is particularly true on ATI cards.
As I interpret that, Patch 1.04 did delete the shadercache, which is why the game might stutter during the intro while it was rebuilding the shaders.
Post edited September 06, 2016 by Wishbone
Posted September 06, 2016
avatar
JudasIscariot: I've talked to our QA and they've never had to delete the shader cache directory, I've installed the game via Wine, both offline and using Galaxy, and I never had to delete the shader cache directory.

The only things I can think of may be either a driver issue as in the game somehow might use your graphics driver when generating the shader cache (just a guess) or there may be some other corruption going on maybe something on your disk? In any case, the next time we get a full update to NMS, we'll try to reproduce the issue, if possible.

Could I at least get some basic hardware/driver information from you such as what card you have and what driver version?
avatar
Wishbone: Sure. What do you want? A DxDiag?

Edit: Mind you, it is just a suggestion. It's an easy fix for me, so the suggestion is more in the nature of saving you some unnecessary support cases from other customers.
avatar
JudasIscariot: That is ...odd. The reason I say that is because I've updated the game on my home install and nothing ever broke for me. Perhaps there was some corruption on your system in the cache directory? Not saying there was but I am just guessing as we have not heard of anything like this either via Support or our own tests in our QA lab.
avatar
Wishbone: Actually, Hello Games alluded to a similar issue in the patch notes to 1.04:

Framerate was initially stuttering due to shaders not being correctly cached by the GPU on some systems. We have replaced the GPU caching system. You may notice some stutter during the Galactic Map intro to the game (the very first time you run), but it should be smoother from then on. This is particularly true on ATI cards.
avatar
Wishbone: As I interpret that, Patch 1.04 did delete the shadercache, which is why the game might stutter during the intro while it was rebuilding the shaders.
No DxDiag needed, just the model of video card you have and the driver version for it :)

As for the patch 1.04 log, all I see is that the shader caching system was changed but I see no mention of the shader cache files being deleted. Only going by the fact that the word "deleted" is nowhere in your quoted post , not trying to be obtuse or anything :)
Posted September 06, 2016
avatar
JudasIscariot: As for the patch 1.04 log, all I see is that the shader caching system was changed but I see no mention of the shader cache files being deleted. Only going by the fact that the word "deleted" is nowhere in your quoted post , not trying to be obtuse or anything :)
Given that they specifically said the game might stutter the very first time it was run after patching, and not after that, I'm guessing (but I do think it is a very good guess) that the patch simply deleted the cached shaders, since the game has a built-in mechanism to rebuild the shaders if they are missing for whatever reason. Alternatively, they would have to have put code into the game to check whether the existing shaders were built by an older version, which would be a bit silly, since that would then run every time the game started from then on, even though it would only actually be used the first time.

Edit:
Oh, and here are the (possibly) relevant highlights from the DxDiag I did just now:

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.160408-2045)
Processor: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 8192MB RAM
DirectX Version: DirectX 11
Card name: NVIDIA GeForce GTX 760
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 21.21.0013.7254 (English)
Driver Version: 21.21.13.7254
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 8/11/2016 16:31:06, 17462904 bytes
Post edited September 06, 2016 by Wishbone
Posted September 06, 2016
avatar
JudasIscariot: As for the patch 1.04 log, all I see is that the shader caching system was changed but I see no mention of the shader cache files being deleted. Only going by the fact that the word "deleted" is nowhere in your quoted post , not trying to be obtuse or anything :)
avatar
Wishbone: Given that they specifically said the game might stutter the very first time it was run after patching, and not after that, I'm guessing (but I do think it is a very good guess) that the patch simply deleted the cached shaders, since the game has a built-in mechanism to rebuild the shaders if they are missing for whatever reason. Alternatively, they would have to have put code into the game to check whether the existing shaders were built by an older version, which would be a bit silly, since that would then run every time the game started from then on, even though it would only actually be used the first time.

Edit:
Oh, and here are the (possibly) relevant highlights from the DxDiag I did just now:

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.160408-2045)
Processor: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 8192MB RAM
DirectX Version: DirectX 11
Card name: NVIDIA GeForce GTX 760
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 21.21.0013.7254 (English)
Driver Version: 21.21.13.7254
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 8/11/2016 16:31:06, 17462904 bytes
Well, the only thing I can suggest at this point based on your driver date is try the 372.20 drivers that came out on August 30th.
Posted September 06, 2016
avatar
JudasIscariot: Well, the only thing I can suggest at this point based on your driver date is try the 372.20 drivers that came out on August 30th.
Again, I have no problem anymore, I fixed it, so you don't need to suggest anything ;-)

And I specifically skipped 372 because several people reported that it severely degraded the performance of NMS, and they had to roll back to the previous release to fix it.
Posted September 06, 2016
avatar
JudasIscariot: Well, the only thing I can suggest at this point based on your driver date is try the 372.20 drivers that came out on August 30th.
avatar
Wishbone: Again, I have no problem anymore, I fixed it, so you don't need to suggest anything ;-)

And I specifically skipped 372 because several people reported that it severely degraded the performance of NMS, and they had to roll back to the previous release to fix it.
OK, understandable. The only reason I mentioned anything is because your drivers are from before NMS released and I thought having drivers after the release of NMS would help.
Posted September 06, 2016
quick relevant question. do any of the graphics settings effect the shadercache content? i guess i am also asking what is the shadercache content and how does it work?
Posted September 06, 2016
avatar
Wishbone: Again, I have no problem anymore, I fixed it, so you don't need to suggest anything ;-)

And I specifically skipped 372 because several people reported that it severely degraded the performance of NMS, and they had to roll back to the previous release to fix it.
avatar
JudasIscariot: OK, understandable. The only reason I mentioned anything is because your drivers are from before NMS released and I thought having drivers after the release of NMS would help.
Hmm, they shouldn't be. NVidia released a new driver right after NMS released with specific performance optimizations for NMS, and I did install that.

Okay, I just checked and it's really weird. DxDiag reports a different driver date than GeForce Experience. According to GeForce Experience, I have got the driver with the NMS specific optimizations (372.54), but it's dated 2016-08-15 while DxDiag dates it as 2016-08-11.
Attachments:
geforcedriver.png (98 Kb)
Posted September 06, 2016
And THAT`S why I mentioned I didn`t have a problem, so that you might consider that the issue might be something other than what you were so certain of. But no, instead you had to get offended.
Post edited September 06, 2016 by Socratatus
Posted September 06, 2016
avatar
Socratatus: And THAT`S why I mentioned I didn`t have a problem, so that you might consider that the issue might be something other than what you were so certain of. But no, instead you had to get offended.
Nooo, that's not quite it, is it? I said the last patch broke the game for me, didn't I? Yes I did. And it did. Presumably for the reason I stated at the beginning, so I have no idea what you're being pissy about now. Then you decided to jump into the discussion and state "I didn't have this problem". Well, no shit, Sherlock! It would hardly be something that affected everyone, would it? I think if that was the case, in all likelyhood a lot more people would have mentioned it since the patch was released, wouldn't you agree? But you still considered it a worthwhile contribution to the discussion. Now imagine that everyone beside you who also didn't have this problem each made a post saying they didn't have the problem. Would that have the makings of a fruitful discussion do you think?

So, I experienced a problem which I knew wasn't widespread. I stated it was a problem I experienced, hence probably not a general one, and made a suggestion which could potentially prevent more problems of that type from arising in the future, thus saving GOG some valuable support hours. Which bit of that is it that you were so offended by?
Posted September 07, 2016
I'm sorry I asked now.
Posted September 07, 2016
avatar
JudasIscariot: OK, understandable. The only reason I mentioned anything is because your drivers are from before NMS released and I thought having drivers after the release of NMS would help.
avatar
Wishbone: Hmm, they shouldn't be. NVidia released a new driver right after NMS released with specific performance optimizations for NMS, and I did install that.

Okay, I just checked and it's really weird. DxDiag reports a different driver date than GeForce Experience. According to GeForce Experience, I have got the driver with the NMS specific optimizations (372.54), but it's dated 2016-08-15 while DxDiag dates it as 2016-08-11.
The only other reason I mentioned the date and asked you for some basic hardware/software info is because I entered the make and model of your card into Nvidia's very own driver search tool on their website and came up with this: http://www.nvidia.com/download/driverResults.aspx/107008/en-us

Nvidia's driver search tool for reference: http://www.nvidia.com/Download/index.aspx?lang=en-us
Post edited September 07, 2016 by JudasIscariot
Pages:
1
2
3
This is my favourite topic
Community
No Man's SkyPatch 1.08(32 posts)(32 posts)
(32 posts)