Cee-Jaay

Hi Dean; unfortunately no recommendations; just to say I have similar issues - Win 7 / P3d v3 / Saitek Cyborg 3d Force (thought it was force feedback incompatibility, which seems un-disable-able from the device settings in CP). I'm now wondering which joystick 'will' actually work with this thing. If I find one that does all reply again. Kinds Rgds, Chris. P.S. A bit unhelpful that when postng a reply on these forums; the original posts doesn't show.

Well you live and learn! just did a similar test & it seems that FSX does recognise the parking codes in the FSX config files for user-driven aircraft. I have a modified parking file for LFMN & from the threshold of 22R, Lufthansa and Air France repaints of the Airbus Extended are directed to their respective terminals ...once the parking codes are added to the aircraft.

Perhaps... 1. Ask Aerosoft & PMDG, why they both apparently 'forgot' to include the parking codes in their latest products. 2. do a test - disable ALL AI; close FSX; set an airfield with two unique airlines codes in the parking spots; and land/request parking from the SAME taxiway with TWO variants of the SAME aircraft type; using each of the codes set in the spots. And you'll find that ATC directs you to the same parking both times, rather than a spot associated with the parking code. Kind Rgds, Chris.

Hi Dan, The parking code data is only used by AI planes - in both FS2004 & FSX. So the line in the config is entirely redundant for your own aircraft parking. Kind Rgds, Chris.

I was thinking that the window screens/visors would have been included. There may be some constraint regarding total animations, but I think it's a stretch to say that there'd be a noticeable impact on frames. It was a good feature I remember on the PSS 777 when travelling westbound over the pacific and chasing the sunset for most of the trip. Cheers, Chris.

>>Some of us that have been around MSFS for a long time remember that the 767 was first done by an American Airline real world pilot. Aah those were the days... Eric & Wade brought us a groundbreaking new plane to play with in FS2002 originally & v6.4 was the famous first complete release, I think. I remember following the updates on the website every few weeks as they built and previewed each gauge as they went along. Chris.

I'd recommend getting addon airports for those places you've been to IRL or know very well. If you're not careful you'll fall into the trap of only going to places you've got highly detailed scenery for; or feel that you have to get the airport scenery before going to some place - when the route itself may provide ample interest. Chris.

Cheers Guys, top menu bar now rendering and working on homepage on iOS/Safari.

Hi Bugor, it certainly doesn't do that (items entered on Tracker for details of both issues highlighted). Chris.

Hi there, is anyone looking at sitewide issues for iOS devices? It appears the top-level navigation does not display, which makes the whole site largely inpenetrable (e.g. How do I get to the file library from the homepage on iOS? And could I just check what the "full version" button should be doing? Cheers, Chris.

Hi EgbertMy monitor is widescreenIt's rather odd (and surely wasteful) that the normal panel includes FO gauges, but doesn't show them!Hi Trevor,Awesome, Many thanks, It's on my shopping list for this weekend. I too find some panels a tad fuzzy these days - must be middle age.Regarding the Service Pack - Do folks know if that's just for the full new "Wilco 737 Evo" or does it apply to the "2d panel update for FS9 737pic" as well?

Interested in this as I still fly the old 737pic albeit merged with the fiftynorth external model (in win7 64bit).I do have FSX/NGX, but found I was getting the dreaded 'uiautomationcore.dll' issues too frequently - even with the vista version in the root folder. And since I have a big ai collection, running fs9 ai in fsx pulls the frames on my i7 down to a third of what I get in fs9 (the slowest I've ever seen in my fs9 is 45fps e.g. QW757at a very busy EHAM).Generally I find VCs great for those 'ooh, look at the view' moments in the cruise, but too many payware a/c centre the VC view straight-down and so aligning back to straight ahead is either too much 'left a bit, right a bit' or scanning up from a view of the seat cushion - not what you want at 400ft in a crosswind, hurtling towards the concrete.If only they would move the window centre-post over to the right a bit more, since it looks like it would get in the way when lining-up from a right base to finals; and we don't 'really' need the FO PFD & ND displays - surely that's gonna gobble up a bit more horsepower than needed.There are still some classic fs9 destinations like Seattle and Portland, that haven't been 'done' for fsx yet.Chris.

Hi Wanabflyer,Essentially, when I change views or close fsx dialogs (like the flight planner) I can get a black screen or missing textures (i.e. the sidewalls of the VC are gone, or the pfd/nd displays show other texture parts (presumably meant to be hidden by the gauges).And when I close FSX after flying the NGX I get the unrecoverable error/restarting FSX sequence.To be fair to PMDG, I'm wondering if this is down to the dreaded FSX/Win7 uiautomationcore.dll issue. I hadn't encountered it with other aircraft, however after installing the Aerosoft AirbusX I got a lockup on changing views.The other things I've noticed (specific to the NGX) is the ND brightness knob doesn't seem to work (although the PFD & Centre displays do), and all brightness knobs zip between min and max if I do multiple clicks.Chris.I'm running Windows 7 64bit (Home Premium) & FSX SP2 on an i7 2600k @3.4Ghz with 8Gb of DDR3 RAM.GPU is NVIDIA Geforce GTX 560 with v285.62 (6.14.12.8562) drivers.Windows partition on a 1Tb Caviar Black HD & FSX partition on Corsair GT 60GB SSD.

TBH I've given up on the NGX, which is a shame but the texture issues are constant, i.e. they will occur eventually on a flight.From my experience it's unreliable.btw I don't have EnB (whatever that is)

Hi there,Having built a new rig a few months back I was experimenting with various settings and noticed just how much AI affected framerates, what was interesting to find that it didn't seem linear.For example placing the microlight at Jackson Int'l (where there was no AI parked) I was getting framerates around 100.When I moved to Jackson Hole (Wyoming) where there was a single A320 parked-up, the frame rate was around 60.And at a busy and complex airport (like FSDT Los Angeles) it settles down at around 25.I can only assume that as soon as any AI is placed, FSX invokes a large amount of additional processing to manage the AI Flightplan, jetty states, etc.Chris.