Has anyone ever rolled their own UI in C++ with AHud::Draw() functions? It wouldn’t be too complicated. DrawText(), DrawTexture(), and DrawMaterial() would get you 90% there.
Could compose the HUD WPF Xaml style but with C++ only. Zero blueprints needed. 
Visual designers shouldn’t have to screw with c++ or xml. If I am looking for some adobe or figma guy for UI and UX I’m 99% sure it is not someone programming because a good combination appears to be rare. I’d personally get rid of the binary files and UMG with fire and prefer a text based approach similar to CSS, or an editor writing that “CSS”. It’s an entirely different topic though. If the team just perfects the core that is under UMG (Slate) and stops breaking it / not testing it, then a lot of the frustration with both systems would already be gone.
Look at how I handle my widget design for Melonade , it’s pure and simple no nonsense css. doesn’t get any cleaner. I don’t need 5 editor windows and bloated UAssets to make an app.
Try doing that in UMG and compare the effort and amount of data on your disk to the few lines of css I wrote there (did not even use textures!)
So no response and currently the Bug Reporting category has been closed for non fortnite users. Soooooo…
@DoubleDeez This guy is an engineer handling UMG
I don’t know but the forum activity of that profile is not promising. I’d at least have expected some response from it on this thread.
Besides, I want to bump this post up a bit on the forum list because a lot changed around UE5.5.4 . Unaware of what got fixed and what bugs (usually) were introduced on the Slate side.
And honestly, I don’t care about Enhanced Input or Common UI. I don’t use them and don’t need them. I built my system using a UMG HUD as a central manager for nested menus, input modes, cursors and improved focus control. I think of Enhanced Input and Common UI as two steps sideways and 3 steps backwards. Perhaps more of a marketing move than a functional product.
What I confirmed through version control is fixed in 5.5.4:
What is most disappointing is the focus on Fortnite bugs, for which the forums has a full adaptation and even bot assistance to process the bug reports. “Normal” Unreal Engine users can not use this. The bot does not process such reports and there is no feedback on attempted reports.
By now, I had expected the forums to be bot assisted for reporting UE non fortnite related bugs. Why? Because bugs reported through the official way end up on the pile of literal millions, while on the forums we can help eachother out and build more detailed feedback in public. Bugs reported through the official way gave me no feedback at all. Think of it. One guy introduces an engine bug, hundreds? thousands? of us UE developers spend X time debugging the same thing. And why should we? Put it on the forums.
AND EPIC, test it properly in the first place. Some bugs are so ridiculously easy to detect they are insulting: (“add a slider widget, drag the handle around, oh it doesn’t work”). How can you not write a test for that or spend 2 minutes to do by hand? No, let 5000 devs spend 30 minutes on it reading that insulting code, that seems fine?
By now, we’ve had bots capable of summarizing and linking one post’s content to another (of any website) for at least 10 years, probably double or more. Look at github for such AI which are widely available and can be used on home (potato class) hardware. The forums has actually had quite a few bot accounts invading posting summaries of what a real user just posted seconds before.
The bug reporter and bug form on this forum is exclusively used for Fortnite, which makes clear that Epic is not focusing on innovation, as they continue to release experiments into the wild without collecting feedback. Therefore their focus is not on improving a user experience, developer experience, or improvement on support, services and Unreal Engine as a product.
When bugs are reported, there is no feedback. When bugs are fixed, there is no feedback. When bugs aren’t fixed but pushed aside, we see posts dating back to the early UE4 popping up on the forums occasionally.
i think this is a more general issue than umg.
though i agree, ideally umg should have new bugs on every release.
i think the whole engine tend to many new bugs on each new release. and it’s noticeable.
it did made me question whether their qa process is up to the task.
i wish they could improve their qa. though i think the LTS version would be the ideal solution.
i also agree there seems to be issues with communication. specially the apparent lack of communication from epic.
reporting bugs has a ton of friction, and doesn’t seem to be effective. i had many issues with the form that made me just skip reporting an issue.
the fact that i’ve came across this post by accident, 2 years after being posted, makes me think there are issues with discoverability in the forums too.
there seems to be a lot of noise as well with ai posts, spam, and now that there are many subforums.
i do think it’s cool to have a centralized place to discuss all the aspects, but it also seems to be hindering discoverability too. and some stuff is just spam/noise.
there’s imgui for ue5 if that helps. GitHub - SLSNe/Unreal5-ImGui: UE 5.4+ Dear Imgui library with latest IO
