Posted September 06, 2016
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
Well, it's up to the developers to upload the update to Galaxy (which we then make offline installers for the non-Galaxy users) as they have direct access to the game so they can update it at will :)
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
doodo477: Whats more confusing is why for the non experimental GOG Galaxy client the NMS exe has the following info. For the patch_no_mans_sky_2.4.0.6 (Patch 1.07)
FileVersion :"0.1.0.0"
ProductVersion :"0.1.0.0"
CompanyName :"Hello Games"
FileDescription :"No Man's Sky"
InternalName :"NMS.exe"
LegalCopyright :"Copyright (C) 2016 Hello Games"
OriginalFilename :"[Built with SIMON-PC by bbbsc_000 on 2016-09-02 0924 ]"
ProductName :"No Man's Sky"
Where the GOG Galaxy client experimental branch (Currently still on 1302131) Reads the following exe info.
FileVersion :"0.1.0.0"
ProductVersion :"0.1.0.0"
CompanyName :"Hello Games"
FileDescription :"No Man's Sky"
InternalName :"NMS.exe"
LegalCopyright :"Copyright (C) 2016 Hello Games"
OriginalFilename :"[Built with DESKTOP-MATL5CM by Will on 2016-08-26 0541 ]"
ProductName :"No Man's Sky"
It's probably because the experimental branch has not been updated after 1.07 yet, hence the older date on the experimental version.FileVersion :"0.1.0.0"
ProductVersion :"0.1.0.0"
CompanyName :"Hello Games"
FileDescription :"No Man's Sky"
InternalName :"NMS.exe"
LegalCopyright :"Copyright (C) 2016 Hello Games"
OriginalFilename :"[Built with SIMON-PC by bbbsc_000 on 2016-09-02 0924 ]"
ProductName :"No Man's Sky"
Where the GOG Galaxy client experimental branch (Currently still on 1302131) Reads the following exe info.
FileVersion :"0.1.0.0"
ProductVersion :"0.1.0.0"
CompanyName :"Hello Games"
FileDescription :"No Man's Sky"
InternalName :"NMS.exe"
LegalCopyright :"Copyright (C) 2016 Hello Games"
OriginalFilename :"[Built with DESKTOP-MATL5CM by Will on 2016-08-26 0541 ]"
ProductName :"No Man's Sky"
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
JudasIscariot: Well, it's up to the developers to upload the update to Galaxy (which we then make offline installers for the non-Galaxy users) as they have direct access to the game so they can update it at will :)
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. edit: did you by any chance ever use Galaxy but then decided to update the game via one of our offline patches?
Post edited September 06, 2016 by JudasIscariot
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
Wishbone: Congratulations. I did.
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. 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.
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. JudasIscariot: edit: did you by any chance ever use Galaxy but then decided to update the game via one of our offline patches?
Wishbone: Nope. I've never even had Galaxy installed on my system. 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?
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
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?
Wishbone: Sure. What do you want? A DxDiag? 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?
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.
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.
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.
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 :)
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
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 :)
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
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 06, 2016
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.
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.
JudasIscariot
Thievin' Bastard
JudasIscariot Sorry, data for given user is currently unavailable. Please, try again later. View profile View wishlist Start conversation Invite to friends Invite to friends Accept invitation Accept invitation Pending invitation... Unblock chat GOG.com Team
Registered: Oct 2008
From Poland
Posted September 07, 2016
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.
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.
Nvidia's driver search tool for reference: http://www.nvidia.com/Download/index.aspx?lang=en-us
Post edited September 07, 2016 by JudasIscariot