4.33 mouse wheel keymaps issues (FOV + ckpit wheel knobs)
-
4.33 64bit
Setting FOV in settings to mousewheel creates two bugs:
- Upon entering 3d the FOV is crazy close to the HUD.(think look closer keymap)
- Lose the ability to interact with the mouse wheel on the wheelknobs in the ckpit
Been searching for reports of this issue and found one in the thread “Anyone else had this mouse issue?”. The solution there suggest to return the function to keyboard. I would like to be able to use the mouse wheel for said operations.
-
Something goofy with your issue as I use mousewheel for FOV and have no issues like what you mention (I also have 64 bit 4.33). If you have TIR, you can set FOV to TIR (in advanced settings in setup in BMS) and thus maybe eliminate this problem.
-
I desperately need TIR. That’s for true. Perhaps there is something that’s gone wonky. I can’t think of anything as it should honor those settings. Atleast, for those who unfortunately don’t have TIR.
-
well the close up hud is fixed in the Falcon BMS.cfg file there are 2 FOV Settings in there.
…user/config/falcon bms.cfg -----open in notepad++
-
well the close up hud is fixed in the Falcon BMS.cfg file there are 2 FOV Settings in there.
…user/config/falcon bms.cfg -----open in notepad++
Neph, I use the mousewheel to resize the level of zoom on the HUD view, but it (the mouse wheel) has no change on the zoom level when using the Extended FOV. When entering Extended FOV The HUD part is way too Zoomed in to be of any use. Will this .cfg file allow this to be correctly sized, or does someone have an idea of how I can change this in Extended FOV? Thank you.
-
Neph, I use the mousewheel to resize the level of zoom on the HUD view, but it (the mouse wheel) has no change on the zoom level when using the Extended FOV. When entering Extended FOV The HUD part is way too Zoomed in to be of any use. Will this .cfg file allow this to be correctly sized, or does someone have an idea of how I can change this in Extended FOV? Thank you.
Well I am unsure what you are talking abour sorry I cant be of any help but perhaps a video or pic could help us that don’t understand??
-
I’m afraid I’m not that pc saavy! There is a feature keystroke called EXTENDED FOV A-A (in BMS full key file it is SHIFT + 5). If you have an enemy padlocked, you can hit this key and the HUD view appears with a small box showing the view of the padlock target - there also is a cue as to where the target is. The problem is that in the HUD only view of this EFOV A-A the Altitude scales, header tape, etc., all the things that are on the HUD appear in HUGE size, thus you really have no FOV. In the mode the mousewheel will NOT adjust the size of the HUD down so that I actually have a nice FOV to fly the jet with. I hope this explanation is better.
-
Sorry hadn’t had time to fly but did a couple of tests and verified both the problem and solution. By default, the mouse wheel changes FOV so there isn’t a need to change it. Enabling the option in the key strokes Advanced Settings causes the issues I described above. The solution that tklineage posted in the https://www.benchmarksims.org/forum/showthread.php?17501-Anyone-else-had-this-mouse-issue thread works.(Setting the fov back to keyboard)
Of course, this is for those who don’t use TrackIR and the likes. I still don’t have this must have device.
