numbergasra.blogg.se

1. #SAITEK X52 SOFTWARE INSTALL PATH HOW TO#
2. #SAITEK X52 SOFTWARE INSTALL PATH ZIP FILE#
3. #SAITEK X52 SOFTWARE INSTALL PATH DRIVERS#
4. #SAITEK X52 SOFTWARE INSTALL PATH SOFTWARE#
5. #SAITEK X52 SOFTWARE INSTALL PATH CODE#

To set one yourself, edit the registry and create a new key Computer\HKEY_CURRENT_USER\Software\Logitech\Configuration\StartupProfiles

#SAITEK X52 SOFTWARE INSTALL PATH SOFTWARE#

Solution: The Logitech software does support default profiles, it just doesn’t expose the option to specify the default profile. But the Logitech version doesn’t support a “default” profile that’s loaded automatically on startup.

#SAITEK X52 SOFTWARE INSTALL PATH DRIVERS#

Problem: The latest X52Pro drivers and profile editor are provided by Logitech rather than Saitek.

#SAITEK X52 SOFTWARE INSTALL PATH CODE#

This was more code for the Freepie script. I mapped the two buttons as mouse left and right click, and one of the scrollwheels as mouse scroll. Can DCS make use of them to simulate mouse clicks/scrolling? This would be useful in VR. Problem: The X52pro throttle has 2 scrollwheels and two buttons below the LCD screen, but these aren’t available through the X52 profile editor. Solution: Freepie uses Python, so a chunk of Python code in the Freepie script can cause native Windows key events to be generated, bypassing Freepie’s keypress generation. Freepie can translate HOTAS button presses to keyboard presses, but only sends these key events to the active window They aren’t picked up by other background apps. With DCS (rather than X52 profiler) managing the Pinkie shift states, I need to disable Clutch mode globally for the X52 pro. Problem: I want to use Fire B with the Pinkie modifier to activate “TrackIR recentre view”. This approach was originally described here: In DCS, the slider on the virtual device is used for zoom view. A Freepie script can provide a filtered/smoothed view of the X52pro slider through this virtual device. This is a virtual joystick that Windows thinks is a physical device.

Set up a new device in VJoy, with just one slider control. Problem: The X52Pro slider is great for mapping to the view-zoom. When starting DCS (or at any later time), I can choose Mode1 on the stick for Function key comms, or Mode2 for Vaicom voice comms. These X52 DCS profiles are identical other than Mode1 having the throttle mini stick defined to activate the radio using F-keys and Mode2 activating the radio using Vaicom TX commands. So in my one X52Pro DCS profile I define Mode1 for F-Key comms, and Mode2 to be for VaiCom comms. Solution: I generally don’t like to change X52 mode states while flying.

#SAITEK X52 SOFTWARE INSTALL PATH HOW TO#

How to use a single set of HOTAS actions to activate the radio by Vaicom or Function key? Problem: I use VoiceAttack/Vaicom sometimes. The single X52 profile configures a few global functions, such as using the Clutch button on the throttle for TeamSpeak/Discord, and the throttle ministack bands for radio commands. Be aware that this will also affect all other games. To allow DCS manage the pinkie modifier, remember to disable the Clutch mode globally for the X52 pro.

It simplifies the X52 profiler profile for DCS. In the DCS control configuration, I can set up the pinkie button (Button ID #6) as a modifier. Rather than using the X52 Profile editor to manage Pinkie-shift states, I let DCS do the work. This addresses the two problems described above. DCS is now reading the joystick input directly, rather than just seeing the keyboard presses simulated by the X52 Profiler app. I created a single X52Pro profile for DCS, and customised the controller configuration of each module in DCS. Let’s hope ‘Shift-S’ isn’t anything like Eject! DCS might see ‘Shift-S’ instead of simply ‘S’. When I press both together, the X52 profile generates the keypresses “S” and “Shift-W” simultaneously. A made-up example: Wheelbrake might be ‘Shift-W’. The keys sometimes clashed when used with modifiers. Every time I moved from one plane to another in DCS, I had to Alt-Tab to the desktop and select a different X52 profile.Ģ. The thinking was that I could keep the default key configurations in DCS for each module, and use the Logitech profile editor to create an X52Pro profile per DCS module, mapping each HOTAS button to the keyboard key presses expected by DCS for that module. Originally, I started with a separate X52Pro profile per DCS module.

#SAITEK X52 SOFTWARE INSTALL PATH ZIP FILE#

I’m attaching a zip file with my default X52Profile for DCS, and the Freepie script referred to below.īefore starting DCS, I have to plug in the X52Pro, then start the “FreePie” application. I hope a few of these might save time for other X52Pro owners.

I’ve got a Saitek X52Pro, and after a lot of bad decisions, I’m eventually settled on a configuration that I’m happy with.