VAFS now recognises landing rate and engine shutdown.

 

If it recognizes engine shutdown, why not engine start. Thats the biggest issue, as the recording can be ended with a parking brake

If it recognizes engine shutdown, why not engine start. Thats the biggest issue, as the recording can be ended with a parking brake

Because their, Majestic, are not "feeding" that information to either FSUIPC or simconnect? No expert but wouldnt think it would be that difficult unless its that external FDE thingy,

Im sure it has everything to do with the external model as this is the first aircraft that doesnt work. 

I was excited to see this post in the VAFS forums. He found something that worked for him. Didnt work for me unfortunatly, but perhaps you might have different results.  Here is his post quoted in case you dont have access to the forum. 

 

http://www.myvafinancials.com/v5/index.php?/topic/2482-majestic-software-q400-and-vafs/?view=getnewpost

 

Well I started this post with the bad news about the Dash 8 and its only been bad news till now. As I had posted that I only ever had VAFS work 1 time with a flight and couldn't work out what I did. Well I was setting up my new cockpit and the controls and playing with the dash 8. So I started VAFS the Ctrl-E started the engines and as we know VAFS didn't pick them up starting so I went for a short fly and still had VAFS running. I hit ESC and as soon as my FSX went back to the menu page bingo VAFS kicked in so I loaded the Dash and done the flight and ended it with park break.

 

Tested this again Dash 8 loaded engines off started VAFS and had it waiting for engines start. Hit ESC bingo again VAFS kicked in and I just loaded the dash again and started it up and im on my way back to YSSY with VAFS working,

 

Give it ago and post back in here that you have it working or if its not.

 

 

bump

I was just playing with this yesterday..

 

 

I am at work now, here is a quick fix.  

ipc.writeSW(0x0894, 1)

I tried one flight last night and it worked nicely.  On your next flight VAFS will set it back to 0 when you start flight.

 

I'll explain later in more detail if you don't know what to do with this.

 

/regards

I was just playing with this yesterday..

 

 

I am at work now, here is a quick fix.  

ipc.writeSW(0x0894, 1)

I tried one flight last night and it worked nicely.  On your next flight VAFS will set it back to 0 when you start flight.

 

I'll explain later in more detail if you don't know what to do with this.

 

/regards

Yeah sorry I have no idea where to place that.  A little tutorial would be fantastic when you have time.  Cheers! 

Create a blank file called  (be sure to get the extention right!)

 

VAFS_fake.lua

 

then edit it and place these two lines in there.

 

ipc.writeSW(0x0894, 1)
ipc.display("Faked Q400 start")

 

Save it in your FSX modules folder

then launch FSX.

Goto FSUIPC and bind a key or button to do an "FS action" and select from the list "Lua VAFS fake".

 

just press the button to trick VAFS.  it will throw your #1 condition lever and throttle to max.  just wait 5secs and bring them back down.  Engine won't actually start but vafs will think it did.

 

/regards

Excellent thanks.  Is this the same as doing the Ctrl-E trick?  Because that work around does not work for me for some reason.  The only thing that works is to hit ESC and reload the flight.  Once I get back in FSX VAFS thinks the engines have started.  

 

I'll give this a go.  Thanks so much.  

This appears to be a similar issue to why the Q400 won't work with the FSEconomy engine.  Perhaps solving one might solve the other, too.

 

 

 Is this the same as doing the Ctrl-E trick?

 

Sort of,  they are both tinkering with the same setting in the end.  I was never able to get any CTRL E  to work.   This bypasses the panel and simply sets the engine as "firing".  (rather ungracefully).

 

/regards