Solved [4.36] Mouse Scroll No Longer Alters Cockpit
-
Not sure if I flubbed a setting, though I’ve looked all over and can’t find one for this. In 4.35, if I placed my cursor over a cockpit knob and moved the mouse scroll, it would alter the knob, otherwise it would zoom; in 4.36, it does nothing other than zoom.
Minor annoyance that mostly only impacts my HSI function, but still.
-
@PotatoPilot Aah, you didn’t understood me, … I wanted picture when you place mouse cursor over the button, so .I can see to what type cursor change , is it “plus/cross” or “two rotating arrows”… for HSI or any “rotating button” where wheel operation is possible it should have those “curved arrows”.
- that is beacause I don’t know what pit was it , if F16 pit then it should be Ok, like I’ve said , but for example in F18E/F pit some rotating switches are not working… as not complete pit, not 100% functional
But I suspected it was setup/config thingy… Thanks to @airtex2019 .
Good, cheers
-
@PotatoPilot … did you alter (assign) mouse-wheel axis to some other function in setup/config screen … is wheel working at all ? Have you edit falcon bms.cfg regarding axis setup ? Is this cockpit button working with wheel at all ?
You haven’t specified what plane/cockpit , what theater was this happening in… picture of the cursor above button which is not working with wheel would help., video clip, even better.
Just from this text would need a crystal-ball to figure it out, exact problem.
-
First check the specific setting in your falcon*.cfg files:
set g_bMouseWheelKnobs 0
There are some less obvious cfg settings to look for, too… I don’t know if mouse-wheel-knobs works, if you specify any callbacks for these.
set g_sScrollUpFunction "FOVDecrease" set g_sScrollDownFunction "FOVIncrease" set g_sMiddleButtonFunction "FOVDefault"
Then, as white_fang says, check all the axes in the in-game Setup to see if any have been accidentally assigned to mousewheel.
HTH
-
@airtex2019 said in [4.36] Mouse Scroll No Longer Alters Cockpit:
First check the specific setting in your falcon*.cfg files:
set g_bMouseWheelKnobs 0
There are some less obvious cfg settings to look for, too… I don’t know if mouse-wheel-knobs works, if you specify any callbacks for these.
set g_sScrollUpFunction "FOVDecrease" set g_sScrollDownFunction "FOVIncrease" set g_sMiddleButtonFunction "FOVDefault"
Then, as white_fang says, check all the axes in the in-game Setup to see if any have been accidentally assigned to mousewheel.
HTH
Hi. This value is 1 in my settings (the mouse wheel rotates the knobs).
set g_bMouseWheelKnobs 1 // Allows mouse wheel to turn knobs in 3d pit
I think the second group of settings are not related, the knob rotation and FOV change do not interfere with each other (the wheel change the FOV or rotate the knob, based on where you point the mouse)…
-
@white_fang
Wheel works for FOV. The wheel does not work over any buttons on any pits I’ve tried. Korea. None of the buttons work. The video would be of me placing a cursor over a button and nothing happening.@airtex2019 My cfg has:
set g_bMouseWheelKnobs 1
I cannot find the other 3 lines in the .cfg file.
The flight controls are all non-mouse. The mouse is selected for FOV only in-game settings. -
@PotatoPilot said in [4.36] Mouse Scroll No Longer Alters Cockpit:
The mouse is selected for FOV only in-game settings.
Ah ha! that’s your problem. I think this has caused confusion in the past.
Change your fov axis to just be “keyboard”. The mousewheel behaviors are kinda hard-coded … overridable via the cfg lines I referenced earlier. But coded by default to do what you want.
-
@PotatoPilot Aah, you didn’t understood me, … I wanted picture when you place mouse cursor over the button, so .I can see to what type cursor change , is it “plus/cross” or “two rotating arrows”… for HSI or any “rotating button” where wheel operation is possible it should have those “curved arrows”.
- that is beacause I don’t know what pit was it , if F16 pit then it should be Ok, like I’ve said , but for example in F18E/F pit some rotating switches are not working… as not complete pit, not 100% functional
But I suspected it was setup/config thingy… Thanks to @airtex2019 .
Good, cheers
-
@airtex2019 Thank you! That’s the trick. Yes, it’s very confusing.
-