I’ve just upgraded my current project (C++) from 4.26.2 to 4.27.2. Now, in shipping builds when the client connects to the dedicated server, I am getting this error:
[2023.01.18-20.00.45:658][620]LogStreaming: Error: Couldn't find file for package /Script/GameplayDebugger requested by async loading code. NameToLoad: /Script/GameplayDebugger
It only happens in shipping builds so I’m not sure why it’s even trying to load it, but even if I disable the GameplayDebugger, the error still appears. Any ideas on what could be causing it or how to resolve it?
It’s possible that the package is not being included in the shipping builds, this could be caused by a few different things, such as:
The package is not being included in the project’s cooked content, you can check this in the project’s settings under the “Cooker” category.
The package is not being included in the project’s packaging settings, you can check this in the project’s settings under the “Packaging” category.
The package is being excluded from the shipping build in the project’s build configuration, you can check this in the project’s settings under the “Build” category.
You can try to include the package in the cooked content, packaging settings and build configuration. If the problem persist, please provide more information about your project and how you are building it.
So I checked your suggestions, but I did not find anything referenced with regards to manually including/excluding packages. Maps and blacklists all there. I also built with full logging on the cook and never saw the GameplayDebugger plugin included.
However, I think it maybe appears to have been a discrepancy between using a Development dedicated server and Shipping build client. I’m not 100% sure, but when I matched the Shipping client to shipping dedicated server, the error disappeared on it’s own.
I don’t know if this is actually what was happening, because I did the same in 4.26.2 and never got this error. But I’m using 4.27.2 as a stepping stone to UE5 anyway. If UE5 presents no issues, then I won’t need to worry anyway. If for some reason and UE5 has the same issue or I have to proceed with 4.27.2 and the issue persists, I’ll provide you more information as requested.