@Snake122:

SST isn’t really a work around but Win10 throws the not verified software when installing. Slightly worried that Win11 security features will cause an issue with SST, but think that’s a not too much of a concern really. But since I was mentioning drivers I thought I would put “/SST” on there.

Away from the computer to confirm if I’m using 7.0.53.6, but the drivers have been problematic for me because they are not verified drivers. I had to do the dig into device manager and select the more generic named driver instead of the one Windows assigns. Again, not hard to work around but seems like it all happens because they are older drivers. I’m afraid security features in Win11 will lock this down even more to where it is an issue where it breaks something since Logitech isn’t going to fix them.

I’ve installed the 7.0.53.6 drivers and SST software several times and have never seen W10 throwing the not verified warning. I’ve only had 2 problems using the drivers and sofware. The first is that on two occasions the SST profiler seemed to lose the scan code for a single key stroke and didn’t transmit the key stroke from an assigned button. A reinstall of the drivers seemed to fix it, though. The second was trying to install the Vjoy virtual joystick drivers. For some reason the Vjoy installer doesn’t completely finish and the result was that the Saitek drivers were trashed. When I tried to reinstall the Saitek drivers, after completely uninstalling them, the reinstall process would not recognize that the X65F was plugged in. My only remedy was to go back to an earlier W10 system restore point. Be careful when trying the Vjoy drivers, create a W10 restore point first, just in case.

@Snake122:

My biggest concern with Win11 is if the driver/SST workaround for the X65F will still work.

I’m using the 7.0.53.6 Saitek driver and SST software with W10 and it works fine with my X65F. Is there another workaround that you are referring to?

@Shadow:

An external drive is not going to help with performance, not unless the internal is failing & needs to be thrower in the bin

Yes I understand, Shadow. I’ve been running BMS for the last few years on an external USB 2 drive. I’m interested to see what the difference will be on the internal. I wasn’t using the internal for BMS or other games due to space limitations – so I’m going to free some space up and see what improvement I can get.

Ilmars

@Cloud:

Correct. In your Benchmark Sims registry folder, you would double-click on the baseDir entry and change the Drive from C to D , etc., to activate which install you want to be active.

C9

Thanks C9, that’s what I was hoping.

I think it’s this key that is involved…. "[HKEY_LOCAL_MACHINE\SOFTWARE\Benchmark Sims\Falcon BMS 4.32]
“baseDir”=“C:\Falcon BMS 4.32"”

Hopefully, that’s the only key that needs to be changed.

Ilmars

Thanks guys for the info.

It appears that what you are saying is that the active version is always in the same named directory, and always on the same drive.

What I wanted to do was to have an instance of the installation that is currently on my external drive put on my internal drive, and switch back and forth between the versions on the different drives – and have BMS actually run locally on each drive. That way I can see how much of a performance hit the external drive contributes. I expect I would likely have to tweak the registry pointers to do that?

Ilmars

I’ve searched through some of the threads regarding installation and updates, but I am getting confused regarding the following…

Is it possible to install 2 instances of BMS 4.32 on the same machine and apply the update patches to each?
I have an instance of BMS 4.32 installed on an external drive, with the patches applied, and would like to install another instance on my drive and apply the updates so that I can compare performance of the 2 instances.

Are there registry issues involved when doing this? Do I need something like a Falcon Switcher program? Or is it ok to just run the setups from the base version of 4.32 on each drive, and apply the updates to each?

I noticed that at one time Zelegend provided a launcher that provided switching, but I can’t find it anymore.

Sorry if this has been covered elsewhere.

Thanks,
Ilmars

@Agave_Blue:

In Falcon BMS config there is a setting for the the ‘short press’ on the pinky/fov button. Does that affect ‘short press’ on other buttons as well? What is yours set to?

set g_nHotasShiftQuickPressTimeLimit 250

I didn’t have set g_nHotasShiftQuickPressTimeLimit in my BMS config file at all. But when I inserted it the parameter, it din’t make a difference. I also tried mapping the hat on my old X52 Pro stick as well, it didn’t work on it either.

Agave, could you please send my your BMS Config file as an attachment via email? There may be a setting in it that I don’t have included. I’ll PM you with my email address.

Thanks,
Ilmars

@Agave_Blue:

In Falcon BMS config there is a setting for the the ‘short press’ on the pinky/fov button. Does that affect ‘short press’ on other buttons as well? What is yours set to?

set g_nHotasShiftQuickPressTimeLimit 250

Thanks, Agave. I’ll take a look and give that a try tonight, and let you know.

Ilmars

Thanks for testing Zaltys.

Has anyone had any luck with this using Joysticks other than Saitek? Thrustmaster etc?

Ilmars

Has anyone managed to get the TMS-Left double click (2x < .5 sec) to work for switching the TGP sensor from IR to TV, with a DX hat binding on the X65?

I’ve tried binding the POV 1 hat with:
SimTMSLeft 0 -1 -3 6 0x0 0
or, HAT 2 with:
SimTMSLeft 79 8 -2 0 0x0 0

But it doesn’t seem to accept a double click to switch the sensor mode from IR to TV, it just changes the polarity from WHOT to BHOT.

If I send keystrokes for TMS-Left, either by the Saitek software, or via the keyboard, it works. But a DX binding does not.

Any input will be appreciated.

Cheers,
Ilmars