Laud Posted May 26, 2007 Posted May 26, 2007 Hi mates! Today I completed my Saitek Setup (X-52, Pedals, (new) Pro Gamer Unit). Drivers are installed and SST seems to be working. Just one problem comes up when starting LockOn: Within LockOn the mode-switch seems not to work. All inputs always refer to the default (blue light mode) mode setup. It doesn't matter wether I switch to green or red mode the inputs remain the same. Does anyone here has a similar setup and a hint whats goin wrong here??? Thank you in advance... [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Black_Hawk Posted May 26, 2007 Posted May 26, 2007 Hm, I don't have that issue. Are you sure that you programmed it correctly in SST? And BTW, PGCU rulez! :pilotfly: 159th GAR LockOnFiles CAW Team
Black_Hawk Posted May 26, 2007 Posted May 26, 2007 It could be that you didn't clear the keycommands for the PGCU in Lock On Input Options 159th GAR LockOnFiles CAW Team
Laud Posted May 27, 2007 Author Posted May 27, 2007 Since the profiles for the X-52 and the ruder-pedals work I think I made no mistakes using the SST. In LOMAC I removed all related commands. Right now I'm testing the newest Saitek drivers and SST (just downloaded) for each controller. But there's the next problem coming up: Profiles are no more .dat they are .pr0. So it seems like I have to redo the whole work... :( [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Black_Hawk Posted May 27, 2007 Posted May 27, 2007 I'm not going to the next version of the Saitek drivers as long as they're Beta... I've had too much problems making my X52, Pedals and PGCU work in a harmony, and I don't intend to change that for a looong time :joystick: Hop to the Saitek forums, tech support will surely get your problem fixed 159th GAR LockOnFiles CAW Team
hitman Posted May 27, 2007 Posted May 27, 2007 One of the bugs in the new software (its currently released strictly as beta) is that the Clutch button wont work, which means you cant change profiles on the fly. Your better off assigning that button to a different command instead.
Laud Posted May 27, 2007 Author Posted May 27, 2007 One of the bugs in the new software (its currently released strictly as beta) is that the Clutch button wont work, which means you cant change profiles on the fly. Your better off assigning that button to a different command instead. Thats just what I didn't get to work with the old ones (for the stick it worked fine but for the PGCU it didn't). I just started to create new profiles in .pr0-format which seems to work so far. Rudders are ok and PGCU is also working fine. I'll have to see how the HOTAS is gonna work. Too bad the .dat -> .pr0-converter isn't available yet... But as I have to rethink my whole profile concept with getting those new buttons on the PGCU it's not too bad to create whole new profiles. Just rudders remain the same as before but that's not really much work! ;) [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Ramstein Posted May 27, 2007 Posted May 27, 2007 Thats just what I didn't get to work with the old ones (for the stick it worked fine but for the PGCU it didn't). I just started to create new profiles in .pr0-format which seems to work so far. Rudders are ok and PGCU is also working fine. I'll have to see how the HOTAS is gonna work. Too bad the .dat -> .pr0-converter isn't available yet... But as I have to rethink my whole profile concept with getting those new buttons on the PGCU it's not too bad to create whole new profiles. Just rudders remain the same as before but that's not really much work! ;) the on the fly works only witht he Beta. And don't waste your time making new profiles with the old non Beta software and drivers. as the old pro profile will not work with the new beta . The new beta will soon become the standard. :joystick: ASUS Strix Z790-H, i9-13900, WartHog HOTAS and MFG Crosswind G.Skill 64 GB Ram, 2TB SSD EVGA Nvidia RTX 2080-TI (trying to hang on for a bit longer) 55" Sony OLED TV, Oculus VR
Laud Posted May 27, 2007 Author Posted May 27, 2007 When you read my post carefully you'll notice that I'm creating new profiles in.pr0! But thanks anyway!! As I'm nearly finished now with the new profiles and already did some test flights I must say the new (beta) drivers and SST are great. Everythings just working fine. Just takes a bit to understand the little different handling of the SST. [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Ramstein Posted May 27, 2007 Posted May 27, 2007 When you read my post carefully you'll notice that I'm creating new profiles in.pr0! But thanks anyway!! As I'm nearly finished now with the new profiles and already did some test flights I must say the new (beta) drivers and SST are great. Everythings just working fine. Just takes a bit to understand the little different handling of the SST. rgr.. but it will confuse some people because the old *.pro and the new *.pro wil confuse people. They will try to take the old *.pro and they will not open or work in the Beta. Only the new *.pro will. Saitek kept the same extension '*.Pro' file extension name for the new ones. :joystick: http://www.saitekforum.com/ A note about old .dat profiles The new software uses a new format for the profiles (.pro) so your old .dat profiles will not work. This does mean that you will need to create new profiles for your games, I'm afraid. We're working on a conversion tool that will convert .dat files to .pro files, but it's not ready yet. Some of you will be aware that the old SST software did generate .pro files in addition to the .dat file when you saved a new profile so may think that these will work, but unfortunately this isn't the case. Fixes Printing support is now working - you can print out a list of the controls on your controller and what they are assigned to do. Old X45 owners should now find that the calibration works. The Aux switch should also be working fine. Cyborg evo Force and Cyborg 3D Force stick owners have the ability to set the centering on their sticks so that they auto centre. The option for this is under the Force tab at the top of the Properties screen in Game Controllers and it's called Default Spring Always On - simply tick/untick the box to enable/disable it. Fallback commands now work correctly on POV Hats Aux button now works X52 Clutch "on the fly" profile selection now works Key Presses now default to zero time. Use Advanced Editor if you want hand crafted input. This avoids those instances where you have to hold the button down for the length of the programmed sequence of keystrokes in order for it to all happen. Exception fixed when using cut in advanced commands Key presses and Macros now release keys in opposite order to their presses. First key pressed is last key released. Exception fixed when user deletes all shiftstates and tries to set new shiftstate fallback. ASUS Strix Z790-H, i9-13900, WartHog HOTAS and MFG Crosswind G.Skill 64 GB Ram, 2TB SSD EVGA Nvidia RTX 2080-TI (trying to hang on for a bit longer) 55" Sony OLED TV, Oculus VR
Laud Posted May 28, 2007 Author Posted May 28, 2007 Yap, but the SST beta2 (SD6) generates the new .pr0. You can read that in the beta-feedback-thread in the Saitek-forums. [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
hitman Posted May 28, 2007 Posted May 28, 2007 Thing I dont like about the new drivers is that theres no way to turn off the led lights now.
Laud Posted May 28, 2007 Author Posted May 28, 2007 Which red lights? X-52pro? [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Black_Hawk Posted May 28, 2007 Posted May 28, 2007 :D he said Led, not Red :P I'll stick with the current drivers and SST until the new drivers and SST get cleared of bugs; I don't want to be like those Vista users :smartass: 159th GAR LockOnFiles CAW Team
Laud Posted May 28, 2007 Author Posted May 28, 2007 LOL! Rgr LED... Hm... never used that function. So far I'm not a victim of bugs. I also suggested (in the Saitek forums) to implement the axxis configuration into the new SST (like it is in LOMAC and the Cougar software). [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Black_Hawk Posted May 28, 2007 Posted May 28, 2007 At which topic (at Saitek forums) do you put your suggestions? I'd like to put in a few of my own :joystick: 159th GAR LockOnFiles CAW Team
Laud Posted May 28, 2007 Author Posted May 28, 2007 http://www.saitekforum.com/showthread.php?t=11551 [sIGPIC][/sIGPIC] Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200 Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD) TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5
Recommended Posts