@Delta558 Thanks again. The next day, I was able to select "Ready for Takeoff," and discovered that means "Eventually . . . ."
If you wait a while, all 4 engines spool up. So now at least I can get off the ground.
I'll try again later to do a cold start.
BTW, notwithstanding p. 57 of the Manual, saving a flight does NOT save the panel state. Yesterday I saved a flight at 32,000.'
When I loaded that scenario today, I was at 32,000', but no engines on, and the landing gear extended!
Aah, fuel tanks - we're actually just looking at them again for the X-plane version! The tanks are physically grouped into two areas in each wing and then 1 and 2 in the fuselage. Unfortunately, they are grouped differently in terms of which tanks feed which engine! As I said, I'm not sure of the code but you generally need to lower the fuel level evenly across all tanks to achieve a sensible outcome.
In terms of real world, display weight (so lightweight) was aimed to be around 135,000lb - remove all payload bar the crew and adjust the fuel evenly across the tanks until you hit the right area. Should probably be around 30 - 40 % per tank? Then, if trim is a problem, you can use the tray between the seats to transfer fuel to/from tanks 1 and 2.
@Craig-Haskell yep, I uninstalled the last version and did a clean reinstall using the update for FSX:Steam last week. It always seems that the JPT winds down on the outboard engines - I’ve found that I can start them by pressing the relight buttons on the throttles but then it leaves the engine ignition buttons flashing like an eighties disco...
The rudder authority is correct. The Vulcan used nosewheel steering until the rudder becomes effective around the 90kt (from memory) mark which is why you will see the elevons down (stick forward) if you watch take-off videos of the aircraft. Unfortunately, FS has a rubbish ground friction model and you tend to lose NWS too early.
Line up properly, respect crosswind limits, lead with either left or right throttles and occasional left or right brake are about the only advice I can give on that, sorry.
Sorry to say it's uncontrollable on my PC using P3Dv4. I have a list of issues - which may be for me unfamilarity with the Vulcan - but support ticket sent. I thought the Autopilot had been fixed? Currently it doesn't even go to ready state.
@Martin1 No intent to be condescending, the comment about low-level was a fairly flippant attempt at humour! However, the B2 was introduced in the same year Gary Powers was shot down in the U2 and that prompted the move from high level to low level, so the B2 Vulcans only did four or five years of what the original concept was designed around before spending the vast majority of its career (almost 20 years) in the low-level attack role (Blue Steel until 1970, then conventional or tactical nuclear afterwards).
I find flying the Vulcan at low level, with the poor visibility from the cockpit, much more rewarding than sticking the autopilot on, hence my comment. Some of the original routings are described online, a couple of the low-level entry points to the UK low flying system being not far from me along the South Wales coastline and there is also a very good video on YouTube of the last days of 617 squadron's Vulcan time with a planned low level sortie. Obviously not everyone's cup of tea, but whilst I hope the fix gets released soon I don't think the package should be described as 'not fit for purpose' solely on the basis of a non-functional autopilot. Anyway, check your PMs for a potential temporary fix.
Thank you both very much. I've been advised to throttle back to about 1/3 power after take-off which I wasn't doing. Also to adjust the trim with '7' and '1' (num lockoff) which doesn't seem to have any obvious effect. I've also loaded 'RAFVulcanUpgrade'. And have now managed a climb to a decent height. You have to work hard to keep the nose up though. I may return to my Jet Provost for a few circuits