Vehicle control with the mouse is fundamentally broken!

Dear Devs
There is a big problem for all mouse users since BeamNG.drive version 0,37!

Symptoms:
If you move the mouse over the edges of any apps, data contact with the brake/gas and steering is lost and set to neutral until the mouse generates new input for that axis regardless if you are in or outside of the app-area. It only affects the borders of any apps. If this happens in addition within a controller dead zone, contact remains lost and neutral because no new mouse data is produced. If this happens at the very edge of the screen, where an app's border is placed, contact also remains lost.

Impact:
In practice, this means, for example, that braking is abruptly interrupted if you reach the bottom of the screen or your mouse dead zone and you have placed an app there. Other situations involving steering are just as dangerous! The pedals and steering, depending on which axis is affected, are only activated again when you try to "shake" the mouse into a zone that generates new input, what ends the journey in a fatal way in most cases.

This state makes normal driving with the mouse virtually impossible! Playing with BeamNG.drive using the mouse, which is my favourite input device, is suddenly over for me. I cannot drive and play any more . The only option is to remove all apps, but that makes driving difficult for other reasons.

I would be very grateful if you could tell me if you have this problem in focus, because it is very important for all mouse drivers. I urgently beg for your response.

 

ive seen games set it up that mouse controls are a thing you have to enable by pressing a key that temporarily removes all other mouse functions unless you disable mouse steering by pressing that key again hopefully the devs can implement somthing like this

 

Update:
I've investigated a little bit with the help of the html engine DevTools and wrote some listener code which gave me some more information. So what I can say now is:

More exact symptoms:
Those "Axis Drops" occur not at some border element or wrapper arround each app. They occur only on enter into the app area what means, if you move into the area of an app, the vehicle control is lost as long as no new movements per axis are produced. If you enter and move exactly horizontally then the vertical control (brake/throttle) is lost whereas the horizontal axis (steering) recieves permanent changes and thus updates continuously. If you enter the app vertically than the steering is lost and brake/throttle continue to work.

My first idea was, that some kind of html pointer-event is swallowed by an app surrounding object (wrapper). but that isn't. Is seems to me more that some bridge between the html UI and the car control (mouse > engine bridge) has some kind of update logic bug. (logical AND instead of OR for delta_x/delta_y for example).

Hope that is usefull and can halp to solve the issue.

 

Although I don´t use the mouse for driving personally, this is a major issue for all players that do. Devs must definitely look into this.

 

Driving without an UI is obviously a rather poor option, as many displays are important while driving. Or roll back to 0.36? I don't know how many mouse drivers are out there, but if you're reading this, I'd be interested to know how you're currently handling the issue.
--- Post updated ---
Update:
The issue occurs with all user interface elements, not just apps. I didn't noticed it before because the game normally pauses when you open the main menu.

With the UI Elements of the World Editor (with driving enabled) or for example the little settings "app" for grid map, mouse control is always blocked/locked what seems more intentional than the behaviour with the other UI elements.

I really hope the developers take note of this and there can be some kind of solution for this.