Always when I’m creating project and have cycling call references in blueprints bugs are occurring later in production. For example Widget Switcher UMG screen - it was working for couple of days but now I’ve REINST near my custom widgets.
The same thing happened couple of times in different parts of blueprints. I need to delete blueprint which is causing the issue and implement it again to resolve the issue.
As far I know you guys are working on different blueprint references implementation. THIS SHOULD BE DONE ASAP because people will run into this problem really quick being in middle of production.
The system is supposed to find and replace all active references to classes that exist, then it renames all the old ones with REINST_ClassName. Since the REINST text is appearing, that means the references were never updated.
What are you referring to when you say “cycling call references”? There is a kind of BP issue that we are working on involving cyclical references, but I wanted to be sure you are talking about the same thing. Any additional information or reproduction steps may help.
Yes - we are talking about the same thing. The problem is that I can’t give you any repro steps, just every time middle in production blueprints are breaking because of the cyclical references. (REINS and Engine/Transient error)
That is a known issue that our blueprint developers are working on resolving. Once it is resolved, we will include it in the build notes. Let me know if you encounter any other unexpected behavior.
