Why did the UI become so unresponsive after 0.23?

Basically, before 0.23, my UI usually would start dying on around 6-7 cars with a bunch of props, yet after 0.23, my ui literally gives up on around 3-4 cars, sometimes even when I only have 1 car spawned. This happens both with and without mods.
here is an example for the UI literally dying on me, this time its only 1 car, but it should show how bad it can get sometimes.

 

It was like that in earlier releases as well though...

 

at least it wasnt this bad, i literally only had 1 car spawned and it was acting like i had 10 of them spawned in in previous versions

 

106301 is the id which it gave me, game ran in safe mode, spawned around 4 cherrier vivaces, UI started dying again

 

I have actually noticed the same thing... but for me, it seems to be some sort of Ram leak... and the more Ram Beam starts to take up, the slower and slower the UI starts to run. This happens over the course of a Half hour to an hour of play time, and I never have more than one vehicle in the game as I am usually just constantly respawning that one vehicle (building mods)

The UI gets to the point where it can take over 5 minutes for it to respond to an action that I make. Under the surface it appears to be doing what its supposed to, as when the UI is opened into a menu, my controller is unable to upshift (no idea why) however, if I press Esc, I become unable to upshift with the controller immediately as if a menu is indeed open, but it just doesn't show up for a good 5 or so minutes.

When I finally got fed up with it, I checked out the task manager just before shutting down Beam and it was using over 22GB's of Ram. Normally Beam only used about 4 to 6GB's, and I understand that it got a new render system... but that seems excessive and I would be willing to bet part of the reason that the UI was running like it was.

 

checked right now, seems the same as you just told here, usually my game is at 4-6gb, then it goes up to 12-14, and after like an hour of the ram leak, the game just closes and i have to re-open it.
Seems as if beamng has really bad ram leak problems

 

thank you so much

 

Out of curiosity, what constitutes low FPS? The only reason I ask is because my machine usually is running 60+ pretty much all the time pretty easily. The UI FPS has always been somewhat choppy... if I had to guess it looks to be around 30 FPS, but Beam itself (like... vehicles, the environment... anything 3D) has always seemed to run very well and easily is far and above 60+ FPS.

 

0.23.3 hype.
yeah its worse in lower end hardware, i run beam with 4Gb of ddr3 at 1600Mhz, Which, yes is below recommended, but never caused any 'major' issues like the UI freezing, sometimes the game refused to even start, as the previous verons (0.22) ran fine.. will be waiting for the hotfix! Thanks!

 

Ahh... well that explains that then. I did go back and take a look at my game and how many FPS it was really running.

Max seemed to float anywhere from 100 to 130
Average seemed to be about 70 to 90
10% Mins seemed to be about 40 to 50

However, having said that, watching the actual FPS counter, despite the game feeling very smooth at all times, the FPS counter itself was all over the place. Sure, a lot of the time it bounced up around the 100's, but many times it also spiked downwards into the teens a lot. I never felt any of these "drops" despite the FPS counter claiming they were happening for at least one frame. But according to the FPS counter it was happening all the time, like, roughly 3 to 4 times every couple seconds. So perhaps that is why I am experiencing this issue.

 

i presume this was the ingame fps counter?
how does it look in MSI afterburner? because you can set the refresh time and get a much better avg fps result

 

So it's memory leak, that may explain why UI often lag over time. I only have 8GB RAM but I never had any laggy UI from 0.13 to 0.22, including Italy and American Road.

 

Yes it was with the ingame FPS counter. Using MSI it claims that my FPS is much more steady around 68 to 72FPS on average.

 

I found a surefire way to trigger the UI lag. Simply spawn up the AI Control UI app, then the UI drops to less than 2FPS immediately, removing the AI control still 2FPS. Switching map doesn't help, the only way to clear the lag is to restart the game.
Hilariously even the FPS counter refreshes faster than the UI.

Please watch this video, note the tachometer in the vehicle and compare to the UI tach. The FPS is 30 because of recording, when not recording my computer can run Italy at 50~60 FPS without problem, the UI is laggy regardless.

 

Fixed for me, now the UI works like intended, thank you very much