Level-D 767: Throttle causes spoilers to deploy and cowl flaps to open.

[Martinlest]

Hi,

 

I haven't flown the Level-D 767 for a few months (this is FS9, BTW) and I now find that when I am ready to taxi and increase throttle, the spoilers immediately come up and the reversers open...

 

This is undoubtedly something to do with the interaction between my Saitek X52 and my (registered version of) FSUIPC. If I increase power by using F3 or F4 on the keyboard, there is no problem - but as soon as I touch the throttles on the X52 the speedbrakes immediately go up... I am reasonably OK with the Saitek setup but am not too familiar with the FSUIPC interface, I'm afraid!

 

I do not have this problem with any other aircraft, just the Level-D 767, so I am wary of tampering in areas I don't understand too well (FSUIPC!) and messing up things for other aircraft. Could you kindly help me to sort this out, I am pretty sure that the problem must be due to the way I have FSUIPC set up and the way it interacts with the Level-D software. No luck Googling...

 

Thanks a lot,

 

Martin

[Martinlest]

This is with all a/c I see, not just the Level-D after all... my mistake.

 

If I temporarily move all the FSUIPC files out of the FS9/Modules folder, the problem is resolved, so it is clearly an issue with the way FSUIPC is set up (I wonder therefore why all was OK till yesterday: I made no changes myself to FSUIPC). I do not need to have FSUIPC acting on my joystick at all - I am happy with the way it works with my Saitek profile, but I can't see how to disable this function - nothing I have tried works.

 

Hope you can advise, as I can't really fly properly at the moment, with spoilers and reversers deploying whenever I move the throttle.

 

Thanks again.

[Pete Dowson]

This is with all a/c I see, not just the Level-D after all... my mistake.

 

If I temporarily move all the FSUIPC files out of the FS9/Modules folder, the problem is resolved, so it is clearly an issue with the way FSUIPC is set up (I wonder therefore why all was OK till yesterday: I made no changes myself to FSUIPC). I do not need to have FSUIPC acting on my joystick at all - I am happy with the way it works with my Saitek profile, but I can't see how to disable this function - nothing I have tried works.

 

Hope you can advise, as I can't really fly properly at the moment, with spoilers and reversers deploying whenever I move the throttle.

 

Thanks again.

 

It sounds exactly like dual assignments -- try disabling controllers in FS. If it then works okay, you have the same axes assigned in both FS and in FSUIPC, to different actions. If it doesn't help, then either you have some Saitek software making assifgnemtns as well as FSUIPC, or you have dual assignments in FSUIPC -- but you should be able to see that latter case immediately by simply going to the Axes tab in FSUIPC and moving the levers.

 

Pete

[Martinlest]

..you should be able to see that latter case immediately by simply going to the Axes tab in FSUIPC and moving the levers.

 

Well, the numbers go up and down but I am not sure what any of it means - I am afraid FSUIPC is just one of those programmes I have never really got to grips with (though I do see that it is wonderful!).

 

Someone on another forum told me how to stop FSUIPC controlling this axis (pressing the Rescan button on the axis assignments tab then moving the X52 throttle up and down, finally pressing 'clear') and having done that, all is OK again. I had tried disabling controllers in the X52, to no avail, and since simply pressing the f3 or f4 keys caused no problems I was at a bit of a loss.

 

Wish I knew how this came about suddenly - I have had the regsitered FSUIPC and the Saitek working just fine till the other day, and I made no changes myslef to either of their setups..

 

Thanks.

[Pete Dowson]

..you should be able to see that latter case immediately by simply going to the Axes tab in FSUIPC and moving the levers.

 

Well, the numbers go up and down but I am not sure what any of it means - I am afraid FSUIPC is just one of those programmes I have never really got to grips with (though I do see that it is wonderful!).

 

It isn't the numbers that matter, it is what you have assigned below -- you can have up to four different assignments and they are displayed below, on the left.

 

