Seconded on this. It seems unreasonable to leave such a critical bug forever present in a version of the engine that Epic presents as “stable”. I don’t particularly appreciate Epic forcing me into a minor version upgrade for every project I’m running to correct something that should function correctly from the start.
Epic can also change its license agreement between minor versions (like they recently did with their new per-seat model for some industries). IMO, this sets a pretty bad precedent if previous engine versions are being left behind with critical issues present.
If this had occurred in 5.3 instead of 5.4, we’d have some very angry ArchVis and film professionals here saying, “I’m not paying you $1,850 to fix this”. Epic is certainly within its rights here, but it’s a pretty bad look.