Regression UE-55496 won't be fixed til 4.20?

I’m sure 4.19 is getting close to being released, but UE-55496 is a major regression for us vs 4.18 and yet it has a trivial fix - see e.g. .

We’ve been eager to get onto 4.19 because 4.18 introduced a separate regression. So our project works in 4.17 but we’d love to get some of the improvements in 4.18, but we can’t because of the other regression. But now because of this bug in 4.19 our project won’t even load, so it looks like we’re out of luck until 4.20.

Since this regression was just added in January, and since there is a very straightforward fix, is there any way this could be reviewed for inclusion in 4.19? This is a new bug that was created as part of the 4.19 work, and here’s an opportunity to fix that bug before 4.19 is ever released.

Also, that bug entry says it affects 4.20 but it fails to mention 4.19 - any way we could get that changed so it’s accurate?

Hi, thanks for writing. I might be misunderstanding you, though. This question is referencing a bug that was already filed using that form - bug UE-55496 (the new bug submission form is great, but it is problematic in that it is 100% read-only for the public).

So in the case where there is a problem with the bug writeup, what is the correct course of action? I posted here only because that bug submission form doesn’t allow me to point out the mistake in the bug writeup, but I’m happy to use some other means if you can point me in the right direction.

I guess I could open a bug /about/ another bug writeup, but that seems like it’d be abusing the submission form. But happy to do it if that’s what Epic wants. Thanks again!

Just to follow up some more - that forum thread you directed me to has many, many people that are explaining the same problem with the submission form that I’m talking about, and it also includes this bit from the “UE Community Manager”:

“What about visibility and collaboration?
Bugs will be visible on the Public Bug Tracker after we’re able to reproduce them and it is determined not to be a design request. You can always create a public thread on AnswerHub discussing the issue and reference the ID of the bug, once it becomes available. You’ll still be able to collaborate, discuss issues, and work on solutions together.”

So… I think I did exactly that, but please let me know if Epic wants us to follow a different process now. Thanks!


We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.