MotoGP 21

[spiritovod]

The game is built with 4.25. The situation is almost exactly the same as with Chivalry 2, some skeletal meshes works, some doesn't.

Here are results of brief analysis: in both games with some particular non-working meshes you're getting exactly the same "serializing behind stopper" error with A0008 data set. Also, you can get exactly the same error in some 4.26 games (like Project Morpheus) in umodel builds prior to 1504. Considering all this and that those games were created by different developers it's quite possible that Epic backported some changes from 4.26 to 4.25 without announcing it, so a few of recent 4.25 games became mid-version games even with stock engine. Though the reason may be different, it's just a guess.

Some samples: link

[BIKER7202]

Hello, sorry to bother you but I'm having an issue with umodel when trying to open meshes in the newly released MotoGP 21 game.

The game is made in Unreal Engine 4.25 and there's no problems when opening textures, skeletons, material instances, etc.
It's just the models, every time I open one I get this error:

"Memory: bad allocation size 1384278040 bytes
appMalloc: size=1384278040 (total=47 Mbytes) <- FArray::Empty: 692139020 x 2 <- TArray::SerializeSimple <- FStaticLODModel4::SerializeRenderItem <- TArray::Serialize: 3/8 <- USkeletalMesh4::Serialize <- LoadObject: SkeletalMesh4'chassis102.chassis102', pos=7074C1, ver=518/0, game=ue4.25 <- UObject::EndLoad <- LoadWholePackage: /Game/assets/graphics/vehicles/bikes/cat001/chassis/chassis102/skeletal_meshes/chassis102.uasset <- CUmodelApp::ShowPackageUI <- CUmodelApp::ProcessKey: key=6F, down=1 <- VisualizerLoop <- Main: umodel_build=1544"

There's one model in the game that doesn't throw this error and loads fine so I'm not sure why this errors occurs with every other one.

Is there anything that can be done to resolve the problem?

Thanks, BIKER7202

[adrmelandri]

Did you even read the above comments?

BIKER7202's topic was actually moved by Gildor to this topic. So I doubt BIKER7202 realizes this.

[adrmelandri]

Now it's a different message. But I was trying to access the pak files with 4.27, with 4.25 will have "serializing behind stopper" while with 4.26 will have "bad memory allocation size"

[Juso3D]

I hope Gildor can add 4.25 plus override in the next incoming updates

I believe Gildor wont do in between versions or when only 1 game is effected by it....

[adrmelandri]

Skeletal meshes and animations works fine with specific umodel build (from this topic) - no special override is required, simply choose proper engine version. It can be used with all games with this particular problem.

@Blenux: Please read my post above, this problem affects all 4.25 games, which are presumably build with modified branch of the engine. Currently there are 3 known games with such problems, including this one, Hood: Outlaws & Legends and Chivalry 2.

@abbiyukd: It sounds logical, considering my previous findings, but actually next-gen consoles are properly supported since release of stable 4.25 (base version). I took a quick look, apparently 4.25-plus branch is more about ray-tracing features and async optimizations. The only related to meshes commit look like this, but I failed to understand if it's even related to the issue. Despite it also has merges from 4.26 branch, umodel doesn't have related conditions, it serializes that part almost identically for 4.24-4.26.    

If anyone is curious, what the problem is - most meshes from those games suggest that LODInfo is bigger than actual LODModels data (for example 3-5 items for constant 1 LOD). While it may happen, due to specific StripFlags and bIsLODCookedOut, bInlined values upon serialization umodel is going into "if (!StripFlags.IsDataStrippedForServer() && !bIsLODCookedOut)" condition instead of skipping it along with Lod.RequiredBones for non-actual data - and crashes.

Thank you so much man! Helps a lot!