Hey there @Ursu1a! Welcome to the community! I couldn’t find an issue listing for it, since this was a one time migration bug with a verified fix (not fully overriding the original command) I’m unsure if it would be addressed immediately. Also if you’d already migrated, you’ll have to make this change to the asset even if the migration tool corrected it in 5.2 since it wouldn’t make the same jump.
ok thank you. is it possible to apply the fix via blueprint?
Thank you so much! It worked!
