Look Closer

[jc1]

The FOVToggle callback is lower case L. I got a problem with this. On the BMS Controller screen, when I press the lower case L, the Controller screen shows “Look Closer”. When I press the switch that FOVToggle is mapped to, the Controller screen shows “Look Closer”, but when I go in the game, my mapped switch does nothing. Pressing lower case L in the game does nothing. I uninstalled Falcon and reinstalled, but still got the same problem. I already posted about this problem on the “Joysticks & Input Devices”, “Warthog”, “Mud’s Profile” posts #208, 209, 210, 211, 212. But so far, there’s no fix. So I thought I’d try here. Hope somebody can help out.

[Eagle-Eye]

Looking at Mud’s profile, FOVToggle is assigned as “FOVToggle -1 0 0x26 0 0 0 1”. Looking at the list here, 0x26 is Arrow Up. However, looking at this list, 0x26 is L. As Mud lives in Belgium, and you live in the US, I’m guessing there may be a problem in “translation” between different keyboard layouts (AZERTY, QWERTY, QWERTZ, …)?

And not sure if it’s relevant, but there’s also “LoadCockpitDefaults -1 0 0x26 0 0x2E 4 1”. By the looks of it, key 0x26 is also used as a sort of activation key to load cockpit defaults (by first pressing Arrow Up, then Alt Delete on AZERTY; or L, then Alt C on QWERTY).

Have you tried assigning it as a DX-button in the key-file? I see you want the FOVToggle on your Paddle Switch, so I’d suggest you try adding this to the end of your keyfile and see if that works?

# Paddle Switch/S4
FOVToggle 3 -1 -2 0 0x0 0

[l3crusader]

@Eagle-Eye:

Looking at Mud’s profile, FOVToggle is assigned as “FOVToggle -1 0 0x26 0 0 0 1”. Looking at the list here, 0x26 is Arrow Up. However, looking at this list, 0x26 is L. As Mud lives in Belgium, and you live in the US, I’m guessing there may be a problem in “translation” between different keyboard layouts (AZERTY, QWERTY, QWERTZ, …)?

And not sure if it’s relevant, but there’s also “LoadCockpitDefaults -1 0 0x26 0 0x2E 4 1”. By the looks of it, key 0x26 is also used as a sort of activation key to load cockpit defaults (by first pressing Arrow Up, then Alt Delete on AZERTY; or L, then Alt C on QWERTY).

Have you tried assigning it as a DX-button in the key-file? I see you want the FOVToggle on your Paddle Switch, so I’d suggest you try adding this to the end of your keyfile and see if that works?

# Paddle Switch/S4
FOVToggle 3 -1 -2 0 0x0 0

The only relevant list of key <-> DX code for BMS is in your install folder, Docs->KeyFile & Inputs -> Keyboard Layout files. And in US Int, FR, and german keyboard, 0x26 is always L.

[Tiffy]

I would suggest the issue is with the LoadCockpitDefaults entry in Mud’s profile. Try commenting that out and see if the L key suddenly jumps into life. I think BMS is waiting for the second key press of this command and thus failing the FOVToggle command.

Just a thought…

[Kolbe-49th]

No, it has nothing to do with the LoadCockpitDefaults key assignments.

There is also nothing wrong with the Look Closer code line itself. That it’s working in the setup shows us, that the function is working properly.
If there would be a syntax error simply nothing would happen or, in worst case, BMS would crash upon entering the setup screen.

I think, one of the two following advices will help:

FOV increment / decrement / toggle (aka Look Closer) do only work in the 3d Pan Pit view [3].
It does not work in the 2d Pit Snap view [2].

FOV changes via key press or DX will not work if the TrackIR Z Axis Vector Mode is set to FOV or the Field Of View axis is assigned to a device axis.
Note: It can happen, that the DX device order and axis assignments get shuffled under specific circumstances. So it is not unlikely that
one of your physical device axis has been assigned to the FOV axis. This can be overlooked easily.

[jc1]

@Kolbe-49th:

…I think, one of the two following advices will help:

