output with this error said to “contact framework team as we need a repro for this bug!”
I can explain how it happened in general terms: I placed a Set Timer Delegate node into my character blueprint (I admittedly have no idea what I’m doing with delegates and such) and bound it to an event another class of mine with a hitscanned instance of that class set as target. I compiled, it compiled successfully, and I then played it. It wasn’t behaving way I wanted and I was sure that this wasn’t right path to try to go down, so I hit ctrl+z to undo and things froze up for 20-30 seconds. When it came back to, it had deselected specific event that I had selected in “Create Event” node, after which I deleted that node and Set Timer Delegate node to restore it to how it was. I then tried to compile again and it failed with error I specified.
I am able to repro this by following similar steps.
Hi Squarepupil,
I wasn’t able to reproduce this in 4.7.2. Are you using a different version of engine? Does this occur in a new project as well, or only your current project? Can you post a screenshot of your BP set with specific step-by-step instructions so we can try to reproduce it here? Thanks!
I think it would be easier if I just share branch on github with you. There’s too much going on and my blueprinting is too ad-hoc to bother trying to explain it. If you give me your github name, I’ll add you as a collaborator and give instructions on how to repro.
I am using 4.7.2 btw.
Can you check to see if this is producible in a new project? You mentioned being able to reproduce it following similar steps, I just need clarity on what those steps are, and order in which to take them.
I can’t reproduce it in a new project.
What I meant is that I don’t have to do exactly same steps as when it happened first time. I can do a slightly different procedure (but still along same lines) to make it happen again. It’s definitely bound to something in my project.
Okay. My GitHub username is BenHalliday. Have you edited source at all for this build?
Nope. repo is called ColorTheoryTest and branch is Compiler-Error.
Here’s how to reproduce it once you’re on branch:
Change while loop in ColorTheoryCharacter event graph:
…to a Set Timer Delegate as follows:
Make sure you add “Deplete” event in ColorContainer event graph so that you can select it in event dispatcher:
Compile and play. End play session and hit undo to undo last command, which would be to select Deplete() from dropdown list in Create Event node in ColorTheoryCharacter. On my system, editor hangs for a 10-20 seconds. Try to put ColorTheoryCharacter back way it was with a while loop (like in first picture) and recompile. You should get error:
I hope these instructions are clear enough.
I pulled project from Compiler-Error branch, and wasn’t able to reproduce this at all. If you close project and reopen it, does this reoccur? Are there any other steps I might be missing?
I never saved it in that state, so when I reopen it’s got original while loop. It’s 100% reproduceable on my end. Not sure what might be different about it that it doesn’t repro on your end. I can try this again in a couple of days when I have access to another machine of mine.
Okay, sounds good. I didn’t get any hang on undo, though that may be a system thing. I definitely didn’t get those errors by undoing all way back to original While Loop and recompiling. If you think of anything else that I may have missed, please let me know.
Just tried it on my other system. Didn’t repro. Ah well.
Would you mind giving me a brief description of what this bug is about?
Unfortunately I have no idea, and without being able to reproduce it here I’m at a bit of a loss. I can’t think of any reason this would happen on one machine and not another, assuming project is same between them.
In system in which this occurs, are you able to create a new Branch node and get past this compiler error?
Yea. On original system I ended up abandoning entire Set Timer Delegate workflow that I was trying and I’m in clear. No such bug since then.
Okay, I’ll go ahead and resolve this post, then. If this sort of thing pops up again and you’re able to reproduce it on both machines, please comment here again and we’ll take another look. Thanks for trying to report this for us!
