# Unreal 5.1 Datasmith Dataprep Asset Crashes on Updating Viewport **URL:** \ **Category:** Pipeline & Plugins\ **Tags:** unreal-engine, question\ **Created:** [December 11, 2022, 2:45pm UTC](https://forums.unrealengine.com/t/unreal-5-1-datasmith-dataprep-asset-crashes-on-updating-viewport/725968 "2022-12-11T14:45:15Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Goraxxius1](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/goraxxius1/32/1163279_2.png) [@Goraxxius1](https://forums.unrealengine.com/u/Goraxxius1)\ **Post date:** [December 11, 2022, 2:45pm UTC](https://forums.unrealengine.com/t/unreal-5-1-datasmith-dataprep-asset-crashes-on-updating-viewport/725968/1 "2022-12-11T14:45:15Z")
Hi everyone. I’ve been working with Datasmith and Unreal for a while now and find it a very effective workflow. I’ve upgraded to Unreal 5.1 but I am unable to utilize dataprep assets from 5.1. As soon as I load a file/folder into the dataprep asset it crashes as soon as it reaches the updating view port stage. I can load the datasmith files directly through the import datasmith file tab, just not through the dataprep asset. The same datasmith files do work in Unreal 5.0 which is why i have narrowed it down to Unreal 5.1. I haven’t found anywhere, where someone has had a similar problem so I am a bit lost. The main reason I use dataprep assets is so I can do bulk changes to materials and convert models to Nanite without tediously doing it manually on each reimport after changes. My question is, can I do anything to correct the problem or alternatively another way to do bulk changes on my datasmith assets after import? Thanks in advance. ---
**Author:** ![UElaci](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@UElaci](https://forums.unrealengine.com/u/UElaci)\ **Post date:** [December 12, 2022, 7:40am UTC](https://forums.unrealengine.com/t/unreal-5-1-datasmith-dataprep-asset-crashes-on-updating-viewport/725968/2 "2022-12-12T07:40:15Z")
Same issue here. I can avoid dataprep for now but it’s a shame this nice tool is completely broken apparently. ---
**Author:** ![UE\_FlavienP](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ue_flavienp/32/1194546_2.png) [@UE\_FlavienP](https://forums.unrealengine.com/u/UE_FlavienP)\ **Post date:** [December 12, 2022, 12:34pm UTC](https://forums.unrealengine.com/t/unreal-5-1-datasmith-dataprep-asset-crashes-on-updating-viewport/725968/3 "2022-12-12T12:34:18Z")
Do you guys @UElaci @Goraxxius1 have those 9 assets in the Dataprep Editor Content? ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/8/e/1/8e129f0ce19e5a74854dee9c64cb9ce8950e2165.jpeg) Else you will need to perform a “verify” on your installation of UE5.1 and when closing UE after running dataprep import do not save modification on those files. c.f. more details here [Visual Dataprep Viewport Crash - #2 by UE\_FlavienP](https://forums.unrealengine.com/t/visual-dataprep-viewport-crash/715278/2) ---
**Author:** ![Goraxxius1](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/goraxxius1/32/1163279_2.png) [@Goraxxius1](https://forums.unrealengine.com/u/Goraxxius1)\ **Post date:** [December 13, 2022, 8:06pm UTC](https://forums.unrealengine.com/t/unreal-5-1-datasmith-dataprep-asset-crashes-on-updating-viewport/725968/4 "2022-12-13T20:06:51Z")
Thanks @UE_FlavienP. That worked perfectly. I was missing the Dataprep assets as you indicated in the screen shot. I did a verification and tested with a Datasmith Asset. It worked! I didn’t save the Datasmith changes as you suggested and all is still working. Thanks again for your quick response and suggested actions. Really appreciate it. ---
**Author:** ![UE\_FlavienP](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ue_flavienp/32/1194546_2.png) [@UE\_FlavienP](https://forums.unrealengine.com/u/UE_FlavienP)\ **Post date:** [December 14, 2022, 11:16am UTC](https://forums.unrealengine.com/t/unreal-5-1-datasmith-dataprep-asset-crashes-on-updating-viewport/725968/5 "2022-12-14T11:16:50Z")
You are welcome, the bug as been reported and should be fixed for 5.1.1