Gregg you really dont need a combo with this aircraft I have a Boeing combo II and I dont even think about it, this is a very nice aircraft I just need to learn it about 1/2 way there and didnt invest much time into it besides I will be doing a paint for it I think you may change your mind when you see it hint hint

I'm having an odd sound problem. Seeing as the support forums are temporarily turned off due to volume overload, I thought I'd post here and see if anyone has input.

 

try setting speakers configuration in windows to "7.1"

 

 

Couldnt agree more. So in depth and I have to use Shift E.  Really?? Im sure they will address this. 

 

BTW anyone have suggestions to how your programming your condition levers if you dont have an independent lever setup? I have everything setup through FSUIPC. Are you all just using the mouse? But I dont see a good way to implement it.  X52 setup

 

I can't see what using Shift+E has to do with the depth of simulation. It's not Ctrl+E. I find it more useful to press Shift+E than to dig in FMS menus with the mouse. Anyway, I've suggested implementing door interface to Oleksiy.

 

I have the X52 too and I mapped the CL to the slider on the throttle. In fact CL have only few distinct values, there is no need to have a full travel control.

 

 

Yes, I have the same problem. In exterior view the engine sound is very quite and dull.

 

you can tweak everything by editing the ini/mjc84.ini file, there is a section for sounds there

 

The FMS modelling is already frustrating. SIDs that don't draw correctly are unacceptable. It's clear that the Nav data isn't being read and interpreted properly. Direct To's don't work 50 % of the time. The track line disappears when selecting a Direct To and LNAV goes wildly off track. Go-around procedures are not depicted properly either - it's a shame.

 

There's a couple of other small bugs - it seems the attitude indicator is 2-3 degrees nose down on the ground - it should read 0 degrees. When tuned to an ILS the DME value jitters to and fro about 0.8 nm as well.

 

well, I am not a Q400 type rated pilot, but this part (and the others) was extensively tested by real Q400 pilots and approved by them. The Q400 FMS is different from the B737's one in many aspects, including how it draws the flight path. For some types of legs you can have an impression that the flightplan dissapears while it's just drawn outside the visible area. The aircraft will fly 60° course to such a leg and the leg drawing will appear sooner or later.

Bear in mind also that there are different versions of FMS on the Q400. If in your real Dash it is not drawn this way, it doesn't mean it's incorrect.

 

As for the attitude, the plane is leaninig forward while on ground, so it's normal to have a negative indication.

 

 

Gregg you really dont need a combo with this aircraft I have a Boeing combo II and I dont even think about it, this is a very nice aircraft I just need to learn it about 1/2 way there and didnt invest much time into it besides I will be doing a paint for it I think you may change your mind when you see it hint hint

 

Okay...lol.  Show me the repaint and let me see some vids.  I have some aircraft that don't work as well with the Combo and it's annoying sometimes but others I could care less.  The Mustang is probably the worst of the bunch with the J41 a distant second..for the most part.  I just use the mouse in the cockpit (as one of my friends gasps in horror "A mouse?  In a cockpit???"). 

Commenting just as a customer here: (don't worry, PMDG's not going to make a Q400)

 

Having tried this a few times, I don't think the plane is flying the psuedowaypoint departure stuff out of KPHX correctly in LNAV. Try the TFD3.TUS departure off 25R. It should be runway heading until 1550 feet, then heading 240 until 9DME PXR, then heading 160 indefinitely awaiting vectors. I'm not seeing it do that at all right now - it makes a wide right turn to the east somewhere - not understanding why because the waypoints in the FMS actually do look correct to me.

I guess you can't use GEX or AES to do a pushback? For starters the wheels dont turn when pushing back, and secondly, the airplane warps back to the starting location. Sometimes it warps underground, and takes off like a rocket forward, even though throttles are set to idle. Also when loading the aircraft using the config utility, going back to the FSX window, the airplane sometimes bounces up and down violently.

Purchased, Downloaded, installed and activated inside 40 minutes, all issues from yesterday seem to have improved.

 

This is one impressive add on indeed.

There you go Greg thats the spirit    :friends: just need to get a handle one the paintkit but what ever I do it will look realistic US carrier and maybe a nice private doing homework now.

When I press F9 it goes to the right seat (2nd officer seat). How do I make it go to the left seat(captains seat)?

 

NVM. I fixed it by adding a "//" in front of hotkeyselect.

 

[CameraDefinition.6]

Title = "VC Right Seat"

..

...

....

//Hotkeyselect=1

Edited April 21, 201313 yr by nzeddy

no problems with activation,however when loading the aircraft the panels and VC are blank and no under carraige on the aircraft.Re installed three times and same problem.

Anyone else had this issue. any ideas and solutions please, completely unflyable on my system.

Very disappointing for me .

 

Regards

 

It's seems there maybe someone on here from JF, so I will try this public forum since I can get no help thru emails.  

 

I purchased earlier  and keep getting failure to install >> ERROR - INCORRECT EMAIL . I sent my request as instructed over 5 hours ago and received an IMMEDIATE auto reply that my issue was being worked on.  I copied and pasted my email address directly from my receipt of payment. I have downloaded the installer with Google Chrome and Internet Explorer with all antivirus on and antivirus off.  I have attempted to install approximately 5 different installers and every attempt ends with INCORRECT EMAIL ADDRESS.

 

Just Flight - you have my $$  -- can I get some help ??  :angry:

