bennyboy75

^^^^this. You'll be disappointed with the voices in RC and the stuff it can't do compared to PFE. Pro ATC I can't speak for, but the voices need work.

Thanks Xiter. Obviously until it's up and running in my study here we won't know. As you say stable as an overclock and stable in FSX is a different thing. Either way, I'm confident it will do the job for what I need.

And/or check 'global texture settings' - make sure it's 'massive'. The default config is medium, iirc.

I changed the default flight to a default Cessna 152, at the gate at my local airport. If I select this first and then load up the dash after the Cessna loads I get no problems. I suspect it's something to do with the default flight being airborne.

I tried dialling up the dhm and other camera effects to the max in Ezdok on the Q400. When landing the dhm went crazy - as if I'd ripped the gear off with a really heavy landing! The view bounced up and down all over the place and then stopped as I rolled out down the runway. If I dial in a more 'normal' level of dhm as used in the NGX there is nothing felt at all. So there's something happening with Ezdok but to all intents and purposes it doesn't work for me. Perhaps NyxxUK could share his Ezdok settings with us?

I recall this was a big problem in the Level D 767 back in the day. You'd open the doors at the gate and then when ready to button up the nifty fingerwork involved in closing one of them would abandon you. In the end some enterprising soul created a panel for it that popped up with one of the 'F' keys. Keyboard commands for stuff like doors on an add-on as good as this one is a real let down. PMDG had full FMC control of the aircraft actions on the FS9 MD11 years back, let's hope the Majestic team look at this.

+2 life's too short for minimising FSX. Please also put a menu for the doors in the FMC too. That would complete this lovely bird!

Very nice! You've spent money on the right stuff. I just went nuts and ticked every box! It'll be interesting to see how much more bang per buck I get (if any!) from my rig over yours. Not long to wait now...

I will, it's in build now and should be here soon. I'd rather not think of the price too much, but let's just say I could have bought a fairly decent used car - or a fair chunk of a private pilots licence for the cost of this little puppy!

Here's the full spec: COOLERMASTER HAF 922 MID TOWER GAMING CASE Overclocked Intel® Six Core i7-3970X (4.8GHz) ASUS® RAMPAGE IV EXTREME: INTEL X79, SOCKET 2011, R.O.G 16GB KINGSTON HYPERX BEAST DUAL-DDR3 2400MHz X.M.P (2 x 8GB KIT) 6GB NVIDIA GEFORCE GTX TITAN - 2 DVI, HDMI, DP - 3D Vision Ready 1st Hard Disk 120GB KINGSTON HYPERX 3K SSD, SATA 6 Gb/s (upto 555MB/sR | 510MB/sW) 2nd Hard Disk 240GB KINGSTON HYPERX 3K SSD, SATA 6 Gb/s (upto 555MB/sR | 510MB/sW) 3rd Hard Disk 2TB 3.5" SATA-III 6GB/s HDD 7200RPM 64MB CACHE 1st DVD/BLU-RAY Drive 24x DUAL LAYER DVD WRITER ±R/±RW/RAM CORSAIR 850W PRO SERIES™ HX850-80 PLUS® GOLD MODULAR Corsair H100i Hydro Series High Performance Thermal Paste ARCTIC MX-4 EXTREME THERMAL CONDUCTIVITY COMPOUND IIYAMA XB2776QS 27" LED IPS Widescreen - HDMI, DP, DVI, VGA It's made by PCspecialist.co.uk, a pal of mine is very happy with the build they did for him.

Don't get too hung up about the finer details of the charts. In Europe, and particularly at a busy field like this in Germany you'd be vectored by ATC once inbound on the STAR around to the localizer. In the real world with considerations of fuel, noise and the environment it's highly unlikely you'd go all round the houses from the IAF at MIQ back round to the runway. More likely would be you'd get a heading issued by ATC from ABGAS to line you up with the localizer. They have a lot of traffic coming in and want you in the flow as efficiently as possible. To simulate this as true to real life as possible you could get to the STAR and then self position onto the localizer.

Gents, I'm assured by the co supplying it that it will be o/c'd to 4.8 out of the box. It will go higher but they tell me that's my call. This chip has been clocked and stable up to 5.1 if you look on the overclockers site. Also taking into account the results of Word Not Allowed's test with the Titan on his blog then this rig should pack a punch. It might seem like overkill but I've been on FS9 since forever and a day and my last purchase was a Dell desktop that cost similar amounts to this one back then but obviously now has less processing power than my iPhone. I can run FS9 like butter and I knew unless I spent some serious cash I wouldn't be able to enjoy upgrading to FSX but the time has come. This is a (very pricey) treat but if I get 9 years out of it like my last one I'll be very happy!

Probably Qantas didn't like it. There was a 777 pilot from Singapore Airlines who also had a channel that vanished like this also. Airlines can be funny about stuff like this. I'm currently recording some video tutorials for the Q400 with a real world pilot and he's specifically requested we don't reveal his name or airline.

I have Ezdok and I can't detect any movement at all.

Just ordered a 3970X o/c to 4.8 (hoping to push it 5.1) with a Titan + 2 SSDs. I have high hopes! Will let you know how I get on.

