MJC Q400 x64 Profile Beta

Slayer

Beta version of Q400

Please post any questions or suggestions here and I will try my best to implement them within reason.

I still need to implement the EFIS again but wanted to get something out so you can use the MCPPro with GIT again.

There are a lot of overhead buttons and switches in the profile already. If you are building a custom profile I will not change the names of bespoke events and you can use them in your custom profile. All you will need to do to get the new bespoke events I create is to open detective and click the button to delete all bespoke events, then click the button to import the new mjcq400.xml file. This will keep your assignments but give you access to new bespokes as I create them.

I'll try to update the changelog file as I make progress on it.

billstewart

Hi Steve,

Any more progress on this? I've been trying to figure out stuff on my own, but not having much success..i.e. Found how to turn on Autofeather, but can't turn it off.

Slayer

Got sidetracked with the FF757 and FFA320. Haven't done much on this but I'm off the week of Christmas so hope to finish it then.

Slayer

Bill. Almost everything that I use is in the profile, what additional buttons and switches do you want to see included? Post a list of what you would like and I'll put them in.

billstewart

my bad.. I thought you were still continuing with things like EFIS stuff and radios. I'm slogging my way through but it is painfully slow. Can't seem to get the wx/terrain button to work. I see that it is #226 and when I create mouse click event, I can get it to turn off, but can't get it to turn on.

dr1980

Thanks for your work on this, the MCPPRO is working well. Looking forward to seeing the EFIS update.

Slayer

Ran into a snag with the EFIS stuff lots of it not working as expected. Some of the Fake Lvars are firing the wrong buttons and mouse clicks aren't working right for some of the buttons. I'll ask Steve to look at it:

For instance I tried EFISdata_->EFCP_controls2.button_WXTERR_pressed is pushing the FUEL SYS button instead of the FO WX/Terr button. EFISdata_->EFCP_controls2.button_FORMAT_pressed is pushing the DOORS SYS button instead of the FO Format button

Never tried the fake Lvars til now because I was too lazy and didn't want to redo the whole profile, but now it's the only way forward.

I suspect not many people used the fake lvars as it wasn't compatible to my original profile so these might have not got fully tested

Slayer

new beta, partial EFIS , new blanking routine.

robains

Hi Steve,

What are "fake Lvars"?

Cheers, Rob.

Slayer

They are hard coded into git, so no need to do write / read codes anymore, he basically aliased those into LVARS that you can directly access in the detective and they match the list provided by Majestic.

Slayer

Steve did some testing on his end, looks like a Majestic issue or code change causing problems. I was going to post on their forum for a bug report but forgot. Ill ask over there when I get home from work.

robains

Oh I see ... yes those fake LVars would have been very handy!! Does the old method still work? I haven't touch Q GIT programming for a while. I fired off an email to Oleksiy and Simeon. I plan to return to the Q GIT programming because the Q has got to be the most performance efficient and feature rich aircraft I have in my hangar for P3D V4.x

Slayer

The old way doesn't work in 64 bit for an unknown reason, so my old profile had to be redone. I started experimenting and found that the fake LVARS did work though.

The two are not compatible and cannot be mixed together at all.

Mouse events still work with both versions except I still haven't mapped them all out yet. My new profile is using a mix of mouse events and fake LVARS. I prefer the mouse events for momentary push buttons or toggles as there is no need to make an on event and off event. Fake LVARS are good when you need to read data or have to set something specific.

The fake LVARS also don't require a monsterous start event anymore either so it seems a bit more stable but you may fine tune your delays on the MCPPro to get things more responsive as the Q pumps out data every frame I believe.

dr1980

Thanks for doing this profile. I'm having an issue where after takeoff my MCPPRO and EFIS stop working. On the ground I can use both without issues to set things up, but on multiple flights after takeoff the displays on the MCPPRO become frozen and the inputs do not register. Anyone else experience this?

Slayer

