Error: Error in Feature pack C:/Program Files/Epic Games/UE_5.0/FeaturePacks/TP_VirtualRealityBP.upack. Failed to parse manifest: Invalid Json Token. Line: 43 Ch: 4

Qwarku · August 6, 2022, 8:48pm

Today I downloaded the update to version 5.0.3 and the same. Maybe some new information about solving the problem?

rskinner9000 · August 7, 2022, 1:57pm

I deleted TP_VirtualRealityBP.upack and that fixed the problem! Don’t think I need it not sure about your project.

Alkaseeh · August 8, 2022, 5:06pm

Ok it worked for me but I start to receiving anther error:

PackagingResults: Error: Visual Studio 2019 x64 must be installed in order to build this target.

I Installed VS 2019 but the error still appear, and am using blueprint why I need Visual Studio???

emypippo · August 10, 2022, 8:43am

Tks

unit23 · August 17, 2022, 6:40pm

This worked for me too (TP_VirtualRealityBP.upack), moved the file to a new folder, ‘Temp’.

unit23 · August 17, 2022, 6:41pm

Are you using a source build?

Big-Fel · August 18, 2022, 12:51pm

Acabei de alterar estes caracteres ï¼Œ pela virgula “,” e o meu projeto não esta abrindo mais. Esta dando mensagem de erro de crash report.

Tentei desfazer a alteração mas não funcionou.

Seja o que for não altere o seu arquivo Json.

thedarkyaman · August 23, 2022, 5:05pm

man i need u
i see went this way(C:/Program Files/Epic Games/UE_5.0/FeaturePacks/TP_VirtualRealityBP.upack,) and i see it but to where i should copy it i use in version 5.0.3 i did not use 4.2.7

rskinner9000 · August 24, 2022, 7:46pm

Delete that sucker. All my builds have been successful since.

Scott_Barrett · September 2, 2022, 1:50am

I hit this error as well - run visual studio installer, click ‘modify’, then add the c++ stuff. then I get the error asking for .NET stuff, back to visual studio and modify, adding the .NET stuff. you can save yourself the trouble and do it all at once. 2019 isn’t the important thing, the packages within it are. those packages exist in 2022 but you have to install them as described above.

Cenobite69 · September 11, 2022, 6:20am

I have this error when trying to import DAZ3D content, as the bridge fails to work when i try to import via using the DTU file i get this error.

I found this error in the outputlog.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/StarterContent.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_FirstPerson.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_FirstPersonBP.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_HandheldARBP.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_ThirdPerson.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_ThirdPersonBP.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_TopDown.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_TopDownBP.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_VehicleAdvBP.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogPakFile: Display: Mounted Pak file ‘H:/Unreal/UE_5.0/FeaturePacks/TP_VirtualRealityBP.upack’, mount point: ‘root:/’
LogPakFile: Display: Mount point: ‘root:/’ is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
LogFeaturePack: Error: Error in Feature pack H:/Unreal/UE_5.0/FeaturePacks/TP_VirtualRealityBP.upack. Failed to parse manifest: Invalid Json Token. Line: 43 Ch: 4
LogSlate: Took 0.000196 seconds to synchronously load lazily loaded font ‘…/…/…/Engine/Content/Slate/Fonts/Roboto-Regular.ttf’ (155K)
LogSlate: Took 0.000180 seconds to synchronously load lazily loaded font ‘…/…/…/Engine/Content/Slate/Fonts/Roboto-Italic.ttf’ (157K)
LogSlate: Took 0.000114 seconds to synchronously load lazily loaded font ‘…/…/…/Engine/Content/Slate/Fonts/DroidSansMono.ttf’ (77K)
LogViewport: Scene viewport resized to 2961x1627, mode Windowed.
LogStall: Startup…
LogStall: Startup complete.
LogLoad: (Engine Initialization) Total time: 10.96 seconds
LogLoad: (Engine Initialization) Total Blueprint compile time: 0.00 seconds
LogAssetRegistry: Asset discovery search completed in 7.5597 seconds
LogCollectionManager: Fixed up redirectors for 0 collections in 0.000002 seconds (updated 0 objects)
LogContentStreaming: Texture pool size now 600 MB
LogSlate: Took 0.000217 seconds to synchronously load lazily loaded font ‘…/…/…/Engine/Content/Slate/Fonts/Roboto-Bold.ttf’ (160K)
LogSlate: Took 0.000147 seconds to synchronously load lazily loaded font ‘…/…/…/Engine/Content/Editor/Slate/Fonts/FontAwesome.ttf’ (139K)
LogSlate: Took 0.000155 seconds to synchronously load lazily loaded font ‘…/…/…/Engine/Content/Slate/Fonts/Roboto-Light.ttf’ (167K)
LogDerivedDataCache: C:/Users/User/AppData/Local/UnrealEngine/Common/DerivedDataCache: Maintenance finished in +00:00:45.885 and deleted 0 file(s) with total size 0 MiB.
LogFactory: FactoryCreateFile: SkeletalMesh with DazToUnrealFactory (0 0 D:/Users/User/Documents/DAZ 3D/Bridges/Daz To Unreal/ethelgeneric/ethelgeneric.dtu)
LogSlate: Window ‘Message’ being destroyed
Message dialog closed, result: Ok, title: Message, text: Failed to import ‘D:/Users/User/Documents/DAZ 3D/Bridges/Daz To Unreal/ethelgeneric/ethelgeneric.dtu’. Failed to create asset ‘/Game/ethelgeneric’.
Please see Output Log for details.
LogAssetTools: Warning: Failed to import ‘D:/Users/User/Documents/DAZ 3D/Bridges/Daz To Unreal/ethelgeneric/ethelgeneric.dtu’. Failed to create asset ‘/Game/ethelgeneric’.

THE ROOT IS NOT MOUNTED TO A VAILD POINT! sounds funny but yeah how do i fix this?

A_Derpy_Chicken · September 13, 2022, 4:40am

I fixed my packaging error by deleting the C:/Program Files/Epic Games/UE_5.0/FeaturePacks/TP_VirtualRealityBP.upack then verifying my installation after that my build worked and was able to be launched!

Gladiatoer · October 16, 2022, 1:47pm

This worked for me too.

Soliver84 · November 13, 2022, 8:04pm

FIXED:
Quelle: [Solved] Unreal Engine 5.0.3 - TP_VirtualRealityBP.upack - Zip Packaging | Space-Nerd.com

But reading further in the same log, Unreal Engine 5.0.3 itself indicates the solution to correct this problem! You have to download and install from the Microsoft site the : .NET Core 3.1 Desktop Runtime (v3.1.28) – Windows x64

The Framework is available at the following address : Télécharger le .NET Core 3.1 Desktop Runtime

Once the .NET Core 3.1 is installed, no need to restart, you have to restart the Unreal Engine 5.0.3 and redo the export of the project in a .ZIP package.

walemmlis · November 15, 2022, 2:55am

Tried, it doesn’t work for me. The building error is still there.

Rcttroix · December 5, 2022, 2:10pm

That’s work for me too, thanks

Ivonny · October 19, 2023, 10:23pm

Hola a mi lo que me funciono fue instalar el .NET Core 3.1 antes mencionado, migrar el proyecto a uno nuevo y ojo desinstalar el plugin Electra que es para los videos y listo funciono, creí que iba a ver problemas cuand se empaquetara pero no fue así los videos funcionan bien en móvil en PC no se ven(pero es lo de menos)