That's the one. Also remember what we said up thread about ai usage. Rather than fart about with closing runways at this stage, I'd turn off your ai so that you can be ready for either runway at the arrival end, and specify a runway for departure in the dep/arr page so you can brief and depart on the right SID. Also I turn off the taxi feature as it gives you spurious directions and annoys me. I just pull out a chart and follow the directions given by ground when I'm ready to taxi. In the real world there's no pointer thing showing you the way to go. You read the chart and look at the taxiway markings. One other thing, use the co pilot mode to handle all coms once you're ready for taxi. After that you can concentrate on flying, as in the real world. Oh yes, one last thing, it should auto detect you at the holding point and tell you to contact tower if you have co pilot mode in handle all coms but often the detect point is well beyond the hold short line. If this happens tune to tower manually and there's a keyboard command to ask for takeoff clearance. I can't remember it now but some kind soul will post it I'm sure.

Can you not try to reassign the FSX default axis and then try again with FSUPIC? I must admit, I've not heard of this method before for assigning steering. I would prefer steering via the rudder pedals to be honest as that leaves my hands free to do stuff in the FD during taxi but steering via the ailerons works well enough, albeit it's VERY sensitive.

Hi all Just noticed from going back into the NGX for a few flights that there's absolutely no turbulence or head movement injected by either Ezdok or Accufeel when flying the Q400, something I'd not really noticed as I was so busy trying to fly the thing! Is this to do with the external FDE etc?

Indeed it is. The more I see of X Plane the more I'm inclined to give it a go.

Very true. They've worked hard on building their brand and we'll probably see more 'global' products after this. Airports, mesh, ai traffic. As long as it's all up to scratch (and they have the strength of their brand behind them to support this) then it'll all sell. I have mixed feelings though in some ways. If there effectively ends up being a single developer who does a good job on virtually everything you'd need to get the sim looking good then it'll probably force the others (Flight 1's GEX and UT namely) to quit developing altogether and then they have a monopoly. That's not great either.

The real Airbus definitely has it - they call it the 'hockey stick' as it gives you a little arrow along the flight path where your current rate of descent/climb will put you. It's not modelled in the AXE, although there was talk that it might appear in the (just released) SP. I'm not sure whether the Q400 has one. I suspect not as the Majestic guys haven't really left anything else out. And yes you're right, it's the thing I miss most from the NGX!

If you've got a decent bit of wind then you shouldn't have any problems. I'm an afcad fiddler as it means there won't be any annoying surprises when I'm on the arrival. The best thing about PFE is the way you hear the ai traffic doing real life stuff. If you're in a queue for takeoff you'll hear ai cleared one by one and as you depart you'll hear the ones behind you join the departure frequency. On arrival similarly you can build 'the picture' as they call it of where everyone else is around you as they get handed off to the tower and onto ground. It's really quite nifty. It's just a shame that the interface via proflight (a very dated looking piece of FS98-era software) is a bit clunky.

Pedals are easy. Buy yourself the registered version of FSUIPC. Clear out all the axis in FSX (it will assign all kinds of daft axis like ailerons and throttle - for pedals!) and then open up FSUIPC. Go to axis assignment and hit rescan. Then push your rudder pedal forward (the pedal, not the toe brakes!) and assign that axis as a direct FSUIPC function - 'rudder', from the drop down list. Then hit rescan and press gently the top left of the pedal, assign that the same way but as 'left toe brake. Do the same for the right pedal but assign as 'right toe brake'. Then go to the calibration tab and click forward through the options until you get to left and right brakes. Make sure 'rev' is ticked on both, as otherwise they will be on when the pedals are released instead of the other way round. Hit ok and you should be good to go!

As above, I got this wrong. You can specify the end of the SID and the beginning of the STAR on the flight plan page. Depending on how far out the final waypoint on the STAR is from your arrival runway you may fly the whole thing or just some of it. No two airports are the same in respect of STARS. Many STARS in the UK for example terminate at a VOR or NBD on the field itself which isn't realistic to real life ops. In most of Europe, you'll be pulled off the STAR and radar vectored to the localizer. PFE handles this pretty well. If you want to fly the whole STAR to the FAF, which is pretty standard somewhere like EHAM then you can do that too, by requesting 'pilot's discretion to final', where they will let you fly the whole thing and you contact tower once established. The reason I close runways is that PFE gives you runways based on ai usage and winds. On calm days when FSX can't quite make up its mind you may find yourself landing into oncoming traffic. I find if you close everything but the runway you want then that doesn't happen as everyone is landing and taking off in the right direction. It's not entirely realistic but it's more realistic than being vectored to the moon and back because PFE keeps changing the arrival runway because FSX can't make up it's mind. You can close runways to PFE inside the program, which means PFE won't give you them, but it does nothing to stop ai using them. Only closing the runway altogether via the afcad does, in my experience. Remember to open them again after the flight or when the wind changes all your ai will go screwy taking off with a tailwind.

Ah yes I forgot that's what you can do! So you can have the best of both worlds. That's my only bugbear with PFE - all this stuff changes with every flight so there's a lot of inputting the right info beforehand to make it all play nice once you're in the air. If you do it right though it's well worth it.