Cam

Mate, I appreciate all the work that goes into these add-ons - I have also been the target of customers who find bugs in my software. One thing I do understand is the effort and cost of testing. I know my comments don't help fix the bugs, but I cannot fathom why the testing doesn't identify them if it is so rigorous. Thanks and all the best in resolving our bugs - I really, really love flying this aircraft and want to complete successive, successful flights again.

Hi guys, Test flying today at YSCB and experienced a range of repeatable problems as described below: - Aircraft started great - Selected VOR 116.7 on Nav1 and ILS 109.5 on Nav2 - Nav1 selected, HDG mode selected and Climb mode set at 140. - Took off normally and engaged AP normally. - Turned 180 degrees right using the heading knob (HW yoke rocker switch) to intercept the outbound 150 radial from CB VOR. AP Nav mode engaged and radial Intercepted and flown. - LOC 14nm out I selected HDG mode on AP and turned right to intercept the CB ILS LOC (348) at 30 degrees. - Slowed to 175kts and selected Nav2. LOC lock achieved. Selected APP on AP and GS lock achieved. - Selected Nav1 and then re-selected Nav2 (as I was trying to replicate a previous problem) and Nav2 would not select (no light). VOR1 was displayed in the AH as well as GS lock. It flew the Nav2 ILS LOC and GS. - Selected UC down using HW lever but no red lights (Sim UC lever went down but no gear down). Hyd pump started running. Selected flaps with HW lever but had trouble finding the detent. Used the Sim flap lever and also had trouble. - Hyd pump kept running and I could not turn it off or even open the guard. Anti-skid switch also non-responsive. Throttles and CL non-responsive. - I tried a range of other things including AP disconnect (horn would not cancel on either Sim Yoke button or my HW yoke). Selected GA, jiggled with the flaps to get them retracted and finally I got my throttles and CL back and the Hyd pump stopped. - This is repeatable.Log.txt Log attached. Good Luck.

That's nice to know - I'll not debate the point any further, although I do note all the bugs reported herein. Cheers

I'll do some more flying this weekend and let you know. I did get a console error message, but that was from manipulating one of the HDG/CRS knobs - can't remember which one, but I took a screen shot that i'll provide later. Cheers

I totally understand what you are saying, and that is why software developers establish test cases and test as they make changes - to minimise the likelihood of bugs falling through the cracks. Yes, they won’t catch them all, but we seem to have introduced a lot with the v1.6.x changes. Guys, I love this aircraft and the work you’ve done, but we’ve gone from a flyable v1.5.1 to something that has too many bugs for a successful release. Very frustrating. I’m not ‘stirring the pot’, but as someone who has developed and released software, I can’t understand this. Cheers and all the best in getting us a working aircraft.

What are you talking about. These are professional software developers who understand testing regimes - particular regression testing.

The flap mapping appears to be erroneous mapped to my Honeycomb quadrant lever. I can move the hardware lever to max but the aircraft flap lever does not move - flaps move to 15. It is not consistent in what it does and jiggling either lever may or may not get things going again. I have my hardware lever mapped to Xplane Flaps.

Flying an intercept course to an ILS approach and tried to adjust my hardware throttles - no response from the aircraft throttles, no response from the engines and no movement of either the green box or yellow lines on the TQ Viewer. Tried to move the aircraft throttles with the manipulator ( both together and individually) - the yellow lines moved but no engine response. Also, the engine rpm dropped to 80% which I don’t think is supposed to happen (CLs at max). edit. After pausing the sim a couple of times and then changing to heading mode, the throttles worked again. edit 2. They then promptly failed again. CLs are not responding either.

Yeah I get that. But this is such a simple change that only involved turning a knob - how could a tester miss that?

Out of curiosity, I can’t understand how this would not have been picked-up during LES testing after implementing the change.

They would not move at all, even the hyd pump cover.

I also have the same problem.

I also had the Hyd Pump running continuously in-flight after selecting U/C down. I could not turn it off manually as the manipulators would not work on either the Hyd Pump or the adjacent Brake Anti-Skid system. Hyd Pump stopped after i jiggled with my hardware flap lever.

My ITT is also erratic and I do not have EFM activated. Same symptoms as above.

You have to assign switches to them. There are now commands for each.

YSCB Canberra Australia - 109.50

Your absolutely right. I just checked the Saab 340B Instruments and Recorders Manual - 340A is likely the same as they are fed from the ADC. Thanks for that.

Hi, Just downloaded/flew v1.6.1 for a quick flight around the flag-pole and found the following issues: 1. ILS symbology not showing (reported on my other thread with JGregory) 2. ITT indication. When advancing the CLs from Start, through Unfeather, Min and to Max (slowly), the ITT seems to rise very rapidly to max temp - this seems like an anomaly. 3. Pilots Altimeter. The needle does not move until you have power on and turn on the LAVION switch (co-pilots is fine). The needle then does a rotation and settles on the correct indication. Same when you turn off the LAVION/power, one rotation and then stops at the 12 o'clock position. 4. I still can't map my Flaps lever (Honeycomb Quadrant) to get the flaps working as they did on 1.5.1. The PLs and CLs are heaps better. Cheers

Hi Mate, Still no joy. No Runway or GS guidance symbology on either pilot or co-pilot displays using Nav 1 or Nav 2. Also, when using Nav 2, VOR2 is displayed vice LOC. ILS captures and flies the LOC and GS, but just no/wrong symbology. Cheers

Will do.

I flew in to YSCB on a VOR radial using Nav1 and the AP. I then selected HDG Mode to vector myself on to the ILS Approach to RW 35 using the correct frequency in Nav2. I selected Nav mode on the AP (after pressing the Nav2 selector) and got a lock onto the localiser. I then selected APP Mode and and got a GS arm and then a GS lock. However there was no GS symbology on either of the EFIS displays. I know I was on the GS as the aircraft descended as and when it should. The German 530 was not in GPS mode. On the ground I tuned in the ILS frequency to Nav1 and got the symbology. Also, with Nav2 selected, the Course 1 knob moves the Course 2 needle in the HSI. All works as expected with Nav1 selected. Finally, when in GPS mode and flying to a flight plan to intercept an ILS approach, the the AH symbology does not change to LOC when you switch to Nav1 and an ILS approach. 530 not in GPS mode. cheers

Not stirring the pot, just ensuring he is an informed buyer. Regardless of individual hardware scenarios, realistically, if a guy with a 10th generation i9900K, 32M of ram and an rtx 3090 has difficulty, even in VR, then I think that says a lot. I get the ‘settings’ approach being proposed as the fix, but from all the threads being presented, perhaps this software is ahead of current hardware capabilities. Not a criticism, just stating the obvious from what users are being advised to do to get it to work properly with the new features. Cheers. sorry, that was a 9th generation 9900.

Before you update your video card, look at the post where a guy was having problems with a new rtx 3090 which has 24G of vram.

Thanks so much. After jiggling with the checkbox I got both the joystick Andy rudder pedals to work. Cheers.

How is everybody steering on the ground. Nothing works for me - not the mouse, pedals differential braking or anything that works on v1.5.1. I had the tiller selected.