The A2A Simulations Community

Just bought the Spitfire I/II with Accusim a few weeks ago and was very pleased with it at first. Flew like a dream between the all-too-frequent visits to the hangar for repairs.

However, and please forgive me for bringing this up again, but the major problem that I have is the "Spitfire won't move" and "lights don't work" problems covered here:
http://a2asimulations.com/forum/viewtopic.php?f=78&t=23614
between Jan 27th 2011 and Apr 10th 2011
and here:
http://a2asimulations.com/forum/viewtopic.php?f=78&t=23957&start=15
between Feb 6th 2011 and Feb 12th 2011.

I have tried all the solutions suggested even to the extent of doing a clean install of FSX and Accelleration and the Spitfire with Accusim and after one flight the problem is back!

My controls are the Saitek X52 Pro HOTAS Programmed via registered FSUIPC and function perfectly with all other standard and add on aircraft and with the spitfire on the occasions that I've got it into the air!

No more mention has been made of this problem since the April 10th 2011 posting and a vague reference to the long awaited update, which may fix a battery issue!

Can A2A Simulations confirm that they are actively seeking to rectify the "Stuck Spitfire" issue?!! This aircraft looks and sounds beautiful but is currently useless to me!

Ted

Huh I have only had this issue in multi-player and there is a patch coming out when the MK V is released just hang in there
This is a FSX battery issue which doesn't shut off when you stop the Spitfire and let it stand for awhile before going on a flight.
The Spitfire will start on its own battery.

FSX wont let the Spitfire move as it thinks there is no power to the plane, as the Spitfire engine is separate to FSX. The Spitfire engine starts, but the FSX engine required to actually fly the aircraft will not, due to the flat FSX battery. This is due to how AccuSim is written.

_________________
Ron
B-17 AIRFRAME 710 HRS PLUS AND CLIMBING




GIGABYTE X58A-UD5 MB, INTEL I7 950, 12GB DOMINATOR-GT DDR3 RAM, WIN7 64, GIGABYTE SUPER OVER CLOCK GTX 560 TI 1GB GGDDR5 1000Mz, CORSAIR 850W PS, NOCTUA NH-D14,
TRACKIR 5 & TrackClipPro

Ron, thanks for clarifying that. I just could not see how the not moving problem was due to a depleted battery when the engine was working fine!
I look forward to the fix

Thanks again
Ted

In the interim, if you want to "cheat a bit" FSUIPC has an option to make the battery last longer (for ever?) you could just check the box for that?

_________________
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.

Correct Tony.

In the misc section of FSUIPC set the "Extend battery life by...".. Tick that box, and set the variable to 0.

That should solve the problem for now.

_________________
Lukas

Thanks for that, guys! I'll try that solution and see what happens!

Ted

Well, that works as I use it

_________________
Lukas

I have been using that "cheat" or "tweak" (depending on how you see it) ever since I started using the licenced version of FSUIPC... one of the things in FS that annoyed me from day 1...

Andrew

_________________
i7 2700K @ 4.8GHz on air (NH-D14), ASUS MAXIMUS FormulaV, 8Gb DDR3-2133MHz
EVGA GTX670 2Gb, Windows 7HP on RaptorX 300, FSX on OCZ Vertex2 240Gb SSD

I've just encountered this problem - my FSUIPC's battery is set to "0" for indefinite battery life, but the plane won't move. Also, the exterior sounds are not present....not sure what's going on, but it's very irritating. I've tried to fly 4 times today, with no luck....any other ideas as to the possible cause?
Thanks,
Jim

Edit #1...I think I found the problem - GoFlight module switches for starter and fuel cut off were set to off....forgot to switch them to ON....just completed successful flight after switching them to ON...will do another flight to confirm.

Edit #2 - yup, that was it. So, if anyone else uses GoFlight switches for engines, make sure you move the fuel cut off to ON, and start the Spitfire with the engine start swtich ON while pressing the Spit's starter button!

_________________
Jim B.
R/W C172N Pilot
SWVA Captain, NorCal Hub

Thanks for the help
After installing the update I had the same problem, except that my spit decided to "unstick itself" after about two minutes....Ouch!!! it then (if I had the brakes on) tipped straight on its nose destroying 25 hours of carefuly looked after Merlin engine, or it would suddenly taxi at what seemed like full throttle (even when I had the throttle just cracked!).
I tried the trick using FSUIPC and it appears to have solved it
So now I've got the hard (but fun!) job of getting my now overhauled Merlin up to 25 hours again, and then see how many more hours of my flying it can take
M Jordan

I backup my dat files so that I can restore the hours/states when a "it wasn't really my fault" event occurs. Just get in the
habit of saving a copy either at the end of each flight or just before you start the next one.

I have a couple of scripts that save my dat files every 10 minutes but they are system/user dependent so I can't share them I'm afraid.
A simple batch file that copied the .dat files to a backup location would do the job for you with a double-click of the mouse.

_________________
Paul


i5-2500K @4.3Ghz OC - GA-P67A-UD7-B3 - 8GB Corsair 1600mHz

I backup my dat files so that I can restore the hours/states when a "it wasn't really my fault" event occurs. Just get in the
habit of saving a copy either at the end of each flight or just before you start the next one.

Thanks for the tip Paul
I'll certainly give it a try after what happened! Still the update was worth the hassle, I love how the spit shakes and shudders now.
M Jordan

I have found after an unfortunate crash, that instead of pressing the Complete Overhaul button and losing my hours, I simply go into the hangar and replace everything possible in the engine and airframe (red yellow and green) manually. This repairs my plane, keeps my hours, and I don't have to worry about backing up .dat files and stuff!

Joe

dat files can become corrupted and cause problems which will require deleting them , thus it is a good idea to have a backup
file if maintaining your hours are important to you.

_________________
Paul


i5-2500K @4.3Ghz OC - GA-P67A-UD7-B3 - 8GB Corsair 1600mHz

Every so often my spit still sticks dispite changing my FSUIPC battery settings, I now save time by just simply switching on the landing lights and go to the outside view, if I can't see the light on I reload the spit straight away (it's annoying if you run up first and the discover you're stuck!). This has worked everytime so far.
It's good to know about the backup, I now keep a backup of all the Acu sims on the desktop where it's easy to keep them up to date.
Can't wait for the Mk.V
M Jordan