umg - child widgets create crashes + saving issues

  1. create two widgets (A AND B)
  2. put widget A inside widget B
  3. play - get this c++ exception

— after rebuilding and launching the editor - i can play my game with no issue, i can even update my child widget - however the second i COMPILE my child widget, if i play my game again, i get this exception

22155-untitled.png

!

on occasion i’ve gotten the transient issue too where i couldn’t save the child widget once it was added to another

another mild annoyance is if I dont do any widgets in other widgets - if I compile any of my UMG components, the next time i play my game - in visual studio I get this secondary exception - if i continue twice - everything runs fine until the next time i compile a umg widget

22156-untitled.png

!

Hello ,

I was unable to reproduce this issue on my end. I have a few quick questions for you to help narrow down the problem that you experiencing.

Quick questions:

  1. What version of the engine are you using?
  2. What version of visual studio are you using?
  3. Running the binary version of the engine or did you build it from source code?
  4. Can you reproduce this in a clean project?
  5. If you can reproduce this in a clean project, can you provide accurate steps to reproduce the issue?
  1. unreal 4.5.1

  2. visual studio 2013 - update 4

  3. binary version

  4. no but i was able to produce this with clean modules in my existing project

  5. im not so sure if parenting/childing is the cause anymore - this is just something ive noticed over days and days of UMG usage. sometimes I’ll update a widget, it wont update in my game, pressing compile sometimes gets it to refresh, sometimes pressing save does - and every so often it crashes everything out.

Hello ,

I am still unable to reproduce this crash. Is this only happening in a certain project? If so would it be possible for you to provide the project along with a detailed list of steps to cause the crash?

Hello ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.