Dedlus1
November 20, 2023, 10:22pm
1
Im getting these errors but i have no clue what they could mean. I tried moving the problem files out of their place and repackaging. That resulted in some files being recreated and others not. I have no clue whats going on.
UATHelper: Packaging (Windows): LogWindows: Error: appError called: Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\FileManagerGeneric.cpp] [Line: 123]
Leomerya12
November 20, 2023, 11:03pm
2
Jesus.
It doesn’t matter how many times I’ve helped others with these packing problems, or watched other people help others to learn more, I never seem to see the same thing twice.
Alright, first things first:
Fix up redirectors.
Migrate the ENTIRE project into an EMPTY PROJECT.
Report back.
Dedlus1
November 20, 2023, 11:58pm
3
Neither of those worked. It took a few minutes longer to fail this time though so theres that if it means anything at all.
Leomerya12
November 20, 2023, 11:58pm
4
Can you post the updated output log?
Dedlus1
November 21, 2023, 12:01am
5
Its in the same perforce folder. Only did that so that on the off chance it worked i could easily update everything for the team.
UATHelper: Packaging (Windows): LogWindows: Error: appError called: Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\FileManagerGeneric.cpp] [Line: 123]
1 Like
I notice the path …/…/…/…/…/…/Users/willt/Perforce/Deedls_COMPENDIUM_PP/Project_Pasta/Saved/Shaders/PCD3D_SM6-PCD3D_SM6/ShaderAssetInfo-Global-PCD3D_SM6-PCD3D_SM6.assetinfo.json
1 Like
Leomerya12
November 21, 2023, 12:09am
7
Okay, so you tested previously to make sure that every asset put in the project was packageable?
If not, unless someone else knows exactly what this text means (I do not… I have an idea… but not sure), you need to, one by one, in a FRESH PROJECT try to package each group of assets.
I’m not sure if you/your team made everything.
If you do not find a culprit, then it’s something else.
@IslandPlaya brings up a curious point about the file name length. Worth a shot! (As well as the drive).
Dedlus1
November 21, 2023, 12:12am
8
Replying to both at once. Its on my D drive. I can try moving it out of the perforce folder to see if that fixes it. Also most assets were made by my team. The only stuff not made by us is stuff thats worked in previous builds. Ill get back to you on whether moving it works.
Dedlus1
November 21, 2023, 12:41am
9
Alright so moving it somewhere with a shorter filepath didnt work. Ill try the asset group packaging thing. There werent too many new assets added since the last build so hopefully it wont be too hard.
Dedlus1
November 21, 2023, 2:36am
10
Somehow those errors went away. Now im stuck with this
UATHelper: Packaging (Windows): ********** BUILD COMMAND STARTED **********
1 Like
Leomerya12
November 21, 2023, 2:44am
11
Okay, so the build tool failed.
Under what circumstances did you receive this message in the output log?
I mean, did you isolate the problem assets/files?
Is this a package of the original project or only the problem asset(s)? I’m unclear.
Also:
Is there no more information in this log (or did another pop up)?
Furthermore, I STRONGLY suggest migrating this version into a fresh project and trying again.
Dedlus1
November 21, 2023, 2:47am
12
This is my entire project migrated into a new project. And that was the whole log. It fails within seconds of starting.
Leomerya12
November 21, 2023, 2:49am
13
You mentioned when I suggested migrating the first time:
What is it that has changed between now and then?
Dedlus1
November 21, 2023, 2:52am
14
I honestly have no clue. I just tried it again since i was at the end of my rope and it magically got rid of the other errors this time.
Leomerya12
November 21, 2023, 3:05am
15
!!!
You’re going to have to role up your sleeves and diagnose this:
Can you package an empty project?
If so, you really do need to go through the assets in your project, MIGRATE them in batches to a fresh, empty project, and keep packaging until you receive the error.
Dedlus1
November 21, 2023, 3:13am
16
Alright well ill get back to you once i manage to find a culprit. Thanks for all the help so far.
1 Like
Dedlus1
November 21, 2023, 3:59am
17
Ive narrowed it down to one of my plugins called KawaiiPhysics. Cant exactly disable or remove it since some assets rely on it.
UATHelper: Packaging (Windows): Expecting to find a type to be declared in a module rules named ‘KawaiiPhysics’ in UE5Rules, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. This type must derive from the ‘ModuleRules’ type defined by Unreal Build Tool.
1 Like
Leomerya12
November 21, 2023, 4:13am
18
Okay, you can try copying the plugins to the Engine\Plugins\Marketplace folder.
Unreal 5.x requires this, I think to discourage willy-nilly tinkering.
Dedlus1
November 21, 2023, 11:34pm
19
Im getting this now.
UATHelper: Packaging (Windows): Missing precompiled manifest for ‘KawaiiPhysics’, ‘C:\Program Files\Epic Games\UE_5.1\Engine\Plugins\Marketplace\KawaiiPhysics\Intermediate\Build\Win64\UnrealGame\Development\KawaiiPhysics\KawaiiPhysics.precompiled’. This module was most likely not flagged for being included in a precompiled build - set ‘PrecompileForTargets = PrecompileTargetsType.Any;’ in KawaiiPhysics.build.cs to override. If part of a plugin, also check if its ‘Type’ is correct.
Ill try to do what it says but i cant guarantee i wont majorly mess it up lol
Dedlus1
November 22, 2023, 12:10am
20
Every solution ive found online has done nothing for me. Some people say to disable the plugin but i cant since im using it. Others are saying to just do what it says but i cant because the filepath its giving me doesnt exist and if i go into KawaiiPhysics.build.cs there just isnt a precompilefortargets thing.