FOV increment / decrement / toggle (aka Look Closer) do only work in the 3d Pan Pit view [3].
It does not work in the 2d Pit Snap view [2].

FOV changes via key press or DX will not work if the TrackIR Z Axis Vector Mode is set to FOV or the Field Of View axis is assigned to a device axis.
Note: It can happen, that the DX device order and axis assignments get shuffled under specific circumstances. So it is not unlikely that
one of your physical device axis has been assigned to the FOV axis. This can be overlooked easily.

I took both of your advice.

1.
I “Look Closer” only in 3d view.

2.
My TrackIR is set for Z Axis Control. I don’t have the Field of View axis assigned to a device axis. For testing purposes, I removed all axis from BMS Avionics and for BMS Flight Control I had just the joystick and throttle axis. In the tmc file I commented out all my lines for joystick and throttle, but left the lines for DX23, BMS 22 for Throttle switch CSR. And then I tried the game, first with the keyfile, then with mapped keys.

//Keyfile controlled
FOVToggle 22 -1 -2 0 0x0 0
OTWSelectOrbitMode 278 -1 -2 0 0x0 0

//Mapped
MapKeyIO(&Throttle, CSR, PULSE+‘0’, PULSE+‘l’);

Both times, the FOVToggle switch did not work in game. The Event Tester showed the correct keys for the Mapped test. The Event Tester, correctly I think, showed no keys for the keyfile test, except ESC and E. In both tests, the ‘Orbit Mode’ worked in game, but the ‘Look Closer’ did not.

So I tried the joystick by itself and the throttle by itself. I assigned “Look Closer” to S3 on the joystick and it worked in game. Then I assigned “Look Closer” to CSR on the throttle and it worked. Of course, “Look Closer” should work on Thrustmaster Combined.

Hope you got more things I could try because “Look Closer” is a must have for me. Thanks for your help so far.

[Kolbe-49th]

So, Look Closer works on any DX button when not in combined mode but sucks if in combigned mode?

If this is the case I think I’m not of much help here as I don’t use a Warthog. Maybe Morphine knows a solution? Or sombody else?

What may work is if you try to program the “L” key via TARGET while using DX for anything else.

Edit: Ignore the grey part. I just read your first post again.

[jc1]

@Kolbe-49th:

So, Look Closer works on any DX button when not in combined mode but sucks if in combigned mode?

If this is the case I think I’m not of much help here as I don’t use a Warthog. Maybe Morphine knows a solution? Or sombody else?

What may work is if you try to program the “L” key via TARGET while using DX for anything else.

Edit: Ignore the grey part. I just read your first post again.

Thanks Kolbe for giving my problem everything you’ve got. I’m going to put my response to your advice on the “Joystick and Input Devices Forum”, hoping Morphine and Mud or anyone else over there can come up with something.

[Kolbe-49th]

I think, there is no need to post the very same topic in another sub forum.
Drop them a pm and point 'em to this thread.

[Mud]

I can’t really add anything to what I said in the release thread of my profile. I got it working myself fine on two different PC’s here, and I don’t think anybody has ever reported this problem before.
Only thing left to check if you haven’t done it already is try the stock BMS keyfile and see if the keyboard command for look closer works then.

[jc1]

@Mud:

I can’t really add anything to what I said in the release thread of my profile. I got it working myself fine on two different PC’s here, and I don’t think anybody has ever reported this problem before.
Only thing left to check if you haven’t done it already is try the stock BMS keyfile and see if the keyboard command for look closer works then.

I tried one more time to uninstall Falcon and got a new “BMS - Full.key” file. IT WORKED. All those guys who responded to my situation kept me motivated. Thank you all very much.

[jc1]

The fk* problem is back.

[taotoo]

Is your FoV at the default?

[jc1]

I got the “Look Closer” problem fixed. It had to do with the Field of View setting in BMS Settings/Controller/Advanced/View Control. With the hope that nobody else has to make this frustrating mistake like I did, here is the cause and the solution:

Cause:

Solution: