Cursors
-
Need HELP!
When FLIR is pulled up, how do I align? My mini cursor on throttle just moves mouse cursor. Out of training manual…“Align the FLIR HUD terrain on the mountains you have visual with the cursors.” How is this performed?
Thanks for the help…btw, not really computer savvy.
-
I always forget how. From page 77 training manual.
Level out, zoom in on the HUD, place the FLIR in operate and press BSGT
(OSB 10). The mnemonic of the OSB highlights and the FLIR image on the HUD can then be moved with the
cursors so it matches the item you see on the HUD. Align the FLIR HUD terrain on the mountains you have
visual with the cursors. Once satisfied exit the boresight mode by pressing BSGT again (BSGT is not
highlighted anymore) and turn the FLIR back to STBY for now. -
How do you operate cursors?
-
the same control that moves the radar cursor
-
I tried that, it just moves the mouse. I have the Saitek X52 Pro.
-
Ah the computer mouse. Yeah X52 will do that depending on the profile software setting. You’re going to need to change over the function of that control in the joystick software to do buttons or axes and then assign those buttons/axes to cursor function in Falcon.
-
Now the big question if I may. How do I change that function? I myself am not computer or program savvy. Another question if I may, what’s your opinion on the X56 Pro? Will I have the same issue? Thanks for all the answers to my questions though.
-
As the X56 is 2 seperate devices you can at least use the ministick as analog axis without having to use a registry mod like on the X52/pro. But giving up an axis and use the ministick on the X52 in its best way as analog axis is not harder than to execute a reg file
Gesendet von meinem SM-G930F mit Tapatalk
-
First sir, thanks for reply from both you and Frederf. But I’m still confused as I’m not than savvy with programming. Also, my X52 is also 2 separate devices, am I missing something? Do appreciate the help! I got lost at "execute reg file. Next to the mini stick is a button that says Mouse Fire DX:15
TQS: Radar Cursor - Enable
TQS; RDR Cursor - Cursor Zero
But I see no affect when pushed.Thanks again
-
Does anyone known the X-52 Pro enough to answer that? My memory from X-45 SST software is that in the profile you right click on the row corresponding to the control and choose, mouse, bands, axes, hat, etc. how it performs. Saitek has changed companies 2x since then and the software refaced (although largely the same at its core).
If you’re not using the profile software it might just emulate mouse by default in which case changing behavior would require you to start.
EDIT: The registry file changes settings in the Windows Registry which I guess alters the default device behavior. I wouldn’t worry about the joystick behavior in BMS until you’re happy with its behavior outside of BMS. The game layer is perhaps another source of confusion. There is a dialog called Game Controllers which has become harder and harder to find as Windows changes. In latest you can search in the start button for “Set up USB game controllers” or from the Run dialog run “joy.cpl”. From here you get a view of how Windows understands your joystick.
-
Once you are in the game controllers window, select the MFD tab and make sure clutch is deselected - this so you can use devices with DX.
With regard your comment about x52 pro being 2 devices, I’m assuming the flight stick and throttle are joined by a cable but plugged into your computer by a single used cable? This is view as a single device.
I’m not at my computer now, but I can post some details about Registry hack later - unless someone else jumps in.
-
For a X52pro in order to provide a registry file file the user first has to identify the version of X52pro he has. In order to do so
1. In you windows search bar type regedit and click on the Registry editor app icon (screenshot 1)
2. once the registry editor is open navigate to HKEY_CURRENT_USER\System\CurrentControlSet\MediaProperties\Joystick\OEM (screenshot 2)within that path you find either a folder named VID_06A3&PID_0255 or VID_06A3&PID_075C
where VID_06A3 is the manufacturer ID and PID is the device for the X52Pro the PID is different between those made by Saitek and those made by Logitech. In my screenshot I have both ( in order to edit and create reg files for other others)
So on a system with an X52pro installed you will have only one of both.Once you prove wich PID you have so either 0255 or 075C someone might provide you a regfile to reorder the axis and get the ministick to be used as analog axis
-
Thank you much! Looking forward to the help. Question does the X56 or X65 have the same programming issue? I was thinking of purchasing either or, your thoughts please?
-
I have the X65F (and love it BTW) and the X52
apart of beeing a Force Sensing Stick (which for me personally is a total game changeer for flying BMS) the programming is pretty much the same as with the X52 as X65 doesn’t have the slider as the X52 but a dual throttle you still have the issue with having 9 axis but windows DX only recogizing the first 8. In addition the X65F has more buttons (50) than the X52 and therefore needs either a mixed setup of DX and keybind through profile software or the use of vJoy and Joystick Gremlin to split it up into 2 virtual devices.X56 is a different story as there the throttle and the stick are 2 dicives on it’s own so AFAIK no issues with number of input limits per device
-
Being that I’m not program savvy, it sounds like the x56 is the one for me? Meaning I should have no problem with radar cursor. Great advice
-
Hi Steel,
So you are going to look to purchasing an X-56 or do you still require assistance with the X-52 Pro? If the latter then if you can let me know which version of the X-52 you have(following Oakdesigns instructions) and which inputs on the device you want to use as DX I can help you create a registry record for your device.
This is what I used to set up mine (you will see that I’ve forgone the Slider for a working twist rudder (Axes 8, the ninth, is not recongized by BMS).
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762]
“OEMName”=“Saitek X52 Pro Flight Controller”
“ConfigCLSID”=“{A1902D8A-F8C8-483b-A5E3-D4FCB47CB264}”
“OEMData”=hex:03,00,88,11,27,00,00,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes]
[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\0]
@=“X”
“Attributes”=hex:01,81,00,00,01,00,30,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\1]
@=“Y”
“Attributes”=hex:01,81,00,00,01,00,31,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\2]
@=“Throttle”
“Attributes”=hex:01,81,00,00,01,00,32,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\3]
@=“Rotary 1”
“Attributes”=hex:01,81,00,00,01,00,33,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\4]
@=“Rotary 2”
“Attributes”=hex:01,81,00,00,01,00,34,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\5]
@=“MiniStick Y”
“Attributes”=hex:01,81,00,00,05,00,26,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\6]
@=“Rudder”
“Attributes”=hex:01,81,00,00,01,00,35,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\7]
@=“MiniStick X”
“Attributes”=hex:01,81,00,00,05,00,24,00[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\8]
@=“Precision slide”
“Attributes”=hex:01,81,00,00,01,00,36,00 -
Being that I’m not program savvy, it sounds like the x56 is the one for me? Meaning I should have no problem with radar cursor. Great advice
If you have an X52 Pro, you can try one of the premade control setups in the forums here, mine and others have instructions for creating a working radar cursor out of the mouse mini-stick on the throttle. My own ‘Falconeer’ profiles make use of the ‘bands’ method so I don’t sacrifice any axes - still have all the toys from analog twist rudder to throttle slider for the speed brake & dials for the FCR range/ele.
If I were you, I would try one or more of the premade offerings before dropping money on the issue that could be better spent on other useful flight sim gear like Thrustmaster Cougar MFD’s or a precision head tracking device like TrackIR.
-
Appreciate the reply and that may work using a premade control setup. I do appreciate the help from all.
-
If you have an X52 Pro, you can try one of the premade control setups in the forums here, mine and others have instructions for creating a working radar cursor out of the mouse mini-stick on the throttle. My own ‘Falconeer’ profiles make use of the ‘bands’ method so I don’t sacrifice any axes - still have all the toys from analog twist rudder to throttle slider for the speed brake & dials for the FCR range/ele.
If I were you, I would try one or more of the premade offerings before dropping money on the issue that could be better spent on other useful flight sim gear like Thrustmaster Cougar MFD’s or a precision head tracking device like TrackIR.
Agree with everything apart of TrackIR as that’s money thrown down the toilet. There are better and way cheaper solutions.
If you don’t want to go the DIY route go for a Delanclip setup for headteacking. 1/3 of the price and better performanceGesendet von meinem SM-G930F mit Tapatalk
-
I really can’t thank you gents for all the advice and help. I’m going to give both SemlerPDX and oakdesign a try. Thanks also to CriticalMass.