The A2A Simulations Community

Went through the startup sequence as per the manual, had the trolley and wheel chocks set, removed them, applied a little power, Spit didn't budge.

Tried many many times with all sorts of configurations, making sure the brake indicators are showing off, but no way will the aircraft move forward.

Aircraft flies well after using slew to get me up in the air, and will land OK, and do touch and goes, and will even taxi once landed. But it won't move from the position it is started in.

Any ideas?

John
Canberra

Startup airfield is Forbes NSW at the moment, Spit is parked on the tarmac ramp.

I haven't had that problem but maybe try a push back (shift+p) to get things moving?

_________________
"If other eyes grow dull, other hands slack, and other hearts cold in the solemn trust, ours shall keep it well as long as the light and warmth of life remain in us."

Check the brakes gauges to see if they're on or off. While you're at it - is the parking brake on?

Other could be prop settings - try full fine if you're on the constant speed or the variable pitch props. If you're still having this trouble on the wooden prop that can't be it.

_________________
Tore Johansen
member of VPA - Virtual Pilots Association

Somebody mentioned this, I read it earlier today. I think it was something to do with battery. From memory, he did a test and left all the lights on to run the battery down. Started the Spit and when he applied power it wouldn't move. Scott thanked him for his input, but couldn't recreate it.

I think that's the gist of it anyway.

_________________
Tony

Intel core i7-2600 3.40GHz, 16GB DDR3-1600 Ram, GT430 1GB Graphics, Windows 7 Premium 64bit, FSX Gold Acceleration. REX 2.0 overdrive, TrackIR 5, Saitek X52Pro, CH Rudder Pedals, Saitek Cyborg X.

Thanks for the responses but none are applicable. Brakes are working fine according to the brakes gauge and post landing behaviour. Battery is a fresh charge. Pushback makes no difference. Might have to log this with the developers to nut out. Spit is flyable but essentially unusable for me at the moment!

Which Spitfire and which prop mate?

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

I've only tried the MK1 version so far, but it happens with both props...

Ok,

Try this. Load up a Cessna..default. Take off, land.

Set ALL switches to off then SAVE the flight. Now change aircraft to the Spitfire Mk I.

Startup and see if you can now taxi. If using the DeH prop make sure the "Bike Pump" is pulled all the way back (out) to put the blades to fine.

see how that goes.


Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

OK Will try when I go flying in a while, and thanks.

That seems to have fixed it, will fire up FSX from desktop later and try loading the Spit from that saved flight again, and if you don't hear from me again you know it worked permanently!

Thanks for the help.

No worries...hope t'is permanently sorted for you...

D

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

For add-on aircraft to work properly it's imperative that you save a completely shut down default Cessna 172 as your default savegame. That way it's guaranteed that you can load any flight you wish from the main menu with your aircraft of choice without having issues. Works for me.

_________________
Happy Landings
- Patrick

Sorry, Jigsaw, but that's not true and causes more problems than it solves. I say this from many years of having to get people to change to a default aircraft, turn everything ON and then save the flight again. Otherwise the switch that isn't in the add-on aircraft (say, for instance, "battery master" or "avionics master" in the Spitfire) isn't on and things don't work.

The best, safest and always recommended starting state for loading an add-on aircraft is via the default saved flight: default aircraft, engine running and switches powered on. Then you can switch to your add-on, then shut it down and all of the functionality of the sim knows exactly where it is.

Ian P.

Ian,

Well, in this case and in many others it has worked. I've been using it without a problem since FSX released.
Interesting to know that it causes problems in some cases...cheers, but with the Spit in each case through beta and onto release, it has solved a huge number of problems.. I always recommend that the aircraft is FLOWN though before being manually shut down...


Anyway, as said..interesting to know it causes problems sometimes


cheers


Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

I can't say I've experienced the problem in the Spit, so it may well be that A2A are just better coders than most and have covered the contingency...

The usual problem is the avionics master switch, or the default generator switch. So many developers of add-on models (particularly complex airliners) don't implement those, or don't code them to automatically switch on at aircraft load, that almost all "it doesn't work" problems are resolved by loading the default C172, switching the master switches on, then switching back to your add-on.

In almost all of those instances, the user having the problem has created their own "cold and dark" saved file state and switching that back to the default startup flight resolves the issue.

Gotta love FS and its almost infinite number of options for how to configure it.

Ian P.