Andydigital

Just get EZDok and stop making life so difficult for yourself. I used to adjust my eye points manually for years until EZDok was released, then the nightmare was over. TrackIR and EZDok work perfectly together and it makes moving eye points and creating whole new viewpoints/cameras child's play, it literally takes less than a minute to setup a view once you are proficient.

You don't specify a cruise alt, and TOC is never calculated anyway, this aircraft doesn't have a sophisticated FMC like many other commercial aircraft.

The UK has several TA's, it depends on the airport, 3000, 4000, 5000, 6000 are all common.

If you are using the unregistered version of FSUIPC, when it asks you for a registration key just press cancel, just like it tells you to in the Install instructions.

I read that you have to shutdown the engine then restart it, no idea how true that is though.

Also the Sound tab in the Majestic Control Paenl is greyed out in the Pilot edition, the sound tab will only be available in the Pro and Training editions of the Q400.

P3D isn't that much better performance wise, if anything for me it performs worse than my FSX install, P3D stutters more for me than FSX doesn't. It all depends on how much junk you have installed in your FSX install compared to your P3D install. I actually have much more installed in FSX and its still a smoother experience over all. P3D has been sat dormant for almost as long as my Xplane 10 install has and I haven't touched that since well before Christmas. I will admit that the lighting and default textures in P3D are far better than default FSX, but who uses just default FSX.

If you are going to bring reality into it again, where is the middle mouse button in the Dash 8? You have to make compromises with controls in FSX because a human cant grab hold of a knob or press a button very accurately in the FS VC with a mouse, especially when there are momentum effects moving the cockpit around all the time. My mouse wheel click facility doesn't work very well either (its a free wheeling, wheel) and is next to impossible to press without also turning the wheel, so I end up adjusting the baro (or whatever my mouse ends up pointing at) at the same time I am trying to press the Baro button. If you absolutely must ignore a great many of your customers in this instance then a compromise would be to turn the STD press into toggle function and pair it to a default FS Control that can be assigned to a button, that would help people like myself who have difficulty pressing this knob. Again as has been said before, we are one pilot doing the workload of 2. Hooking up B would be far simpler for everyone involved though.

Sounds like you possibly didn't remove the assignments in the FSX controls menu first before assigning in FSUIPC. Or. Be aware that when you unplug a joystick and then plug it into a different port the next time you use it, FS sees the re-plugged device as a new joystick and assigns a default set of commands to all the buttons and axes. So check that any previously removed assignments in FSX haven't come back again. I label all my USB plugs and sockets and always plug everything back into the same socket to avoid this situation.

When starting out on a new aircraft I usually just fill'er up to the brim until I have done a few flights, then I can use my educated-guess-o-meter once I get an idea of the burn rate for different situations.

You press X-Fill on the FMC you want to import the data to, i.e. you are pulling the data from the opposite FMC.

That's because you pull the data from the opposite FMS, you do not push it. All you did was pull an empty flight plan from the other FMC.

If you bought a system with Windows 8 Pro installed, check with Microsoft, you probably have the right to a free downgrade licence to Windows 7 Pro.

Correct, or more correctly you can only activate one descent leg at a time. VNAV is quite rudimentary in a Dash 8.

Sadly no they didn't do that, but as stated previously you can assign it with a mouse macro in FSUIPC.

I still don't think going from an i7 2600k to a Haswell is a worthwhile upgrade, I'll be skipping another generation.

The tiller/spoiler axis doesn't work above 40 knots, so you should be OK using a yoke or joystick for the tiller axis, my HOTAS WH works great, plus you can switch the tiller off with a switch just above the tiller on the left side panel. I have that assigned to the AT switch on my VRi MCP panel. I tried using the spoiler axis but preferred using my joystick instead, it was much more intuitive. I think MJC could improve this slightly by making the tiller response a little less sensitive around the neutral point i.e. a flatter slope in the middle.

No problems here with TrackIR 5.1, EZDok and the Q400, just make sure you remember to enable the TIR button on each EZDok view you want to use TrackIR with.

LINDA must be running at all times to work with anything not related the a VRi MCP, if you close it then the buttons on any other devices with assignments made in LINDA will no longer work. The LINDA manual does tell you that it must remain running to work correctly.

It looked empty to me, you couldn't see anyone in the cabin anyway. That's what 9000+SHP looks like, lol.

I've not tried it myself yet but I am pretty sure you can use IAS mode too, that will adjust pitch to keep a set speed, if you pull the PL's back to almost idle you should get a good rate of descent with a speed set at 220 to 240 or so. Guess what I am going to try now in FSX, lol.

See the official website, it has a FAQ section at the page below. http://majesticsoftware.com/mjc8q400/support.html See the question "Simulation stops and then resumes, once in 1-2 minutes". There is also further details in the manual in the section that speaks about the Aircraft Manager and Syncing the FDE to FSX.

Do it after pushback but before you taxi. Make sure the control lock is off otherwise you won't be able to move any flight surfaces but the rudder. Also select at least flaps 5 otherwise you won't see full rudder deflection, its limited to 50% travel with flaps up, if I remember correctly.

There seems to be a bug in the Q400 at the moment that seriously limits the range of VOR's regardless of whether they are terminal or high altitude VOR's. I'm not sure if Majestic had confirmed the issue or not yet (nor have I noticed it myself yet) but there have been a few mentions of it on the MJC forum. http://majesticsoftware.com/forums/discussion/comment/1044#Comment_1044

P3D or FSX need to be running for the Majestic Calibration application to work. As for using and setting up FSUIPC, this guide should help to some degree. http://fsuipc.simflight.com/beta/SIMSAMURAI+FSUIPC+TUTORIAL.pdf