Differences in script sources for Steam and GOG version in patch 1.10

[Wasteland_Ghost]

Differences in script sources for Steam and GOG version in patch 1.10

I own Steam version and I don't have any problems with script-based mods. I also know some players on GOG version who don't have any problems with such mods. But. Since patch 1.10 I'm getting TONS of reports about being unable to compile my mod (and every other mod, in fact) using GOG version of the game.

I don't know what the problem is, because I have both mod users who don't have any problems and mod users who can't compile anything. Both sides claim they have updated properly or re-installed the game completely.

I read on this forum and on Nexus about some files that have to be added or removed. Some of them I can't find in my Steam version. This is why I'm wondering if Steam and GOG script sources are the same.

Since I don't own GOG version myself, I can't find out what's wrong. But I'm sure something IS wrong, because this isn't just one case and many people have this problem.

@Marcin Momot, could you, please, bring this issue to attention of proper people?

 

[KNGRSM]

I have GOG Version, no problems with it whatsoever.

 

[Wasteland_Ghost]

Good to know, thank you.

I've asked another player to upload his GOG version script sources for me. Turned out they're identical with my Steam script sources. He also has no problems with mods and he said he used GOG client to install and update the game.

So, I'm quite puzzled here. There's a group of GOG players who claim they have reinstalled the game completely deleting all leftover files and folders and still get compilation errors on mods that were updated to patch 1.10. Probably, some regional differences? I really ran out of ideas.

 

[Lieste]

Are they perhaps reusing old versions of the "current" patches, rather than the updated versions. GoG.com does a fairly good job of hiding the sub-versions of the files. There are no notifications of updated files of the same version number, and although it is trivial to check the current file name against those saved locally, it requires starting (and then dumping) the downloads for each file periodically (or finding a fleeting notification on some relatively obscure social media channel).

I had errors after updating my original
1.01>1.02>1.03>1.04>1.05>1.06>1.07>1.08>1.084>QMBSMods>1.084>1.10>refresh1.10
After replacing it with 1.06 (2.0.0.33)>1.10(2.0.0.40) (original download) I still had script errors, but these were fixed and script mods work after another installation of the newly downloaded base game (1.06 2.0.0.33) and a fresh download of 1.10 (2.0.0.40) and the newer 2.0.0.41 dlc pack. The 2.0.0.40 bin-1 file has a new date, 2015-10-13, and replaced the earlier 2015-10-09 file, though the file name is the same. The other patch files were not refreshed during the "download all" process in GoG Downloader. I don't use Galaxy out of preference.

 

[J_Slash]

GOG version, did not use galaxy to update.
Had compiling errors caused by the duplicate functions in behavior scripts.
I'm not really sure but I don't think there are different versions, my guess is the installer did not delete the old scripts folder before copying the new one, so older files with different names were not overwritten.

 

[KNGRSM]

GOG version, did not use galaxy to update.
Had compiling errors caused by the duplicate functions in behavior scripts.
I'm not really sure but I don't think there are different versions, my guess is the installer did not delete the old scripts folder before copying the new one, so older files with different names were not overwritten.

that's exactly my guess too.

All the people replying with "It fixed some of my compilation errors" probably still had some 1.08 mods installed that weren't updated to 1.10 scripts yet.

 

[Krevitz]

The 1.10 was a bit tricky as you can't use the old dlc installers but have to download the new dlc complete pack as it contain an hotfix.
For GOG user you can do it by downloading directly from the website site, or using galaxy by déactivate AND reactivate the dlc program.

whithout that hotfix no compilation is possible as the game don't reconize any dlc and they are needed to launch the game and you pretty much need a clean install anyway to be sure you don't have any leftovers from previous install.

but your mod aren't responsible for anything except working fine and giving us great time

 

[Lieste]

As I did a complete path removal and installation into a new location (no spaces in names for easier use of modkit tools) I doubt it had anything to do with left over scripts on the first re-installation, which still failed.

GoG was quite flaky over the first couple of hours and bin-1 took a while to even become available.... and when it did the first attempt was short over 1GB and needed refreshing before the installer would even fire off. The 'newer' version was the same filesize as the complete 'older' one, but may have had slightly different content (changes? corruption?).

 

[dragonbird]

I have both the Gog and the Steam versions of the game, and both are currently clean and working - I'm not using any mods in 1.10.

@Wasteland_Ghost - if there's a specific mod you'd like me to test, let me know.

 

[Wasteland_Ghost]

Thanks to everyone for replies.

Are they perhaps reusing old versions of the "current" patches, rather than the updated versions. GoG.com does a fairly good job of hiding the sub-versions of the files. There are no notifications of updated files of the same version number, and although it is trivial to check the current file name against those saved locally, it requires starting (and then dumping) the downloads for each file periodically (or finding a fleeting notification on some relatively obscure social media channel).

