[bug report?] Code changes not taking effect unless .dll file deleted manually
While I'm currently on 4.11 Preview 3, I've been having this problem since 4.10.2 and have only been able to resolve this error with upgrading to a new version of the editor. Here's a description of my problem:
I created a new structure (FSDeadEndTile) in my .h file, and created a TArray for it (called DeadEnds).
I created a function (int32 FindAllDeadEnds()) to loop through my LabyrinthTiles array and find all the dead end tiles and add them to the DeadEnds array.
Upon building and testing this, I kept crashing out when I would try to playtest my level. Any changes I made to the code (including commenting out everything I had just created) and rebuilding, would not clear this error from occurring. The crash report kept referring to an assert in the UE array code (index>=0) & (index < size). The very next line referenced my Labyrinth.cpp file line 14, which was part of the new function I had created. (if (!Tiles.Num()) return 0;)
Even though I had Built, Rebuilt, Cleaned with this whole function commented out, and even restarted the entire computer, this error persisted (and even still referenced this line of code which, as I said, was commented out and should not be executing at all) until I manually went into my binaries folder and deleted the UE4Editor-[gamename].dll file and reloaded the editor (which detected it was missing and rebuilt it.) Then I was once again able to PIE without crashing out.
If you need any more details, please ask. If there's something you can see that I did wrong, please let me know.
Many headaches would have been missed had I discovered this sooner.
asked Jan 22 '16 at 08:10 PM in Bug Reports
Thank you for that clarification. From rereading all of the information given thus far, are you experiencing the issue in any manner when using 4.11 Preview 4 or was this only an issue in 4.10.2?
Also, is this something that you're able to reproduce from a fresh project? If so, could you provide some steps on how to get the issue to occur from a fresh project setup?
If we are able to get a reproduction case and this was something that was fixed somewhere in the 4.11 previews, we may be able to find where the fix was or at least get a proper report entered for the issue.
answered Feb 01 '16 at 04:02 PM
Are you closing the editor, rebuilding the binary in VS and then restarting the editor? This is the only clean way to update.
answered Jan 22 '16 at 08:41 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here