GEL

However I feel anybody accustomed to this model looks to the surge in thrust at the critical moment to confirm activation of the system. I tend to use short runway scenarios (CYTZ) and a typical use of CTOT, for me, is to dial in a Torq% of 110% before T/O and once positive climb is established and 500' AGL passed I dial down to 90%. I purposefully do not go (w/ TL) beyond 'activation point' for the reason above: the ability to dial down to a friendlier Torque% during the climb. So for me the need to observe the surge in thrust (CTOT) on T/O is crucial. When there is no surge to observe I understand that to mean CTOT is not available ... for whatever reason. I decide at that point to abort T/O or continue. Of course if I continue there is no way to observe any of this because the power levers are already at max and I assume to be w/o benefit of the CTOT system. To confirm, when I then lower the TL to the desired 90% torque: that , indeed, translates on the torque displays. If CTOT was actually on line, that should have no effect. (as you said ) I've considered that. And I must say the only program that I consider incompatible to the Saab is x-enviro. If it's a choice between the Saab or x-enviro .... well, I no longer use x-enviro. Otherwise I run few plugins.... betterpushback, xFMC, blu/fx , pretty much does it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There may be other factors such as changing locations w/i the airport environment. Sometimes I don't like the location where the Saab is placed upon start-up and I change to a different location. But perhaps you would know more about the likelihood of effects of that than I. ========================================= I must say all the above is the exception not the rule. I have CTOT MOST of the time but not ALL of the time. And because it is such a wonderful feature of this flight model and truly adds to the immersion of operations ... I wonder: why not all of the time (?) ========================================= I don't see a move to x-plane 11. There's not enough in it to justify an upgrade in CPU for me. Perhaps v12 ? Maybe I just don't like odd numbered versions. ;-) Your Saab will keep me quite busy in x-plane 10 for a long while yet. It truly is one of the best. Cheers

If you are suggesting pitch attitude is normal. Fine. By "hit or miss" I mean I either have the use of CTOT or not. (read: working or not upon starting a session w/ x-plane and the Saab) I'm not new to this model. I understand how this "system works" and have used it with success in the past w/o issue. I tend to do the same things upon start up. When CTOT is available (read: loaded with the model upon start-up) it works pretty much the way it always has... auto-coarsen is "on" , CTOT is "dialed in" to the desired % of torque and both L/R armed. The CTOT system "should" engage at apprx 70% ( at least mine does when working) and increase torque to the dialed in %. If all is good then the power system works as expected. If all is not good (read: CTOT did not load up with the aircraft) then things don't function as expected... for example: when CTOT is not working, as in: unavailable, off line, broken... I can position the TL (thrust levers) to max and keep them there for the entire flight if I choose w/o fear of over heating, etc... IOW the rest of the power system does not act as expected. So, as I said in an earlier text: it's "hit or miss" whether I have CTOT loaded with the aircraft or not. Likewise, before I begin a flight (read: Take off) I prepare CTOT and increase eng rpm (70%+/- ) to see if the system loaded.. if yes: then all is good ...if no: then at least I know not to factor that in upon T/O.

maybe these pics will help to explain.... ...at three different altitudes: 060, fl100, fl140 default weight and fuel ~~~~~~~~~~~~~~~~~~~ FYI: CTOT appears to be hit and miss. I've taken to testing whether it's active or not before each flight. I've noticed when not available I'm able to push the TL to max (at any time of flight) w/o going into red. They (eng rpm) max at 100 and stay there until TL are reduced. I've learned to embrace the mystery... ;-)

Typical cruise altitudes are between 080 and fl140 with ias of 210-220 kts . TL setting of 85%-90% trq . CL settings apprx 13000 On final before GS capture apprx ias 140 - 120 kts .. flaps 20-30... CL to max ... (flaps help lower the nose by a deg or two) default fuel and weight (thought they may have been a contributing factor)

Apologies if this has been approached before but have not been able to find any mention of it. The latest Saab ver (1.5) for x-plane 10.5 seems to always fly in a pronounced nose up attitude. Whether at cruise altitude (2-3 deg) or approach (5+ deg). Anybody else experience this?

Well...back to the ol' drawing board: For me , this version of the Saab (1.5) appears to be a very unstable model. Just finished a session where upon as stated before: NO CTOT available. .. upon arrival: came to a complete stop on rnwy and required TL beyond the flight idle to begin taxi ... tiller disengaged ( i mapped nose wheel hyd to key stroke) ... lost ability to brake ( had left the rnwy at that point so this is a little ambiguous ) ... there appears to be an exaggerated nose up profile to this model This is not a new model for me in xplane (10.5) ... and I've probably flown this plane more than any other in the sim. Wondering if a reinstall is in order. Thoughts?

Just did a whole systems check and CTOT does indeed seem to be working just fine. They even worked with L/R gens off line... surprised by that. They engage at the 70%+ torque range and am able to dial +/- at the console and arm/disarm while in torque range. So I'm at a loss to explain the non events unless it is a loading issue. (?) Thanks for the response tho' .... cheers

Dwnloaded latest Saab 340A (1.5 ) for xplane v10.5 CTOT no longer works. My understanding is: the system "kicks in" ~ 62% + and increases rpm to what is dial in at the preset... ...none of that is happening. Thoughts?

Hey JGregory...... my bad. You know I've never used or was even aware of that pref menu? Your question made me go back and route around some more and voila! I'm guessing the previous ver default was ' zoom on ' and I never had to go there. Thanks for the heads-up .... you're a gem.

I'm still flying x-plane v 10.5 (?) ....after update (v11) of the ever wonderful Saab I've lost the mouse scroll wheel zoom function. All else appears ok.

Update: I may have stumbled upon the reason. Comm1 is slaved to the garmin (comm2 isn't which explains why it doesn't show the same anomaly..) If you notice in the screen shot, the garmin stby shows the same freq which is normal. However if i change freq's using the garmin inputs, and i'm careless (as apparently i was at some point... i rarely input via the garmin controls) and i leave the stby freq in a non-usable format then the saab comm1 is slaved to the non-usable format. I actually didn't catch that when i sent the screen shot but only after starting xplane again to solve the "problem". ...another case of pilot error...man, i'm batting 1000.... :-p GOJAYSGO!

...can't answer to plugin conflicts. The few I run have been in the box for some time now (as i recall) ... no to saitek..i use a twist stick. ....the screen shot shows the set up anomaly.... the stby freq will remain in that 'format' until i switch to stby again, upon which i'm good to go scroll to a proper freq. Log.txt

I've noticed comm1 radio is not able to recognize a freq' with out having to switch into stby and then input the desired freq'. Ex: Say, when trying to input a local Atis freq...the stby numbers will be "off" .. formatted wrong (ie: the decimal numbers are off by 1 or two digits ... and not recognizing any attempt to input a proper freq'. ...then switch to stby again and now the numbers reflect the proper format. Comm 2 radio reflects none of that behavior. ...apologies if this has been noted before. ...thoughts?

Apologies again! It appears the pilot forgot about the volume sliders to the left of 1st seat! Everything works as should. Boy, do I feel silly. ;-p

Apologies if this topic has been discussed before now. I'm unable to receive ATIS info, verbal/script , through the Saab com1 radio. Everything is operational. I opened x-plane's default 'barron' and received atis immediately using the same freq's attempted w/ the saab. I received both verbal and scripted messages w/ the default barron. I seem to recall others flying the saab (youtube) as in fact receiving atis info... so i feel i must be missing something. Everything that pertains has been checked in x-planes sound menu. I'm afraid i'm stumped. Thoughts?