We’ve migrated from older Windows GDK Unity package on 2022.3 LTS to this new unified version and latest Unity 6.3 LTS. Things are now overall working, but, with latest packages from Package Manager, subval fails with the following (before we did this migration, everything was fine):
<failure Id="ILI_NonRetailDependencyFound">Non-retail dependency in file \\?\D:\Jenkins\workspace\MyGame_GDK_Release\BUILD\MyGame_Demo_Data\Plugins\x86_64\Microsoft.Xbox.Services.GDK.C.Thunks.dll: MSVCP140D.dll.</failure>
<failure Id="ILI_NonRetailDependencyFound">Non-retail dependency in file \\?\D:\Jenkins\workspace\MyGame_GDK_Release\BUILD\MyGame_Demo_Data\Plugins\x86_64\Microsoft.Xbox.Services.GDK.C.Thunks.dll: VCRUNTIME140D.dll.</failure>
<failure Id="ILI_NonRetailDependencyFound">Non-retail dependency in file \\?\D:\Jenkins\workspace\MyGame_GDK_Release\BUILD\MyGame_Demo_Data\Plugins\x86_64\Microsoft.Xbox.Services.GDK.C.Thunks.dll: VCRUNTIME140_1D.dll.</failure>
<failure Id="ILI_NonRetailDependencyFound">Non-retail dependency in file \\?\D:\Jenkins\workspace\MyGame_GDK_Release\BUILD\MyGame_Demo_Data\Plugins\x86_64\Microsoft.Xbox.Services.GDK.C.Thunks.dll: ucrtbased.dll.</failure>
GDK version is 251000, as required by Xbox/Series versions. Or is is that WinGDK needs the build machine to also have a different/more recent SDK version installed?
I’ve got these files in Plugins/GDK, which seem to automatically be added when installing GDK Packages via PM:
I’ve seen a few threads here and on Microsoft Game Core for Xbox forum too (this this issue for me is ONLY for Windows GDK, consoles are fine), and I’ve tried cleaning Library/Temp/Obj folder, tried from different PCs, and the result is the same.
Somehow it uses debug versions for DLLs? I’m in Master C++ configuration, non-dev builds, building a non-sideloadable package, and signing with Stable Key. We build with the CleanBuildCache player option. I see in the symbols file, indeed some debug versions of PDBs? Is that normal? :
I believe a version without .Debug should be present here for the PDB. All others use correctly the master version:
(and same for executable)
Packages installed:
For other platforms, I’ve got both VS 2022 and 2019 installed, both with Win10 SDK + Game Dev with C++ :
I do not understand this… Could it be that I’d need to uninstall VS 2019?
Unrelated to this (but could be?), but I’ve noticed that on the contrary to Xbox/Series:
- Since the upgrade from GDK for PC to this new version, symbols for WinGDK are not properly present (only GameAssembly.pdb is present), unless “Copy PDB Files” is true - in which case, since they are copied into the root of the build output, they are included in the final package, which causes Subval issues for suspect files. I’ve been forced to add a post build process (before makpgk) to fully delete them, and they still are then present in final auto-generated .zip symbol files, but no longer included in the package
- To me this is not normal, shouldn’t require me to do that - I imagine there are some issues with these recent versions of Windows GDK packages - or specific to our environment somehow? This isn’t required for Xbox/XSX, and was needed prior to migration to unified packages
Thanks for your help!
Charles