Interesting. Can anyone using GOG give a tip about how to install/update the game properly? Is it better done with GOG client or manually? Which files one needs to download to make sure he/she is on the latest version? Are there any kind of MD5 available for users downloading files manually? I'd happily buy the game second time to test everything myself, because CDPR are a kind of people I'd love to support, but I can't afford it right now.

@Wasteland_Ghost - if there's a specific mod you'd like me to test, let me know.

Thanks. Well, I already asked some of the GOG players I know to test FriendlyHUD and it worked for them. But it never hurts to do more testing. If you have some free time, could you, please, test it too?

but your mod aren't responsible for anything except working fine and giving us great time

I'm not trying to place responsibilities. But after getting so many script compilation errors reports I started to have doubts that I'm correct in assuming that GOG and Steam versions are identical in that respect. I'm probably OCD, but I like to get to the bottom of things.

So, to sum things up: GOG's patches have more subversions than Steam patches, correct? And this means that 1.10 might not be 1.10 even if it says so in menu. This also means that one have to re-download install packages if he/she has problems with the game (mods, missing textures, CTD).

 

[Krevitz]

Thanks to everyone for replies.


Interesting. Can anyone using GOG give a tip about how to install/update the game properly? Is it better done with GOG client or manually? Which files one needs to download to make sure he/she is on the latest version? Are there any kind of MD5 available for users downloading files manually? I'd happily buy the game second time to test everything myself, because CDPR are a kind of people I'd love to support, but I can't afford it right now.


Thanks. Well, I already asked some of the GOG players I know to test FriendlyHUD and it worked for them. But it never hurts to do more testing. If you have some free time, could you, please, test it too?

I'm not trying to place responsibilities. But after getting so many script compilation errors reports I started to have doubts that I'm correct in assuming that GOG and Steam versions are identical in that respect. I'm probably OCD, but I like to get to the bottom of things.

So, to sum things up: GOG's patches have more subversions than Steam patches, correct? And this means that 1.10 might not be 1.10 even if it says so in menu. This also means that one have to re-download install packages if he/she has problems with the game (mods, missing textures, CTD).

using gog galaxy, once you have make the update to 1.10, you need to go "more"/get backup and extra/ here click on more again and configure
once here uncheck the free dlc program than recheck it back, it will upload the hotfix..

 

[dragonbird]

Thanks. Well, I already asked some of the GOG players I know to test FriendlyHUD and it worked for them. But it never hurts to do more testing. If you have some free time, could you, please, test it too?

I'm not trying to place responsibilities. But after getting so many script compilation errors reports I started to have doubts that I'm correct in assuming that GOG and Steam versions are identical in that respect. I'm probably OCD, but I like to get to the bottom of things.
.

I got an error message on Gog, it worked on Steam:
The error -
Error [content0]game\behavior_tree\tasks\monsters\bttaskmaintainspeed.ws(10): Class 'CBTTaskMaintainSpeed' already defined.
Error [content0]game\behavior_tree\tasks\monsters\bttaskmaintainspeed.ws(74): Class 'CBTTaskMaintainSpeedDef' already defined.
Error [content0]game\behavior_tree\tasks\reactions\bttaskisman.ws(4): Class 'CBTCondIsMan' already defined.
Error [content0]game\behavior_tree\tasks\reactions\bttaskisman.ws(15): Class 'CBTCondIsManDef' already defined.

Update: I just ran Galaxy again, and it failed validation, even though it was OK when I installed HoS. As it says it wants to re-download 17GB, I stopped there - it would take a week to do that.

Which means I probably haven't been that helpful - I can confirm there's an issue, but I still don't know if the problem is your script or an error in some Gog installations.

 

[Wasteland_Ghost]

using gog galaxy, once you have make the update to 1.10, you need to go "more"/get backup and extra/ here click on more again and configure
once here uncheck the free dlc program than recheck it back, it will upload the hotfix..

So, when updating from 1.08 to 1.10, one needs to delete all DLCs and then re-install them again, correct?

Which means I probably haven't been that helpful - I can confirm there's an issue, but I still don't know if the problem is your script or an error in some Gog installations.

You was helpful, thanks. Since I have GOG users on patch 1.10 that are able to run the mod, problem is not with one of its scripts. And by the look of things it can be indeed a problem with older subversion. Can you, please, do another test for me?
1. zip your content\content0\scripts folder from under GOG The Witcher 3 folder and upload it somewhere for me to take a look at it.
2. Delete or move this folder to some other place.
3. Copy your content\content0\scripts folder from under Steam The Withcer 3 folder into the GOG The Witcher 3 folder.
4. Check if the mod compiles, if not - post the error log.

 

[Krevitz]

