4.35 Buttons on HOTAS/sound stops working in 3D
-
After a flight, second flight in 3D i either experience loss of sound or the buttons on my joystick & throttle buttons stop working (not the axes/analogs, those continue working fine). The issue can be fixed by restarting the game. I know it is not my joystick & throttle because one of the buttons on my throttle is tied to track ir centering and that still works while in 3d, meaning its not my peripherals acting up. Also, in the setup>controls menu the buttons do work. It seems the issue is when i go to 3d the 2nd time or third time. Also, sound stops working from time to time in 3d, i have to exit out of 3d, go to 2d, and back to 3d and sometimes that fixes it. the sure way to make all work is to restart the game each time after 3d but that is very inconvenient.
-
In my experience, losing sound and input from HOTAS buttons and keyboard usually means the 3D output window has lost focus, and quickly fixed by either a left mouse click on the sky or a cycling of ALT-TAB to refocus on the window.
-
After a flight, second flight in 3D i either experience loss of sound or the buttons on my joystick & throttle buttons stop working (not the axes/analogs, those continue working fine). The issue can be fixed by restarting the game. I know it is not my joystick & throttle because one of the buttons on my throttle is tied to track ir centering and that still works while in 3d, meaning its not my peripherals acting up. Also, in the setup>controls menu the buttons do work. It seems the issue is when i go to 3d the 2nd time or third time. Also, sound stops working from time to time in 3d, i have to exit out of 3d, go to 2d, and back to 3d and sometimes that fixes it. the sure way to make all work is to restart the game each time after 3d but that is very inconvenient.
Never go on 3D a second time.
-
I had the same issue with the buttons not being recognized anymore while the axes were still working (didn’t notice losing the sound, however).
It happened now three, four times since 4.35, and I still don’t know what causes this. But I am sure that it was the first flight in 3D after starting BMS and I didn’t Alt-Tab out of BMS either.My first thought was that somehow the dx-shift state was stuck when that problem arose. But I wasn’t able to clearly reproduce it yet in a defined sequence of actions.
-
I tried alt-tab and focusing on the window initially but it didn’t fix it either. The keyboard works and the axes work but the buttons on the stick and throttle just stop working.
-
I have experienced the same problem: at some seemingly random point, normal key presses stop working, including both mapped from Hotas and also keyboard functions. The axises and dx buttons still work, as do pushing buttons in the 3D cockpit using the mouse. I can’t reproduce the problem in any particular situation so far, but I can confirm it has happened in the first flight in 3D. I may have saved minor changes in a “stock” TE before entering 3D, such as time of day and/or weather. In any event, based on prior experience it feels like a key press may be getting stuck, which seems to allow dx buttons but not other key presses. Is there a way to see a log of key presses? I think that could help…
-
also, what I can add to my previous post: I have a couple of “permanent” DX buttons, i.e. callbacks that are triggered when a button is pressed and others that are triggered when a button is released, e.g. MasterArm mapped to a single DX-button. Maybe this kind of mappings adds to the likelihood of the problem occurring.
-
That may have been true decades ago, but back when I was in bms development, I wasn’t even going back to desktop even if I was changing some data file (3dbuttons.dat for example when we were converting coordinates for 6dof support with g_b3DClickableCockpitDebug). I’d just alt tab, put coordinates, go back in 3d, next repeat as necessary. Given the number of hotspot, I don’t think I need to tell you how many time I switched 2D/3D/desktop without restarting the game even once to finish those damn files…
@LorikEolmin:Never go on 3D a second time.
-
That may have been true decades ago, but back when I was in bms development, I wasn’t even going back to desktop even if I was changing some data file (3dbuttons.dat for example when we were converting coordinates for 6dof support with g_b3DClickableCockpitDebug). I’d just alt tab, put coordinates, go back in 3d, next repeat as necessary. Given the number of hotspot, I don’t think I need to tell you how many time I switched 2D/3D/desktop without restarting the game even once to finish those damn files…
Then it’s back to where it was decades ago.
-
I think i figured out what the problem is, i think i had my pinky switch set to the dx shift by accident and didn’t have a seconded call back mapping, after i i unbound the pinky switch to the one without dx shift in the keybinds its working every game now. I haven’t had the sound issue either so far.