The User Guide dfoes contain pictures you know. They may help -- surely worth a look at the supplied documentation occasionally, don't you think?

 

Someone on another forum told me how to stop FSUIPC controlling this axis (pressing the Rescan button on the axis assignments tab then moving the X52 throttle up and down, finally pressing 'clear') and having done that, all is OK again.

 

All that does is clears the FSUIPC assignment. If you don't want to use FSUIPC that's fine. But why on Earth did you bother to make the assignments in the first place?

 

Wish I knew how this came about suddenly - I have had the regsitered FSUIPC and the Saitek working just fine till the other day, and I made no changes myslef to either of their setups..

 

FS will automatically make axis assignments if you aren't careful. It does this if you unplug a device then plug it back in, and it seems to do it at other times for reasons unknown. As I said earlier, you need to check that controllers are disabled in FS if you want to assign in FSUIPC.

 

If you don't want to use FSUIPC, just delete the INI file from the FS Modules folder. Then you won't have any settings at all.

 

Pete

[Martinlest]

1. "surely worth a look at the supplied documentation occasionally, don't you think?" I do think so, yes, which is why I spent ages last night trying to apply what it said (following the pictures) to the FSUIPC interface, with no effect on the problem I had though. It became very frustrating.

 

2. "why on Earth did you bother to make the assignments in the first place?" Unless I am forgetting what I have done in the distant past, I never have. I imagine an aircraft installation has altered the settings automatically or, as you say, FS has made changes (I keep a backup of the ini file for that reason). If it was something I did for some reason, it will have been a long time ago; and if it had been done wrongly, why did it work for two years (or whatever) and this issue only surface two days ago?

 

3. "If you don't want to use FSUIPC, just delete the INI file from the FS Modules folder." Of course I do want to use FSUIPC (why would I buy a registered copy then delete all the files?), but for other functions that it enables in FS. I have always been more than happy with the accuracy of the throttles, ailerons and so on as managed through FS9 and the Saitek X52. Never had any issues.until this happened all of a sudden.

 

Martin

[Pete Dowson]

1. "surely worth a look at the supplied documentation occasionally, don't you think?" I do think so, yes, which is why I spent ages last night trying to apply what it said (following the pictures) to the FSUIPC interface, with no effect on the problem I had though. It became very frustrating.

 

Okay, then you'd have seen the way assignments are done and where they are shown. Below the numbers, on the left, 4 boxes each with a drop-down capability with the many things they can be assigned to.

 

2. "why on Earth did you bother to make the assignments in the first place?" Unless I am forgetting what I have done in the distant past, I never have. I imagine an aircraft installation has altered the settings automatically or, as you say, FS has made changes (I keep a backup of the ini file for that reason). If it was something I did for some reason, it will have been a long time ago; and if it had been done wrongly, why did it work for two years (or whatever) and this issue only surface two days ago?

 

 

FSUIPC most certainly does NOT make assignments by itself, and nor would FS make changes to FSUIPC files. The most likely thing you've had happen is that FS has made automatic assignments itself because either you have disconnected and reconnected the device, or FS thinks you have for some reason of its own.

 

I already explained this as a possibility if you look back.

 

If you have the same lever assigned in both FSUIPC and FS then obviously there will be confising conflicts of the type you've described.

 

3. "If you don't want to use FSUIPC, just delete the INI file from the FS Modules folder." Of course I do want to use FSUIPC (why would I buy a registered copy then delete all the files?), but for other functions that it enables in FS. I have always been more than happy with the accuracy of the throttles, ailerons and so on as managed through FS9 and the Saitek X52. Never had any issues.until this happened all of a sudden.

 

 

Well, as I said,  there's absolutely no way FSUIPC makes assignments of its own volition.

 

I suggest you edit the INI file and delete all [Axes...] , [JoystickCalibration ...], [buttons ...] and [Keys ...] sections, so removing all assignments. Do this before loading FS.

 

Pete