The A2A Simulations Community

Hi all,

A small question here, concerning the Accusim Spitfire.
I remember clearly that when a flight is ended and the user quits the sim, the Accusim module "remembers" in which state the plane was, in terms of fuel quantity and damage.
However, I noticed that even though I always switch everything OFF when I reach the parking, each time I launch a new flight I get the following situation:
- fuel cocks are ON
- generator is ON
- both mags are ON

The rest of the status, the fuel, oxygen, oil, cartridges etc... is saved correctly. Is this normal ?

You need to set it in the Cold and Dark state.And set your default aircraft in the same state all so
I have my B-17 as the default aircraft and all planes start in the cold and dark state

_________________
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

My default flight is set with the default Baron cold and dark, with all systems OFF.
I didn't use the Spit during the creation of the default flight.
The P-40 stats with everything OFF as it should.
The B-17 and the B377 have their magnetos and master ignition set to ON when I start a flight, but their mixtures are OFF.

However, default flight or not, I thought Accusim was supposed to remember how my switches were set from a flight to another, and it seems that not the case. The "Cold Start" button is a good workaround of course, but I just wanted to know if this situation was normal or not.

There are some functions which are difficult at best to determine the initial state of.
Microsofts extensive use of "toggle" KEY commands instead of "ON", "OFF" or "SET"
causes myriad problems, particularly where miltiplayer flight is concerned. There are far
too many controls whose states are only capable of being changed with a TOGGLE command.
When I write XML code, I always use the ON/OFF/SET functions if available. That way there
is no ambiguity.

I have noticed that reloading the saved flight a 2nd time, after hitting "Fly" , will sometimes
"pick up" some of those missed states. For me, it is not an issue. I just run through my cockpit
checks and varify that all controls are in the required state.

_________________
Paul


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

I'd also like some clarification on this. I have the exact same issue. Not such a big deal but I was somewhat confused after reading the changes in 1.1 and still noticed that after I shut down, when I returned for my next flight, my engine was running. It'd be nice to get an official word from A2A on how this new 'saved' feature works and how to properly use it. If it's in another post can someone kindly post the link?..thanks

My Spitfire also loads often with the engine running (and all temp guages hot!!!) or as mentioned with mags,generator and fuel cocks on sometimes the trimming jumps when I move the trim wheel from 0.0 suddenly to +6.0 (I always check this on the ground before take off!) and it still "sticks" sometimes (won't move!). It is worse when it is different everytime as you never know what to expect.
Although it doesn't happen with the other A2A planes I found a cure for the Spitfire. I now load a standard cessna, close everything down and then load the spitfire. I still need to click the on cold & dark.
I only hope an update will come with the Mk.5

Happy flights

M. Jordan.

"sometimes the trimming jumps when I move the trim wheel from 0.0 suddenly to +6.0 (I always check this on the ground before take off!) and it still "sticks" sometimes (won't move!). It is worse when it is different everytime as you never know what to expect."

This sounds like the FSX autopilot has been enabled (the "z" key). That would run your trim to the max
on the ground, I believe.

Paul

Hi Paul
You wrote: "This sounds like the FSX autopilot has been enabled".
Thanks I've read of other people with that problem, it still doesn't explain the other strange happenings when loading the Spitfire though . Is there any way to disable the autopilot?

Happy flights

M. Jordan.

Paul,

I don't think this is soley related to autopilot...I am getting this all the time since I installed a Helical pot as a trim (5 turn of which 4 turns are calibrated in).


D

_________________

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

Hi Paul
If it helps I'm using the "Pro flight Cessna trim wheel" from Saitek,
it only jumps as I described with the Spitfire.

Happy flights

M. Jordan.

I'm not familiar with that trim wheel but most controllers need
to be moved initially for their positions to be sensed and the
appropriate data sent to the sim. I've not had a chance to take
a look at the trim implementation in the Spit or the encoding
from the trim wheel so I can't speculate on what might be
causing the "jump".

My initial post here about the possibility of the FSX autopilot
being engaged and running the trim to max was based on
having observed that behavior when I had accidentally
hit "z" in the process of getting the cockpit ready for takeoff.
That doesn't appear to be the case in your situation or
Darryl's.

Paul