Jump to content

Recommended Posts

Posted

I've always downloaded others profiles for games, so I don't know how to import actions (say landing gear, flaps, lights...whatever) into the SST software to assign them to a button. Can anyone help me out?:helpsmilie:

Posted
I've always downloaded others profiles for games, so I don't know how to import actions (say landing gear, flaps, lights...whatever) into the SST software to assign them to a button. Can anyone help me out?:helpsmilie:

 

If you can download somebody else's SST profile for the game/sim in question, even if it is for a different Saitek controller, you can then use those command entries for your controller profile. There's info on that in these forums somewhere. Found it.

 

http://forums.eagle.ru/showpost.php?p=993884&postcount=7

 

 

Otherwise, you would normally enter them manually yourself. However, I think it is possible to import a list if it is properly formatted. I seem to recall for instance, somebody getting the command list out of BlackShark 1.0 somehow and then massaging it to be readable by SST. If you attempt that, remain mindful of the need to keep command names (labels) short enough. I think they had to be kept to 16 characters long, or less. If the names are too long, it cause problems for the X-52 / X-52Pro (MFD related, IIRC).

[sIGPIC][/sIGPIC]

There's no place like 127.0.0.1

Posted
If you can download somebody else's SST profile for the game/sim in question, even if it is for a different Saitek controller, you can then use those command entries for your controller profile. There's info on that in these forums somewhere. Found it.

 

http://forums.eagle.ru/showpost.php?p=993884&postcount=7

 

 

Otherwise, you would normally enter them manually yourself. However, I think it is possible to import a list if it is properly formatted. I seem to recall for instance, somebody getting the command list out of BlackShark 1.0 somehow and then massaging it to be readable by SST. If you attempt that, remain mindful of the need to keep command names (labels) short enough. I think they had to be kept to 16 characters long, or less. If the names are too long, it cause problems for the X-52 / X-52Pro (MFD related, IIRC).

 

That first part sounds like a better idea, which is what I've been doing for the most part. That second half sounds like wizardry to me :huh:

 

I just bought Blackshark, any x52pro profiles that you would recommend?

 

Thanks for the help!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...