Cursors
-
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.
-
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 performanceSo true!
Just shooting the shit on the subject, gotta say IMHO the term ‘better’ is subjective - there are definitely way cheaper solutions for those on a budget, for sure, but cheap/DIY/expensive aside, they all work very well for the situations they are designed for (clips/hats/cameras/IR sensors). If on a budget, TrackIR is not the head tracking solution to shoot for!! Back when I bought it, it was pretty much the only mainstream solution or option, and I’m no shill - pilots should definitely get what works for them and their wallet.
My 2 Cents on TrackIR… these days, if I didn’t own TrackIR, it would be hard to justify buying one when building one or finding a budget solution was an option, but now that I do own it, if it broke, I would replace it just for the familiar software interface and all the custom curves and controls I set up for various sims or games I use TrackIR for. I try not to be biased simply because this has been my tracking solution for ten years, but I do want to point out that for the money, it’s not wasted depending on what you value - it truly is the smallest form factor purpose built for aiming the clip and sensor at each other out of any solution (besides face tracking and a standard web camera), and the TrackIR software is tip-top notch and quite easy to program for custom curves and hotkeys on a per-game basis.
Hardware often requires some level of software for additional functionality or customization, and preference for a particular GUI or software program features can be subjective when all other functions are fairly well on par with other hardware solutions. Like most things, you learn the most and have the most control doing it yourself or building your own solution. If money is not the decider but form and function first, the products range from simple to fancy, smallest possible form factor to general DIY designs, with simple to fancy software.
@Steel - Whatever works for you and your budget will do just fine, the differences between the products/methods are quite minor and sometimes personal preference (someone who doesn’t like wearing hats may want to avoid a solution which forces wearing a hat, for example).
-
Sir SemlerPDX,
I went completely with you and got the TrackIr. I got everything up and running except one issue, my pinky wont shift when I try to lower gear or eject and so on. Is it my flight stick or did I do something wrong following your directions. When I check it in the game it shows pinky working. Also, my slider does open and close speed brakes but it also moves my FOV. Again, thanks for the help and advice. Mini also is working correctly now to!
-
(received private message of same, replied there - best wishes - I’m sure the Pinky issue is something simple, just can’t think of what is causing that off the top of my head right now)
-
Sir SemlerPDX,
I went completely with you and got the TrackIr. I got everything up and running except one issue, my pinky wont shift when I try to lower gear or eject and so on. Is it my flight stick or did I do something wrong following your directions. When I check it in the game it shows pinky working. Also, my slider does open and close speed brakes but it also moves my FOV. Again, thanks for the help and advice. Mini also is working correctly now to!
Have you mapped the shift-layer to the Pinkie in the SST Programming software?
-
Have you mapped the shift-layer to the Pinkie in the SST Programming software?
Since he seems to be using my ‘Falconeer’ profile for X52 Pro the Pinkie Shift is handled in DX directly in the binds file, and the profile in STT should have only 1 layer, and Pinkie as ‘Unassigned’ to work as a DX button. The throttle slider actuating speed brake would mean BMS has the correct keyfile loaded and STT has the correct .pr0 loaded.
Should look like this (or one of the Falconeer variants):
I’m still scratching my head on this one, seems he has properly followed the step by step instructions listed with my Falconeer profile. We verified that he’s not mistaken on his X52 HOTAS version, it is indeed the ‘Pro’ - any help would be greatly appreciated, I’ve tested this stick and Falconeer profile setup across multiple computers in my house and never ran across any issues with Pinkie. The FOV on the slider is an easy fix under Setup > Controllers > Advanced (first tab, View Control, FOV setting at top should be ‘keyboard’ or set as desired, and not set to the X52 throttle slider)
-
Since he seems to be using my ‘Falconeer’ profile for X52 Pro the Pinkie Shift is handled in DX directly in the binds file, and the profile in STT should have only 1 layer, and Pinkie as ‘Unassigned’ to work as a DX button. The throttle slider actuating speed brake would mean BMS has the correct keyfile loaded and STT has the correct .pr0 loaded.
Should look like this (or one of the Falconeer variants):
https://i.imgur.com/YW1FpYH.pngI’m still scratching my head on this one, seems he has properly followed the step by step instructions listed with my Falconeer profile. We verified that he’s not mistaken on his X52 HOTAS version, it is indeed the ‘Pro’ - any help would be greatly appreciated, I’ve tested this stick and Falconeer profile setup across multiple computers in my house and never ran across any issues with Pinkie. The FOV on the slider is an easy fix under Setup > Controllers > Advanced (first tab, View Control, FOV setting at top should be ‘keyboard’ or set as desired, and not set to the X52 throttle slider)
Even if the Pinky in SST is unassigned it makes a difference if its Latched or unlatched and I’m not sure if that is saved in pr0 or somehow handled directly through the driver
Gesendet von meinem SM-G930F mit Tapatalk
-
Even if the Pinky in SST is unassigned it makes a difference if its Latched or unlatched and I’m not sure if that is saved in pr0 or somehow handled directly through the driver
Unfortunately, the Pinkie being latched would only be possible through the .pr0 and is not handled directly through the driver, and these files in my Falconeer set are locked to ‘read only’, so can rule out any unknown accidental re-assignment or change being a factor here. Someone would definitely remember the procedure if they manually latched the Pinkie in one of my Falconeer profiles given that extra hassle. Gotta be something along these lines, for sure - there are only two places to tell the Pinkie what it can do: the .pr0 and the .key and I’ve gone over them twice now. Gotta leave it in the hands of fate now, nothing more I can really offer along the lines of help afaik
Any ideas definitely more than welcome - and thanks for helping oak!