, your advice helped me discover the offending node. Thank you. Your massive karma score is well-deserved.
However, this was not a bug on Epic’s part at all. This is simply a case of bad practices due to my incomplete understanding of computer science. I used a DecrementInt node and had passed it the output of a Select node, of which not every pin led to the instance of a variable. No wonder the Kismet Ensure function disliked this! After removing the DecrementInt node, my project now opens without the Error mentioned in my question post.
For those like me, inexperienced with the troubleshooting tools available, here is what I did to track down the node:
Using the error in my question post (and 's helpful confirmation of the code in question) in Visual Studio I set a breakpoint on the function at line 980 in KistmetCompilerVMBackend.cpp. If I knew this process better, I could probably have somehow filtered the breakpoint triggers down, but I quickly executed through the function breakpoints until I was able to tell it was iterating through the class I knew was at fault. Once there, I carefully executed through the nodes one by one until my error came up in the Visual Studio debugger Output window. I made note of all the info about the node in question (in particular, its EdGraphPin number, and the fact that it was a K2_Select node)
Then I loaded up my blueprint in the editor and searched out all the Select nodes and copy/pasted them into a text editor. I found the EdGraphPin number I collected from the debugger among the pasted text and used that info to find my node in my blueprint graph.
