Weird update loop burst behavior

Nifty rendering will be run on another thread some time, also Nifty will get more caching features internally, atm it literally regenerates each frame.

Alright then. I’ll keep an eye on those changes.

I proposed a plan for calming down a bunch of the nifty->jme churn a while back but I haven’t gotten around to implementing it. Right now the JME nifty layer creates a new BitmapText for each text element every frame whether the text is the same or not. It’s possible to reuse these from frame to frame when the text is the same and the code isn’t even that hard.

Mythruna only uses nifty for its menus and stuff right now. Nothing like overlays while the game is running so the performance has been a low priority for me personally… but still something I want to get to.