Hi

 

I am using P3DV3 and have just downloaded and installed the Dash 8 pro to my main P3D root file.

 

I then went to follow the P3DV3 beta patch, as shown here

 

2.  Very Critical Step!!!

There is an alternate .dll (mjc84_main.dll.p3dv3beta) which has been supplied for the Beta testing purposes specifically for users of P3D v3 which is located in your PANEL Folder.  Please ensure to re-name the default/original .dll to something like mjc84_main.dll.original, and re-name the supplied .dll to mjc84_main.dll.

 

 

but I cannot find the PANEL folder, and when I search for the .dll, nothing comes up.

 

What am I doing wrong and where should I be looking for the PANEL folder?

 

 

:\\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\mjc8q400\panel

 

I did not have to rename the new mjc84_main.dll, only the old if you want to backup. (That was the case with the Pilot version)

 

Are you sure you downloaded the beta update for the pro version in you user area. Remember to log in with your order number you received when you purchased the Pro version, not the Pilot version?

Many thanks Olmba

One quick question: Axis assignments in both P3D itself and FSUIPC have to be deleted (for aileron, elevator and rudder) if I want to use that Q400's own control interface as described above, right?

 

I didn't bother and it worked for me.

I havent deleted the FSUIPC axis. They dont seem to conflict. Its so much smoother now. Thanks alot everyone.

 

Michael Moe

 

So you got it to work? Great  :smile:

 

What did you change in the end?  Also might be worth sharing your controller como, just in case it helps someone else.

Guess I am missing something, used the settings I had set up in V 2.5 for months with the Q400 Pilot,  and the Pro flies perfectly. 

Guess I am missing something, used the settings I had set up in V 2.5 for months with the Q400 Pilot, and the Pro flies perfectly.

Well unless you have engaged in some INI butchery, you are using the standard FSX/P3D controls interface (that the Pilot edition used) rather than the improved 125hz custom one.

 

Nothing stopping you leaving it as is, but it makes a significant positive difference to the feel.

With the new control interface the aircraft is much more smooth and stable to handle.. Is a dream to hand fly, before i was struggling much more.

Well unless you have engaged in some INI butchery, you are using the standard FSX/P3D controls interface (that the Pilot edition used) rather than the improved 125hz custom one.

 

Nothing stopping you leaving it as is, but it makes a significant positive difference to the feel.

 

I think I have flown this aircraft about 300 hours + and always thought it felt pretty realistic, so I think I will leave well enough alone. Besides, my thinking process doesn't even work at 125 hz  :wink:

I think I have flown this aircraft about 300 hours + and always thought it felt pretty realistic, so I think I will leave well enough alone. Besides, my thinking process doesn't even work at 125 hz :wink:

It's your call, but I have to say I was very surprised what a difference such a minor sounding change made, even on my cheap Saitek Cessna combo. I would go so far as to say it's now the best handling small airliner I've tried (previously the LES Saab 340 in X Plane)

  The new joystick interface is nice, but wait till you start playing with the sound maps. The default 3D effect is quiet in comparision. FYI, I'm using 5.1 surround here

 

regards, Craig

I didn't bother and it worked for me.

 

 

So you got it to work? Great :smile:

 

What did you change in the end? Also might be worth sharing your controller como, just in case it helps someone else.

 

 

Yep and i thank you. Really apreciate your time and effort. In the end all i had to do was using J2 instead for the rudder.

 

Can not believe the difference.

 

Thanks again

 

Michael Moe

Finally solved this 125hz control issue. The problem I am having in P3D V3 is that P3D refuses to recognize my CH rudder pedals, so I had to use FSUIPC to get them to work. So when I edit the ini file I lose the rudder pedals without doing more editing which I di not want to do because that might cause problems with other aircraft. So I decided that the only two changes I really wanted to try anyway were the aileron and elevator changes, so I just made the changes for those two axis in the ini, and left the rudder untouched. Works great now. 

With my saved up points at JF, I can pick it up for $4.

 

Doesn't really get any more no-brainer than that. LOL

Does it work with cockpits? Some of the basic 6 pack gauge numbers were not being output so none of the cockpit hardware systems or even Saitek panels can output these in a home cockpit.

 

Did they fix that? anyone knows?