Guys make sure you installed as administrator might be part of the problem. Incorrect e-mail sounds like a server issue ?

I've now spent the best part of 9 hours testing out the Q400 and I'd like to give my opinions. Frankly I was surprised but hopeful when I first heard people gushing about the quality. Lots of guys have compared it to the NGX and many have said it surpasses the PMDG aircraft - at the moment I'm afraid they're wrong, the NGX still can rest easy, the Q400 has some way to go.

 

Don't get me wrong, the VC and external visuals are very good indeed. Crisp and sharp with lots of detail. Engine sounds are deep and impressive - from the cockpit, although from spot view they're disappointingly muted. Lots have commented on the detail sounds in the flight deck - well yes, some are good and there is a good variety of click and lever sounds. However there is something about the sound mix that is wrong - too many click sounds sound wrongly placed - small switches make big unnatural clunking sounds when moved, a few don't have any sound at all. The NGX sound set is extremely well blended and natural.

 

The FMS modelling is already frustrating. SIDs that don't draw correctly are unacceptable. It's clear that the Nav data isn't being read and interpreted properly. Direct To's don't work 50 % of the time. The track line disappears when selecting a Direct To and LNAV goes wildly off track. Go-around procedures are not depicted properly either - it's a shame.

 

On the topic of go-arounds - it might be me, but there doesn't seem to be anyway of binding a key to the GO-AROUND button on the power lever. The default FSX command doesn't work with it. Majestic's control panel doesn't allow any special key bindings - this is a glaring omission in a product of this type. Performing a GA by panning your view to click a power lever click spot is a nightmare and not realistic. The same goes for the Autopilot disconnect function - there is no yoke disconnect key, pressing z gives you the wrong indications and visual warnings. 

 

There's a couple of other small bugs - it seems the attitude indicator is 2-3 degrees nose down on the ground - it should read 0 degrees. When tuned to an ILS the DME value jitters to and fro about 0.8 nm as well.

 

Unfortunately there seems to be a major issue with the elevator / trim / autopilot interaction. I've just finished a flight with a nose dive into the ground. The autopilot doesn't seem to trim out the elevator to a neutral position in any stage of flight (you can see this on the PFCS indicator) - meaning that when you disconnect the A/P the aircraft you get is badly out of trim - very frustrating results if you're at 200'. Is it using the default FSX autopilot by any chance?

 

It must be said that documentation is poor. The tutorial is a not very helpful and the systems manual is rather short. The 'checklist' is a weird combination of normal procedure flow and checklists, which is hard to follow. Importantly there are no profiles or flight patterns that explain actions and sequence of take off climb and approach. 

 

I'm sorry for the negative post, but with high expectations and a £40 outlay I feel the comments are valid. I really want to support dedicated devs like Majestic but at the moment the Q400 falls some way short of NGX standards. I hope that service packs and the PRO version can go some way to iron out the niggles. 

 

Adam

 

 

I think you are expecting way too much from an airplane when it is first released. Keep in mind PMDG has had to release quick servicepacks at least once for their airplanes after released to fix problems before. Nobody is denying there might be small bugs here and there, but everyone is looking at the big picture, and the big picture is the Majestic Dash 8 is the most complex, complete addon released for FSX. Amazing quality and so light on frames it seems impossible to be true. After a few patches I know it will be perfect.

 

 

try setting speakers configuration in windows to "7.1"

 

Unfortunately no joy with this. When I have this issue, it seems to be at a pretty reliable time point. I haven't gotten out the stop watch yet, but it's always 13-15 minutes in to the setup.

 

I'm curious what the recommended method for cold and dark is? I have not noticed this issue on my quick test flights where I just take the startup state (I'm not quite sure these have lasted >13-15 minutes ot necessarily encounter the problem). The flights that I have encountered this on though were attempting to start cold and dark. I connected the GPU and then turned off all the battery switches and external power. I'm wondering if this could be having something to do with the issues.

 

Unfortunately no joy with this. When I have this issue, it seems to be at a pretty reliable time point. I haven't gotten out the stop watch yet, but it's always 13-15 minutes in to the setup.

 

I'm curious what the recommended method for cold and dark is? I have not noticed this issue on my quick test flights where I just take the startup state (I'm not quite sure these have lasted >13-15 minutes ot necessarily encounter the problem). The flights that I have encountered this on though were attempting to start cold and dark. I connected the GPU and then turned off all the battery switches and external power. I'm wondering if this could be having something to do with the issues.

 

Same problem here. About 10-15 min after starting preparing the bird from cold and dark and I am ready to start engines og some times also during taxi the sound stops. The strange thing was that this did not happen the first flight I took (tutorial from CYZD-CYUL). But every time after that.

Commenting just as a customer here: (don't worry, PMDG's not going to make a Q400)

 

Having tried this a few times, I don't think the plane is flying the psuedowaypoint departure stuff out of KPHX correctly in LNAV. Try the TFD3.TUS departure off 25R. It should be runway heading until 1550 feet, then heading 240 until 9DME PXR, then heading 160 indefinitely awaiting vectors. I'm not seeing it do that at all right now - it makes a wide right turn to the east somewhere - not understanding why because the waypoints in the FMS actually do look correct to me.

Ryan,

 

How are you?  I hope that you are enjoying The Q4.  Thanks for pointing this out.  I will have a look at it and pass it on to Oley to see if there may be an underlying problem

 

Simeon