[QUOTE=paulv2k4;264359]
Ok, so I did some testing and came to some rough conclusions.
It seems this only works properly on a blank map and being run in a standalone process, in the editor window or (probably best) in a packaged game. Any other instance like “new editor window” drops the fps by at least 20 fps (in certain this is Slate/UMG issue). Put that with any decent size/complex map and your fps will soon become 10-20fps. (unchecking “use single process”, does not seem to improve this)
Also there is substantial fps dips occurring every 1-3 seconds bringing the fps down another 5-15fps, which is a little odd.
There seems to be a slight 0.5s - 1.5s pause between a mouse click/hover/interaction and the page actually doing something.
In that case I can not see this usable as a HUD but Menu UI will be fine as long as you keep the 3D background small (which games tend not to do anymore).
I do know that Slate (UMG) is incredibly slow too which could be hindering the process (the profiler proves this). This made me wonder whether I should put this on a plane to see if it improves things.
My concern is that if you were to ship the game and someone with a much worse CPU/GPU were using it, they would notice a more significant performance drop.
I hope we can get to the bottom of this. I am more than willing to help.
Thanks for looking into this and reporting all this information back!
I’ll run some tests on a complex map and see what I find. I don’t want to be fast to point fingers at UMG itself, but I think trying it on a plane would be a good idea to start with.
I currently don’t have access to my workstation for this weekend, but come Sunday I’ll be back at it.
I’ll also file an issue under the BLUI Github with the information you’ve provided!