Looking at the mentioned file and line-number, I get the impression that this has something to do with the new support for double precision in UE5?
The project will crash before it can load, but if I edit the 4.27 to use an empty level as startup before I convert, I can get the editor to load the converted project in 5.01. At this point I can find my blueprints in the content browser, but if I try to edit them, opening some (most) of them will result in an immediate crash like the one mentioned above.
Does anyone have any ideas about what is causing this, or perhaps some clever tricks that can help me identify the source of the error?
Not yet. I also upgraded to 5.0.2, but it didn’t change anything. I’m just keeping my projects in 4.27 for now, but I have to solve this at some point. I tried to recreate one of the offending blueprints from scratch, but there’s a lot of inter-dependencies that make it difficult to reach any conclusions… I’d be very interested to hear about any clues you might find about the cause of this issue. Google is remarkably silent, my own forum-post is the only relevant hit I get.
Yes I have VaRest, although I’m not sure it’s “influence” could damage quite so many blueprints… but who knows, like I said, there are lots of links between BP’s. I’ve also made some custom structs, and I suppose they are good candidates; I mentioned the new double precision data types, and I suppose there are conversion routines for this that are failing to reach some value/variable somewhere. I don’t have time to test things right now, but I’ll be sure to post anything I discover when I look at it. By “first version”, do you mean the 4.27? It is 4.27.2
I’m not using “make json”, but quite a few other VaRest nodes, like “construct json request”, “construct json object”, “decode json object”, “call/set url”, “set request object” and “break json”
Vladimir has posted a fix on the error report you linked. I notice the patch is in a file called VaRest_BreakJson.cpp. so I guess there’s a good chance it affects my nodes/issues as well. I don’t think the patch has made it into an actual update yet, though?
Did it solve the issue? I’ve had trouble in the past, packaging c++ projects that are stored on network shares. To avoid this, I’ve turned the (self made) C++ code I needed into a compiled plugin, and converted my projects back into Blueprint-projects. I suppose my packaging issues might go away with UE5, but I’d just as soon keep my projects BP only for now, which doesn’t give me the option of building VaRest from source.
