Not that I'm against the Concorde, it's just that I have a very-specifically configured 737NG cockpit. I've a feeling I'll need FSLabs to loan me a Concorde X if I'm going to solve it for them - I don't want to buy one as I really would never fly it. All I'm trying to ascertain at present is what is going on. If it needs any tweaking in my software it's probably going to have to wait a few weeks. This weekend is pretty fully occupied as it is and next week I've a lot to do before disappearing on holiday. You can actually get the same effect by calibrating with a zero-sized reverse zone - that's how it was done before I added the checkbox option.īTW there's no rush as far as I am concerned. Save a copy of your FSUIPC4.INI file first, because without that option you'll need to re-calibrate. In that case it would be interesting to find out if the problem still occurs with the option unchecked. Reverse thrust: My axes are calibrated using the NO REVERSE THRUST tab checked. I have double checked to make sure that there are NO duplicate mappings or any stupid stuff like that.ġ) Saitek Yoke w/attached Saitek Throttle Quad (Profile specific for Concorde-Quadrant X axis=Null, Y axis = Eng1, Z axis = Eng2)Ģ) Saitek Throttle Quad (For Concorde, Quadrant X axis=Eng3, Y axis = Eng 4, Z axis = Null)Ĥ) CH Throttle Quad (levers not assigned to anything for this aircraft) Here is a list of my currently connected controllers. I am not using any of the "sync" functionality (my response curves are completely linear, but my min and max values are slightly different for each axis, with an appropriate "null" so as not to accidently induce thrust reverse) They are calibrated from the tab, with the filter boxes checked. My throttles are mapped using "send direct to FSUIPC". I will let you all know within the next day or so as to whether changing the power scheme had any effect.įor FSUIPC, I'm using version 4.60. I am working under the assumption that this is one and the same to the problems I have experienced, but I can easily reproduce the throttle disconnect by shutting down the engine and doing an in-flight Relight. I think what the OP is trying to say is that when it comes time to retard the throttles during the landing flare, he switches off the AutoThrottle, and finds that his throttles levers have no effect (thus he can't cut the power). Unlike the Original Poster in the thread I referred you to, I have not experienced this problem during an autothrottle disconnect, but I don't rule it out, and I will experiment with that scenario. However, I did go in under Control Panel->Power Options and changed my settings from "Balanced" to "High Performance". I'm using Vista 64, and it apparently does not have a per-hub power management scheme. I'll go ahead and cross post this on the Flight Sim Labs forums. The FSLabs team is working very hard on a Service Pack and this issue is of a lower priority to them, understandably, but I think it would be helpful to get you in on this issue, nonetheless. Much of the discussion in the thread I refer you to is on the verge of a flame war, but I would very much appreciate if you could take a look at it. Well, I would very much like to use FSUIPC throttle calibration, and the team over there has suggested that I bring this issue to your attention. Once this happens there are certain workarounds to get throttle control back, such as issuing a keyboard command to the "virtual flight engineer", which may or may not be practical at certain times, like if the throttles disconnect occurs during the landing flare, etc.The development team is recommending a workaround to avoid this from happening in the first place: Simply don't use FSUIPC throttle calibration. To summarize, there is an issue on Concorde where the engines become disconnected from the user's throttle levers under certain circumstances for users using FSUIPC full version to calibrate their throttle levers. May I direct your attention to the following thread on the FSLabs forum concerning their new Concorde X and FSUIPC:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |