Cam

Nope. Your app is great.

Thanks for the input guys.

Thank you sirtopper.

I set the trim for takeoff to 1.5. I then retrim on climb out, after accelerating, to maintain my climb speed. I then engage the AP and the trim does not move from there. I thought the trim DataRef and gauge would change during AP operation as weight and CoG changed. I manually changed the CoG from one extreme to the other and there was no change in either the gauge or DataRef. My recollection is that the trim gauge moved as the AP retrimmed to account for CoG changes during flight.

This is mainly an issue on climb-out. After takeoff I follow the FD bars and trim to the set climb speed. I then engage the AP. The trim position you see on the screen shots is where it is at for the trimmed climb speed. Are you suggesting that I should not trim for climb out speed and hold it manually till AP engagement? Seems counterintuitive. I have always flown the Saab this way and not had a problem till this version. Notwithstanding, you will see that the trim DataRef does not change at all in any of the screen shots. I would have thought that it would move when I used the AP VS mode to climb and descend. it appears locked at whatever position it was at when AP is engaged. cheers

Yep - you are right, just confirmed it. I have just posted a new topic on this that you might like to read and see if you can duplicate it. Cheers

JGregory, I am still having problems with my Honeycomb flap lever and getting the sim lever into the gates so that the flaps move. I am using a set of gates that fit onto the Honeycomb quadrant and they worked fine with V1.5.x, but the changes are causing me problems. Moving my lever from flap 0 to flap 5 and subsequent down settings works fine if I do it carefully, but moving from flap-down 35 to flap-up selections doesn't work properly unless I overshoot the next selection and then bring it back to the selection I wanted. I remember in another thread you mentioned that you had increased the tolerances on the gates and that appears to have helped with the flap-down selections. Is it possible to adjust the gate tolerances again to help with this? Cheers

JGregory, MJRHealth, I have just done some more testing to try and get to the bottom of the Trim issue I reported for both V1.6.3 and V1.6.4. To recap, Trim works great when AP is not engaged - the Trim gauge moves and the DataRef changes as it should. However, after Take-Off with a Nose High attitude (ie climbing to height), if I engage the AP the Trim gauge and DataRef stay where they were when AP was engaged and do not move until AP is disengaged. The trick to duplicating the issue is to be in a nose-high position when AP is engaged (ie climb-out). If in level flight when AP is engaged, there will be no issues. If the Trim was in a high nose-up position when AP is disengaged (but aircraft in level flight), the aircraft jolts to a nose-up attitude. I ensured that I was using the correct les command for the trim switch and I ensured that no other switches had trim assigned. I have taken some screen shots at various speeds and flap settings (with DataRef)Log.txt, which are attached along with the log (2 flights). Any advice would be appreciated. Thanks Log.txt

Could it be that I have pitch trim enabled on both my yoke rocker switch and the trim wheel of my throttle quadrant. I’ll disconnect the trim wheel and see what happens tonight.

Hi JGregory, I reported what appears to be a bug with the pitch trim (AP engaged) in both the last version and the latest version but have not seen any feedback from you guys (MJRHealth confirmed it). Have you been able to replicate it yet and, if so, will it be rectified in a V1.x.x update. Cheers

Hi guys, Great flight in the new 340 just now, but still a couple of things I hope get fixed before finalising V1.x.x development: - Engines still experience a very rapid ITT rise and slight over-temp (not enough for the OT lights to illuminate) when moving the CLs from Start, through to Min and on to Max. - The trim in AP is still a problem as I previously reported. It gets stuck in a Pitch Up position and neither the DataRef nor Trim indicator change at all when AP is engaged. When AP is disengaged you get a sudden Nose Up rotation (MJRHealth has also previously reported it on V1.6.3). Works fine out of AP; aircraft is able to be trimmed. On a good note, the ILS issue I previously reported now works a treat - thanks. Cheers. Log.txt

I have the same setup and use a joystick button mapped to the les Command to depress the tiller and it works like a charm.

Ok. Thanks mate. I saw it the other day but didn’t think to read it. Doh.

Hi Guys, Just completed a flight from YPMQ to YSCB and ,boy, did I get a lot of ice. A couple of problems/observations from that flight include: At FL190, -9 and rain, the LEs started to ice-up so I put on the Wing De-Icing. The continuous cycle started (with indications), so I looked away. I then notice an impending stall (speed reduction, nose up etc) and looked up to see the De-Icing not working, even though the switch was on Continuous. I switched it off and on again and it went through only one cycle. The single cycle on continuous mode selection just repeated itself every time I turned it on and off. Single and manual cycle works as advertised. After touchdown (with Wing De-ice still in the continuous position from the flight in the hope that it might work) I noticed that it was now working. Switched it on/off again and only got one cycle in continuous mode again. Also, the intakes clearly iced-up as well as the Torque dropped-off and ITT rose. However, the ITT indicated 999 degrees on both engines and O/H lights came on. I was expecting a compressor stall/surge and/or fire warning. I switched on the Anti-Icing and all was good - Torque recovered along with the ITT and we went on for a successful landing. Log file attached, Cheers Log.txt

Ok. Thanks Sundog. I’ll stay with the non-volumetric as it gives me a better experience close to the ground.

Hi guys, Do the memory usage and performance improvements remove or minimise the requirement to reduce the AA settings to 2 and/or screen resolution to get decent frame rates whilst using volumetric clouds, as recommended by Sundog?

I can confirm that the trim remains 'stuck' in a nose-up attitude during cruise as the associated dataref did not change for a whole 2hr flight, even when using AP VS mode for climb and descent. Dataref stayed on 0.5495 and the trim indicator remained at the top of the green section. On disengaging AP or selecting GA mode, the aircraft experiences a very quick and sharp nose-up attitude. Cheers

Wow. I’ll have to try that leg now.

Thanks again. I use the TQ gauge and noticed that it took a while after landing for the red line to disappear - throttles were synced. I was using the iGoDispatch App and it is supposed to adjust the CoG, but it didn't.

Ahhh. Thanks mate.

Just flew from YMLT to YSCB with the following observations: - Selecting the Gust Lock switch with the mouse moves the switch to the left, but I can't get it to move back to the right. I released and re-engaged the gust lock but the switch would not move back to the right. - After good starts, moving CL from Min to Max (even slowly) results in ITT over-temp and over-temp lights illuminating. Using hardware throttles. - During cruise, Trim indicator stays at the top of the green segment and does not move at all during the flight. - Still having problem with using ILS App on Nav2. EADI shows LOC2 and GS and flies the approach. Flipping between NAV2 and NAV1 to try and troubleshoot results in LOC1 working ok, but switching back to NAV2 results in the problem previously reported. EADI shows VOR2 but now AP reverts to VS mode (pressing APP on the AP does not select the GS). - Selected GA due to inability to fly the approach and the Aircraft jolts nose-up, probably as a result of the trim stuck on high nose-up. - Second time around on the ILS approach, aircraft flew above the GS the closer I got to the threshold, again, possible due to the high nose-up trim. - There still appears to be problem with my hardware throttles selecting Beta and reverse after touchdown - all wheels on the ground. - The altitude warning light on the altitude selector panel comes on sporadically after GS capture. - DH works great now. - Log for the flight attached Cheers, Log.txt

Sorry mate. I can’t remember.

I also had it unable to se exactly what I wanted. The hundreds digits would only increment like 150, 250, 350 etc. I could not select 100, 200 etc. I can’t reproduce the problem.

Thank you. I took a screenshot of the Gizmo error but did it wrong. I’ll try again with the update. Cheers.

Fair call. Cheers.