i have two predictions or really hopes and dreams, of what the next update could be: 1, the (Good as new) update which is a huge update that includes many remasters of the older cars like the miramar that would have a wagon and a coupe variation, the barstow that would have a convertible option and maybe a four door, the etk i series which would get a coupe and a facelift, the moonhawk that would get a wagon, sedan, limo, and a facelift, as well as a firebird or Hawkeye variant that has a T top, and in the update a new addition to career mode buying cars from auctions that are in terrible shape and restoring them little by little, also it has a remaster for all the beater configs adding very realistic looking dirt and mismatched panels, and lastly an addition of a junkyard to wcusa, 2, the (heavy duty) update that adds a remaster to the t series and the wentward and the new addition of the subway train the first train in beamng that you can drive and crash, and since the train tracks are finished at wcusa it would be perfect to drive the train all the way from the city to the island also the update adds multiple construction rigs to crush cars with, and lastly many new career mode things like being a train, or bus driver, now these are just my imagination so take them with a grain of salt,
in my opinion it would be cool since we dont have a 50-60s sports car but i dont think it'll be added for a while because we just got the updated civettas not to long ago, also if we do get a heavy duty update i think it would be cool if they added a school bus flat nose and long nose, and the addition of a school because if im not mistaken beamng doesnt have a school,
i would love a version of beamng used in schools to show the dangers of driving like an idiot or in collision repair classes to show what crashes cause what damage
If any devs see this, please can we have a quick update on whats going on concerning the UI? Wasn't it meant to be getting ported from HTML to a new system? Would love to know as the UI has felt sluggish for years and years and having something snappy at last would make the game feel dramatically better almost everywhere
I'm quite confident they'd tease anything about it already if they had any progress on it. Beam is made using CEF, and I'm afraid there isn't a silver bullet that will fix the sluggish UI, as the whole thing is simply not made for this. Moving to a new UI would literally mean reworking it from the ground up, which is something I don't expect them to want to spend time on either (though better now than later in the career mode development cycle).
I definitely remember they said that [them moving to a new UI system] was happening though and was in progress. This was a long time ago though, I don't know whats currently happening regarding it (hence why I asked) --- Post updated --- Where are schools finding PCs that can run beam :skull:
There's no magic bullet, no simple solution. Parts of the UI have already been migrated to Vue. A big part of career UI is made with Vue for example. And there's more to be done. In any case it all uses CEF under the hood, where we're working on trying to achieve some optimizations. With some luck, the optimizations might actually work, but will likely be quite small impact. Optimizing it further, or replacing it entirely, is a complete different beast of a monumental task... so despite our ongoing efforts and research in that direction, I gotta advice to not hold your breath. Rest assured we suffer the very same pain, we want a better, faster UI the same as anyone in the community. We're doing what can be done within our means.
He has been moreso inactive due to personal reasons. While he is still involved with the project it isn't on the same scope as back in 2013 when the project started out, or at least not visibly here.
Does CEF have an inherent overhead that is causing the performance issues with the UI? In my experience as a React developer, UI rendered in a regular browser is generally quite performant given that your UI code is well optimized and not causing unnecessary rerenders (memoizing helps a bit here). Granted, the BeamNG UI is more complex than anything I've worked on. Perhaps there are inefficiencies integrating the browser engine into the render pipeline? Also I've noticed that when I run the UI through a browser using the "Enable Browser UI" option, the performance is as fluid as butter. So this leads me to believe that the problem does lie with how CEF is integrated. Another question: What is the reason for switching from Angular to Vue? Is there potential performance improvements and/or improvements in code readability?