Iain

Make sure your controls are centred and calibrated, you can also put the control outputs as data refs on the screen. Also make sure aileron and rudder trim are neutral. Best way is to assign a key to centre them to be sure.

Wunderbar!

Hi Jan A very old topic, I know! But any chance this update can be added to a future patch? I have no idea how much work is involved and since I don't see others asking about it them it doesn't have to be a high priority. I can't get ATIS at EGPH, 131.355, easy enough to check on Skyvector, but you know, sometimes XP isn't right up to date. Cheers Edit: Actually, you know what, I will just change the freq in the apt.dat to 131.350 and it will work then!

I've not heard any complaints about autobrake not working for no reason, usually there is an explanation for it, such as toe brakes being applied by pedals, or spoiler not armed etc. I can say in the last few months I have landed 100 times, every time the reversers are on before the nose gear touches, and the autobrake works just fine. I done 3 short hope last night with the latest beta (KPVD-KBED-KASH-CYQL) and all working perfect. Here is my landing at EGPE a week ago, autobrake 3 (prob should have used max) and you can see I switch to manual braking at 1:21 (autobrake disarm light isn't visable). Again, no manual braking, reversers active as soon as mains touch, and never any problem. You would not get any autobrake in this situation?

AviTab! -300 pilots use pen, paper, stopwatches..never ask about VNAV limitations, and carry a sextant for Oceanic crossings!

Perfect explanation. No idea why I was using it. Will test it later and see if that relates to my C of G question also.

Having done far too many 2000nm+ flights in this aircraft, I can also say I have never seen a drift of the line in LNAV, so I doubt it's to do with the route length.

PROBLEM SOLVED! This happened on a few recent flights, my latest flights however work fine. Pretty sure I entered a value on the ACT PERF INIT - PLAN/FUEL value! I don't know why, never used this line before. But now I see it does some funky stuff with the GW! I still have to check if this caused the incorrect GW when I did a turn around, I think there is a good chance it will. Can you explain in a few words what this line does? One other thing, to save me starting a new topic. My takeoff C of G is always 4.2, regardless of data input. Is this correct? Again I thought this value changed in the past. Maybe a user problem again, or maybe best to take the trim value from another source. 4.2 does work fine though so it's not something I brought up before. Gruss aus der Schweiz

Ok, will do a bit more testing and see if I can work out what is going on Cheers Iain

Hey team I have a small issue which is confusing me somewhat. My GW as I cruise along is not updating, VREF speeds for approach are the same at start of cruise or TOD, OPT FL in CRZ page is always the same. My current flight is slightly illegal as I'm flew across from Prestwick to Providence and now I'm on my way back, on these flight you really notice it, my normal flights are maybe 1-2 hours long so maybe I didn't notice this. Can't say when I last remember this working correctly, changes I've done recently are updated from 11.41 to Beta about 1 week ago, updated Navi data from Navigraph 2 days ago. Current flight is on the only Eastbound NAT there currently is, passing south of St Johns. https://public.airspaces.app/ Also, I am sure I had WPT data (Zulu time at the WPt) on the ND before, by pressing WPT on the pedestal, it used to appear either over the magenta line or in the ND corner. Or maybe I'm confusing this feature with the -800 version? Thanks for any feedback.

I enjoy this airport, fun place to land, at night and during day light. Usually quite breezy. This flight was a cargo flight from East Midlands. https://youtu.be/OoUdlkRlJpE

I tried but could not reproduce this missing texture. I used a different livery but I guess that shouldn’t matter.

Just started a flight, all my camera positions have gone? I thought the files wasn't going to be overwritten in this patch, maybe I'm wrong, no big deal, 10 mins to set them up again only. I also don't have any missing texture problem, 11.50 b14, external looks good to me.

Then don't touch it!

It’s an easy fix, and I only get it on first loading of the aircraft so no worries.

That’s not the problem I have. I have the hiss sound, extremely loud. Then change cam to free roam and move the camera to the other end of the runway or further, 10km away and I still have the hiss sound, same volume, regardless of camera location. Load turn around again and then the hiss sound goes away and is only present when very close to the aircraft.

Cheers Jan 2.21GB. the ortho folder is 2.2Gb, so yeh, hopefully a future fix.

Ok, some testing done. Problem can be switched on and off by toggling the WX on off toggle switch, so your theory is dead on Ben/Jan...you deserve a cold Paulaner! I also tested the Zibo (sorry I mention that here!) and it has the same problem, but only when you switch on the TERR function to the left of the MCP. And it's always off by default so never showed on my tests. JF Hawk, it also has a problem, not the same, but a a very sharp drop in frames like a massive stutter, but it happens at any location, so I think that's a Hawk/Vulcan issue. Well done lads, again, a one of the reasons I love this aircraft is the customer support! I'm happy to fly with the WX off for ENGX, I guess Boundless would have to lower there detail of the mesh etc maybe they would consider that.

I will test this at 18:00 CET, fingers crossed!

Point 1 is the same issue I have. I still have this issue, when loading in turn around, go to external, I have a really loud air hissing sound that stays the same volume regardless of camera position. I just reselect turn around again it the sounds behave normally. I think this only happens with the aircraft is first loaded. I could try and record it to show how it behaves.

Ok, just switched to Beta, had to update my Nvidia drivers, ran it, and it's exactly the same problem. Pulsing with turn around, ok with cold and dark. Game looks much crisper, better colours and contrast and smoother. But doesn't resolve the problem. I'm just updated 20 mins ago and it's build 13. I'm sure your busy with 1.32, so concentrate on that I will try some things to see if I can get closer to solving this. Cheers

Put it on your to do list and get to it when you can. I can avoid it for the future no problem. Would be good to know though as it could pop up again for a larger number of users and be more problematic to fix. I think it's time to switch to Vulcan, good reason to do it. Might manage this evening, if not then tomorrow. Cheers

Oh, I run 11.41, never went beta. But was planning to make he switch soon.

Eh..no. That used to be a thing a while ago , how do you switch to Open GL?

It starts about 10nm out, 4nm away gets severe, even at 9000ft it's severe when overheard, and gets slowly better until at around 10nm it goes away.