Invalid boolean encountered while reading archive

Development Platform & Builds Debugging, Optimization, & Profiling
, , ,
1

I just want to say one thing to the Epic development team.

Thank you very much for mentioning the name of the boolean in the error message.

Now I have to search one by one until I find the variable that is causing the problem.

The person in charge of this definitely deserves a promotion.

Error: Invalid boolean encountered while reading archive /Game/Game/GamePlay/Actors/MovingPlatform/BP_MovingPlatform_NEW - stream is most likely corrupted.
[2025.01.26-08.44.25:787][  0]LogLinker: Fatal: [AssetLog] C:\Users\Admin\Desktop\UNREAL PROJECT\Catharsis55\Content\Game\GamePlay\Actors\MovingPlatform\BP_MovingPlatform_NEW.uasset: OverlapableBoxComponent /Game/Game/GamePlay/Actors/MovingPlatform/BP_MovingPlatform_NEW.Default__BP_MovingPlatform_NEW_C:OverlapableBoxComponent: Serial size mismatch: Got 179, Expected 119
[2025.01.26-08.44.25:787][  0]LogWindows: Error: appError called: Assertion failed:  [File:D:\build\++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\LinkerLoad.cpp] [Line: 4856] 
C:\Users\Admin\Desktop\UNREAL PROJECT\Catharsis55\Content\Game\GamePlay\Actors\MovingPlatform\BP_MovingPlatform_NEW.uasset: OverlapableBoxComponent /Game/Game/GamePlay/Actors/MovingPlatform/BP_MovingPlatform_NEW.Default__BP_MovingPlatform_NEW_C:OverlapableBoxComponent: Serial size mismatch: Got 179, Expected 119

Thank you for your time!!

2

I found the variables that were causing the problem.

The error message had nothing to do with the actual problem.

	//If true, this component will cache its bounds during cooking or in PIE and never recompute it again. This is for components that are known to be static.	
		SceneComponent->bComputeBoundsOnceForGame=true;

		// If true, this component has already cached its bounds during cooking or in PIE and will never recompute it again.	
		SceneComponent->bComputedBoundsOnceForGame=true;

Congratulations, you have implemented the most useless error message in the entire history of computing.

3

Try fixing up redirectors. Your asset is probably a duplicate of another asset with just the NEW added. It probably still points to the old assets location causing the mismatch error on cook.

Guessing you have both

  • BP_MovingPlatform
  • BP_MovingPlatform_NEW
1 Like
4

Hi @3dRaven

The problem was fixed.
I simply deleted the variables that were causing the problem and everything worked correctly.

bComputeBoundsOnceForGame
bComputedBoundsOnceForGame

I was experimenting a little with the class USceneComponent. I was looking for things to optimize!!

Yes, I have two. In the new one I have customized all the components to achieve better performance. A BoxComponent in this case OverlapableBoxComponent .

I really just wanted to note that the error message I received does not help… it does the opposite… it confuses. I guess if someone says it the engineers will try to do better next time.

I was lucky because I just wrote the USceneComponent derived class. But if this happens to another person, they are totally lost.

Anyway this error is in the engine code… These two variables are very dangerous

uint8 USceneComponent::bComputeBoundsOnceForGame
uint8 USceneComponent::bComputedBoundsOnceForGame

Thank you very much for your help @3dRaven
You Rock!! :heart: