SST/X65: Failed to open file, can't save and reload my profile

[Fluke]

• I have a Saitek X65
• Drivers and SST got installed correctly as far as I can tell (mind you: the latest beta drivers, not the ones I can download from the website, because in that case I don’t see SST mentioned in the control panel about-tab, indicating there’s something not 100%)
• Stick and buttons work
• Someone else’s profile works

Now… when I make my own profile, I can edit and design just fine. But after saving this profile, I cannot re-open it in the editor (or load it in the stick):

“Failed to open file”

is what I get. Other people trying my .pr0 get the same result. I tried with different driver/sst combo’s (sd6, sd7), but nothing worked. After making 4 profiles in a row I’m a bit tired.

Has anyone else noticed this or heard about it?
Apparantly I’m doing something in my profile SST doesn’t like, but I don’t know what.
Hopefully I’m not alone in this

[Zaltys]

I suggest you opening of Device Manager and checking if there are any exclamation marks be the Saitek devices. If there are, you may have to reinstall everything.

[Blu3wolf]

Yeah, it does it for me on about 4 different computers so far.

I can remember that it didn’t use to do it originally, but it does now for whatever reason.

Its not just your computer! Wish I could tell you how to fix it though…

[Fluke]

thanks for the replies!

Device manager is ok.

I have narrowed it down to (at least for me) the cause:

I tried to use the mode switch a a dogfight switch. The way I tired this, apparantly goofed up the entire profile. A simple test with an otherwise empty profile but the construction I used before to use the mode switch gave me the same “failed to open” error.

Trying to figure out another way now.

[Fluke]

Closing in on a workaround, but now when I clear the profile, I get a BSOD. WTF… what are you doing, saitek? lol…

[Blu3wolf]

Hmm. Ive done the same thing pretty much all the time. Nice to know that that causes it at least.

[drtbkj]

@Fluke:

thanks for the replies!

Device manager is ok.

I have narrowed it down to (at least for me) the cause:

I tried to use the mode switch a a dogfight switch. The way I tired this, apparantly goofed up the entire profile. A simple test with an otherwise empty profile but the construction I used before to use the mode switch gave me the same “failed to open” error.

Trying to figure out another way now.

Fluke, same thing happened with my -65. Even though we are supposed to be able to make the mode switch a 4 way, it completely freaked out my system, and I had the same problem as you. I had to create an entirely new pr0.
Btw, I was able to make the mode switch function as the D/cancel/M control using the SST command initiation(or whatever it’s called) function. That is where the -65 performs a command every time you enter that mode. One tip on that is to leave a mode without a command, and when exiting be sure the stick is in that mode. Otherwise your pc will see endless letters being produced. For that reason, I eventually set up hat 5 for D/C/M.

[Blu3wolf]

My method was to make an advanced command (I think the same as drtbkj) so that entering the mode would press the key once, and leaving it would press a different key (d,c for the M1, m,c for the M4).

I also had to do the entire profile whenever I wanted to change it.

It was a lot easier for me, because only part of the profile was used. Most of the stick just used DirectX, and the mode switch, the throttle box, and the hat 7 all used keypresses. Oh and the K switch as well. Everything else was DirectX (programmed in the BMS keyfile instead).

[Fluke]

using the SST command initiation(or whatever it’s called) function. That is where the -65 performs a command every time you enter that mode.

Hm… not sure I understand.

I got it to work I think: I made a macro on each mode position (well, 3 of them, 2,3 and 4). Through advanced commands, it sets both a press and release for that button.

Funny thing though, it actually gives 2 commands: first the letter (switch position) from which it came, and than the one it’s going to.

So when going from dogfight override mode to cancel override mode, it would actually press dc instead of just c. Same from cancel to missile: cm or back: mc.

Position 1 gives the same result as position 2 at the moment, the endless letters only start when clearing the profile, not when exiting falcon.

Ah well, slowly but surely

[Blu3wolf]

@Fluke:

Funny thing though, it actually gives 2 commands: first the letter (switch position) from which it came, and than the one it’s going to.

So when going from dogfight override mode to cancel override mode, it would actually press dc instead of just c. Same from cancel to missile: cm or back: mc.

Just set a single advanced keypress then. Set M1 to be d, M2 and M3 to be c, and M4 to be m. Make sure they are all on the down presses.

[Fluke]

it seems that if I don’t put in a release, the command will repeat itself indefinitely

EDIT: UGH… need to go to sleep… stupid me… mixed up releasing the programmed key with releasing the joy button… -sigh-

Edit 2: WHOAAAA… failed to open file… glad I made a backup this time… setting a key to the mode 1 position causes the error, it needs to stay in the fall back setting