In my experience its best to restart the software before you setup for a new flight

robains

Oleksiy did get back to me, he indicated a couple of possible changes but nothing related to what you listed above. I'll try to get more detail clarification of changes.

dr1980

Sorry, when I said setup I meant to set up the aircraft for departure. I also start GIT fresh every time I start up p3d and for each individual flight (I can see now how my post last night was a bit ambiguous!)

I decided to do a flight in another aircraft tonight (PMDG 777) to see if the problem would materialize with a different aircraft, but so far (just reaching cruise) I have not experienced the same issue.

rlw9sr

I've had the same issue. The MCP freezes a short time into a flight; there's no problem with other aircraft. I have installed the GIT beta 64 bit and the profile ..122. Any ideas? Thanks

Slayer

Maybe to short of a delay in start. Are you guys using 64 bit GIT or 32?

rlw9sr

64 bit GIT--

dr1980

32 bit here

dr1980

I tried re-installing the Q400 tonight. I've also been having issues with FS2Crew for the Q400 - the first officer keeps saying "1000 to go, alt sel" at inappropriate times, the flight attendant keeps saying hello when I haven't contacted them, FO calls out V2 when I'm no where near V2 and a host of other oddities - so I thought maybe a reinstall could be helpful for both issues. I mention these details as perhaps there's a connection between the two issues.

I haven't tried FS2crew yet but I'm still having issues with GFIT, albeit different ones this time. Attempt 1 resulted in all dials, knobs etc inoperative even on the ground. Attempt 2 resulted in the lights from left to right red yellow flashing red and GFIT froze up. I've attached a text file to this post with both logs.

Slayer

On the first attempt it shows aircraft switched again after the Q400 loaded. That's why nothing would work.

Not sure on 2nd attempt.

Try starting GIT after you load up the Q400 and also maybe try running as admin if you don't already.

dr1980

Thanks, that's odd on the first one as I loaded the Q400 from the opening scenario page. I'll try waiting until the Q400 is loaded before loading GFIT.

rlw9sr

I also tried this but still after ~ 5 minutes the GIT froze in flight--A restart of the Interface did not resolve the issue--

dr1980

Hello, I finally got around trying this again, waiting until p3d is loaded to start gfit as suggested above. I had the same result as before: the first time i run it I can use my goflight devices on the ground and a few minutes into flight, then they stop responding. When i shut down gfit (has to be done through task manager, it won’t shutdown normally) and try to restart it, I get red, yellow, flashing red (from left to right) and cannot do anything...the restart button is greyed out, the mcppro and efis tabs are greyed out.

dr1980

An update on this, I installed the 64 bit version of GFIT today and this profile is now working for the entire flight.

Slayer

Good to hear. Been busy with other things so I haven't had time to work on this a lot lately.

Slayer

Another "beta". I'm not going to do the full thing with radios as I don't use them anymore but this version has a few more fixes. Some buttons light up when activated, EFIS range etc works , YD and AP lights don't work properly yet but nearly everything else does. Please don't pester Steve from Pollypot about this as it's my own profile I share here. If you have my original profile the graphic included with that applies here except I added the WXR buttons on the EFIS. Please direct all questions / comments here.

bigmarty

Slayer, thank you for this. I have not been successful in getting it to work. I think I have followed the install steps accurately including fresh installs of GFconfig and GIT. The MCP Pro does not interact with the aircraft except for the altitude rotary, and P3D crashes. In the installation instructions it says that on loading the sim I should get a warning about loading 'Goflight Interface Module.dll'. This warning does not appear. I have copied the suggested entry to the dll file but still don't get the warning. I am using Windows 10 64 bit and P3D V4.4.
It would be appreciated if you could give me a couple of suggestions as to how to make it work.
Thanks.
Martin

Slayer

I never get that warning either so I don't think that is an issue. Do you have any other aircraft that GIT works with? Are you for sure using the latest x64 version of GIT?