So, when updating from 1.08 to 1.10, one needs to delete all DLCs and then re-install them again, correct?

well, yes

I also observe that one can avoid the new ctd problem by deleting d3d11.dll and dxgi.dll but for those who were still use to delete the APEX_Clothing GPU_x64.dll for performance it's time to have it back cause it cut the loading times by well from a minute to a couple of second lol (off topic but still can be usefull )

 

[dragonbird]

So, when updating from 1.08 to 1.10, one needs to delete all DLCs and then re-install them again, correct?


You was helpful, thanks. Since I have GOG users on patch 1.10 that are able to run the mod, problem is not with one of its scripts. And by the look of things it can be indeed a problem with older subversion. Can you, please, do another test for me?
1. zip your content\content0\scripts folder from under GOG The Witcher 3 folder and upload it somewhere for me to take a look at it.

https://mega.nz/#!nh1HFIiT!BC11IUM8tcUoF1pA23B-1qulhv6kzV8lDUNzBR4nK6E

Mega seems different to the last time I used it, so if that doesn't work, let me know.

2. Delete or move this folder to some other place.
3. Copy your content\content0\scripts folder from under Steam The Withcer 3 folder into the GOG The Witcher 3 folder.
4. Check if the mod compiles, if not - post the error log.

It compiled just fine, but didn't immediately launch. I'm not sure if I was just impatient, but I tried launching it a second time and it worked perfectly.

Also, just checking the date/time of my Gog updates:
Patch 1.10 - patch_witcher3_1.01-1.10_2.0.0.40 Dated 8th October downloaded 9th October
Patch 1.10 dlc - setup_the_witcher3_dlc1-16_2.0.0.41 Dated 9th October downloaded 10th October
HoS - setup_the_witcher3_exp1_2.0.0.40 Dated 8th October downloaded 13th October

All were downloaded directly from Gog.

Anyway, if it's working for SOME people, it's definitely looking like a discrepancy with the Gog version. Hopefully the script folder will tell you whether it's deliberate or a download error.

 

[Krevitz]

https://mega.nz/#!nh1HFIiT!BC11IUM8tcUoF1pA23B-1qulhv6kzV8lDUNzBR4nK6E

Anyway, if it's working for SOME people, it's definitely looking like a discrepancy with the Gog version. Hopefully the script folder will tell you whether it's deliberate or a download error.

I've seen somewhere here that some versions will launch even with corrupt downloaded files, causing ingame glitches and/or compilation errors, to avoid that you need to verify the file system basically each update

 

[Wasteland_Ghost]

Mega seems different to the last time I used it, so if that doesn't work, let me know.

Thanks, it worked.

It compiled just fine, but didn't immediately launch. I'm not sure if I was just impatient, but I tried launching it a second time and it worked perfectly.

Yes, I also had this issue two or three times. Sometimes the game won't launch after compiling new scripts.

---------- Updated at 04:07 PM ----------

I now have two scripts folders from two different GOG users. Both are using 1.10 as game menu says. But scripts are indeed different!

The other player who uploaded his GOG patch 1.10 scripts for me had these scripts identical to my Steam patch 1.10 scripts. But scripts from Dragonbird are a bit different:
1. telemetryKeyword.ws is different, but the difference is only in comments, so this can't be the reason for compilation errors.
2. There is a duplicated file in Dragonbird's version: scripts\game\behavior_tree\tasks\hacks\btTaskMaintainSpeed.ws and scripts\game\behavior_tree\tasks\monsters\btTaskMaintainSpeed.ws. Both files are identical, except for comments. For the other GOG version and for Steam version this file is located in scripts\game\behavior_tree\tasks\hacks\btTaskMaintainSpeed.ws.
3. There also is an additional file in Dragonbird's version that is missing from both the other GOG version and Steam version:scripts\game\behavior_tree\tasks\reactions\btTaskIsMan.ws.

My theory is that the first version of patch 1.10 for GOG had this duplicated script and leftover script. They've uploaded it, then discovered the problem and uploaded another version. Since these scripts don't affect base game functionality, everything works fine until the player decides to install a script mod.

To sum up the issue: CDPR, please, no more stealth patches on GOG! It seems that the issue was fixed quick enough, but still many people downloaded the "broken" version and now they have problems with mods.

 

[Zanderat]

What has worked for me, through all the patches is to do a verify/repair after each patch.

 

[dragonbird]

What has worked for me, through all the patches is to do a verify/repair after each patch.

Verifying will only work if Galaxy knows there's a problem with it. Mine passed on the day I downloaded it.
And the problem for me is that now Galaxy DOES know there's something wrong with it, it wants to download 17GB. For a 10GB patch. With, currently, a download speed of around 500Kbps. I think I'll continue to play using the Steam version.

Anyway, it looks like @Wasteland_Ghost has an answer for anyone with problems.