kgalagadi 0 Posted December 22, 2012 Share Posted December 22, 2012 Dear colleagues, maybe someone is able to help me: I like the checklist feature very much, but unfortunately the After Engine Start checklist gets stuck at the point "flight controls" where I should move my sidestick to all directions. The infobar says "move sidestick full left", I do so but it seems it does not recognize it. On the ECAM it shows full sidestick movements. My stick is a fairly old Microsoft SideWinder 2 Force Feedback... Thanks very much ladies and gentlemen, have a good night. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 23, 2012 Aerosoft Share Posted December 23, 2012 Did you try to calibrate your stick? It could be it does not reach full deflection. Link to comment Share on other sites More sharing options...
kgalagadi 0 Posted December 23, 2012 Author Share Posted December 23, 2012 I have calibrated the stick once again... screens attached that show the PFD with the cross showing the stick postion - one time centered, one time fully left. Control settings are as recommended (at least I hope so -> view pic). Link to comment Share on other sites More sharing options...
rjord 86 Posted December 23, 2012 Share Posted December 23, 2012 I have the Microsoft SideWinder 2 Force Feedback... and it works fine for me...... possibly needs calibration as Mathijs suggested. Link to comment Share on other sites More sharing options...
balus 43 Posted December 23, 2012 Share Posted December 23, 2012 Try increasing your null zone - I think it is on page 6 of the tutorial Link to comment Share on other sites More sharing options...
Bert Laverman 39 Posted December 24, 2012 Share Posted December 24, 2012 Ok, I have exactly the same problem. Saitek Yoke and Rudder. Changing the null zone has no effect, it just determines when it starts moving, it doesn't affect the end pont. Maxing out sensitivity did get it closer to the end of the range, but not close enough to get me past this checklist item. As it stands, I cannot use the checklist and copilot beyond this point. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 24, 2012 Aerosoft Share Posted December 24, 2012 Ok, I have exactly the same problem. Saitek Yoke and Rudder. Changing the null zone has no effect, it just determines when it starts moving, it doesn't affect the end pont. Maxing out sensitivity did get it closer to the end of the range, but not close enough to get me past this checklist item. As it stands, I cannot use the checklist and copilot beyond this point. Mmmm so calibrating did not redefine the max settings of the stick? That's very strange, calibrating should do exactly that, read the min,center and max values and translate them to 0 <> 32767 <> 65535 for the sim. Could be the control software (if you use it, it's not needed and often creates more problems then it solves), or the calibration results are not stored. Link to comment Share on other sites More sharing options...
Jude 190 Posted December 25, 2012 Share Posted December 25, 2012 I've the same issue,I'll recaibrate, set the null zones and report back, I'm using P3D. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 25, 2012 Aerosoft Share Posted December 25, 2012 Here is a small tool that reads throttle in raw mode, it helped us a lot with some customers. Often we see their joysticks are just not getting the range they should have. Cheaper sticks can do that even after a few months of use.Poswdm.zip Link to comment Share on other sites More sharing options...
Jude 190 Posted December 25, 2012 Share Posted December 25, 2012 Same issue. Link to comment Share on other sites More sharing options...
Jude 190 Posted December 25, 2012 Share Posted December 25, 2012 Happy Christmas, Mathijs, Thanks for the 'Bus Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 25, 2012 Aerosoft Share Posted December 25, 2012 Same issue. So you say it looks the same? That seems impossible. Can you send us a screenshot? Link to comment Share on other sites More sharing options...
golyaht 11 Posted December 25, 2012 Share Posted December 25, 2012 In the screenshots, it doesn't appear that the control surfaces are at full deflection, which is why it doesn't exit out of the checklist. When you move the stick to full left, the captain should say "full left" and the annunciator in the right MCDU should say "move stick to full right". Do you get this? In the FSX control calibration screen, make sure your sensitivity is set to 100%. Hope this helps. Merry Christmas. Link to comment Share on other sites More sharing options...
Jude 190 Posted December 25, 2012 Share Posted December 25, 2012 I installed the drivers for the Saitek Hardware, recalibrated,and issue not present anymore. I hope this can help other users out there. Link to comment Share on other sites More sharing options...
kgalagadi 0 Posted December 26, 2012 Author Share Posted December 26, 2012 Here is a small tool that reads throttle in raw mode, it helped us a lot with some customers. Often we see their joysticks are just not getting the range they should have. Cheaper sticks can do that even after a few months of use. Thank you for posting this tool. Although it seems my stick delivers correct values (see screen). I am not using any special joystick software but basic Windows 7 drivers. Any other hints? Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 26, 2012 Aerosoft Share Posted December 26, 2012 You do can see the numbers change on the X, Y, Z and rZ axis? Link to comment Share on other sites More sharing options...
kgalagadi 0 Posted December 26, 2012 Author Share Posted December 26, 2012 Sure, if I move the stick, the numbers change between 0 and 65ksomething. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 27, 2012 Aerosoft Share Posted December 27, 2012 Mmmmm, why does FSX interpret the data different? Strange issue. Link to comment Share on other sites More sharing options...
fmhellas 0 Posted December 28, 2012 Share Posted December 28, 2012 Hi, i am having the same problem after the patch. (Unistalled the initial, restarted, installed 1.02 ver, then the 1.02b) Did no changes regarding controls. I'll come back, checking. Win7 English 64bit, FSX. Link to comment Share on other sites More sharing options...
fmhellas 0 Posted December 28, 2012 Share Posted December 28, 2012 The control is working ok. I downloaded the utility above, and when the stick is fully left it shows 0 and fully right 65535. With default cessna everything is ok. In the Bus, the motion of the stick is vissible (at cockpit ), but at the lower ECAm seems as it is not working. Teh problem is that i tried to fly to check if it would be ok, but the plane doesnt turn. The strange is that even when i engaged the AP, the plane still wouldn't turn, even with hdg select mode. So there must be something else than the controler itself. I am going now to unistall and install only the 1.02 ver and try again. Link to comment Share on other sites More sharing options...
fmhellas 0 Posted December 28, 2012 Share Posted December 28, 2012 I tried to unistall through the windows unistall via control panel, and there was AErosoft Airbus with no version at the corresponding column. I said what the h..., just pressed "unistall" and within 1 sec, the unistall "finished". The title was removed from control panel, but of course the addon software is still on my disk. At first time when i unistalled ver 1.0 i did it via Aerosoft's unistaller. Link to comment Share on other sites More sharing options...
fmhellas 0 Posted December 28, 2012 Share Posted December 28, 2012 Problem solved here, maybe with the new .xml file. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.