Little issue here. Not sure who flys for a VA and tried to use the Q400 for flights, but when Ive tried, even though the preflight it recognizes the aircraft, it will not see the engine start.  Ive tried some different configurations, perhaps wrong in setup procedure, but nonetheless it will not see it. Perhaps something to do with the external model outside FSX or something?

Its a very well known subject and they, Majestic, are aware of it.

Little issue here. Not sure who flys for a VA and tried to use the Q400 for flights, but when Ive tried, even though the preflight it recognizes the aircraft, it will not see the engine start. Ive tried some different configurations, perhaps wrong in setup procedure, but nonetheless it will not see it. Perhaps something to do with the external model outside FSX or something?

 

There is a workaround, load everything as you would, start engines in the dash and press CTL-E, and bingo, VAFS will register engine start and away you go.

 

When you land, shut down your engines and press CTL SHIFT F1 and VAFS will register engine shutdown.

 

Works a treat!

There is a workaround, load everything as you would, start engines in the dash and press CTL-E, and bingo, VAFS will register engine start and away you go.

 

When you land, shut down your engines and press CTL SHIFT F1 and VAFS will register engine shutdown.

 

Works a treat!

LOL  CTRL-E to start?? I havnt done that in years. 

Ive deleted nearly all keyboard aircraft commands so I gotta reprogram them I guess. I hope this would be a temporary fix though. Kinda lame to do it that way. 

 

But thanks for the workaround. 

Try without reprogramming it, you don't need to actually start the engines with it, just VAFS to register the key press.

 

It might work in your current set up, as you can't start the dash 8 by pressing CTL-E

I found GSX wont register the engines been shut down when you arrive at the gate. But I tried the key press to shut them down and GSX was happy. It had no effect on the aircraft though.

Alright thanks for the tips. Will do. 

Crap it didnt work

 

Just tried different mappings of engine start 1, and auto engine start.   Then tried FSUIPC mappings. Still no go. 

 

Saved the flight and reloaded as well as VAFS. Still nothing registers. 

 

Is this a hit and miss thing?

Still not working. I got it to work by loading another aircraft usually a prop, and then back to load up the situation saved of the Q that was started. VAFS then recognizes it but then some things are not working. Like the gear, steering, ailerons, etc. 

 

Ive just questioned VAFS on whats happeneing, and they say its on Majestic to patch it up to work through FSUIPC.  Majestic says they are working with VAFS to give them the proper parameters. 

 

So which is it?  Everyone is pointing fingers at the other. I just want to fly the Q for my VA. 

Is there a patch in the works for this?

 

 

Its a very well known subject and they, Majestic, are aware of it.

 

 

 

Majestic says they are working with VAFS to give them the proper parameters. 

 

I'd say that pretty much sums it up.

 

 

I'd say that pretty much sums it up.

 

The point was, VAFS didnt say they are working with them. I was just told its up to Majestic to work with fsuipc. They didnt appear to have any interest in solving it With Majestic. 

That is strange. I just load up the Q400 with nothing special, no specific situation, just in its normal default state which is semi-dark. I proceed to start both engines, and hen I am ready for taxi, I press CTL-E, wait a few seconds and VaFS recognises engine start and away I go.

 

I hope you can get it sorted, with the latest update, VAFS now recognises landing rate and engine shutdown.

This is definitely a Majestic problem. My software has the same issue - they are not working with FSUIPC to record the aircraft parameters.

 

Cheers!

Luke

That is strange. I just load up the Q400 with nothing special, no specific situation, just in its normal default state which is semi-dark. I proceed to start both engines, and hen I am ready for taxi, I press CTL-E, wait a few seconds and VaFS recognises engine start and away I go.

 

I hope you can get it sorted, with the latest update, VAFS now recognises landing rate and engine shutdown.

How is it that you can have it recognize by a simple CTRL-E engine start and others cant. Yes my mapping is correct for it to be the Engine Autostart. 

So what is it about yours that is different?

That is strange. I just load up the Q400 with nothing special, no specific situation, just in its normal default state which is semi-dark. I proceed to start both engines, and hen I am ready for taxi, I press CTL-E, wait a few seconds and VaFS recognises engine start and away I go.

 

I hope you can get it sorted, with the latest update, VAFS now recognises landing rate and engine shutdown.

Same here, and I have no idea why others can't get this to work as I have.

 

 

Sent from my iPad using Tapatalk HD