nolatron

Pretty much. For a 29" monitor the 21:9 is just over 1" wider but about 4" shorter. http://www.displaywars.com/29-inch-21x9-vs-29-inch-16x10 I personally prefer a wider than taller desktop. I also use this pc/monitor for more than just FSX so the wider desktop has other benefits for me. But again... that's me.

Yeah, I was testing my displays when I took the photo. Here's some more pics for comparison. MFD displays are readable to me and I have no problem with the view. Works perfectly fine to me, but like you said, some may not like it. How the PMDG 777 Starts up by default. 777 zoomed out one click to .60 My EZDok View for the now. How the PMDG 737NGX starts by default 737NGX zoomed out one click to .60 My 737NGX EZDok view Once I get new mini MIP built this how'll mostly fly though.

I love my new 21:9 29" monitor. Replaced my triple monitor setup with it. Here's a look at the 737NGX on mine.

Same here. Mine is out for delivery right now so I'll get to play with it tonight. It's going to replace my Saitek X45 that's dying a slow death.

Are you able to undock the display screens and move them to another monitor?

Mine looks ok using nvidia surround with these settings and halo.bmp if you wanna try it. RUNWAY_LIGHTS_APPROACH_SCALAR=0.8 RUNWAY_LIGHTS_STROBE_SCALAR=1.0 RUNWAY_LIGHTS_SURFACE_SCALAR=1.3 RUNWAY_LIGHTS_VASI_SCALAR=0.8 http://www.mediafire.com/download/p5sjpnmal18qhrl/halo.bmp AI aircraft departing KSFO

Latest cycle is 1310 which came out Sept 19. http://www.navigraph.com/FmsDataDownload.aspx 777 came with AIRAC cycle 1309. There's a section in the Intro PDF on how you can change the cycle end date to get rid of that message if you don't want to update.

what happens when you jump to an external view? You just see nothing?

If you have a 3 monitor setup just divide the window_size in the panel.cfg file by 3 and use that number. It works for me.

That's cause it's Best Buy. Mainstream gaming has gone to online delivery via Origin, Steam, etc... Any gamer knows that. Heck, even consoles are moving to online delivery for the future. And no, I don't ever see mobile devices like an iphone (and sometimes the DS and PSP/VITA) being the future of gaming. The hardware will just never compare to a PC or Console. It's good for a 'mobile' game to pass the time with or for kids but that's about it.

I don't think it is. PC gaming hardware already surpassed the next gen consoles (XB one, PS4). There's more developers for PC games than there are for all consoles combined (source). I wouldn't call it obsolete just yet. I think the PC will always win as the best gaming platform because the better hardware will produce the better visuals, and I think I developers know that. Consoles are mainly popular cause they're cheaper and in the living room. With all the restrictions, dropped backwards compatibility, subscription fees, etc... that next gen consoles are bringing I wouldn't be surprised to see a surge of people going back to the PC Platform.

Looks like a telephoto shot. The fence is probably nowhere near the aircraft. Good photo though.

I've got the 737NGX FMC screen and 3 MIP displays undocked and moved to 2 secondary monitors and I run in fullscreen mode all the time. Maybe since these are real monitors though? <shrug>

http://commons.wikimedia.org/wiki/File:Sarah_Palin_Flight_Simulator.jpg

When MSE V2 came out I picked up 4 states. I thought the look of photoreal gret and a direction I wanted to head. Though I didn't like the flatness while taking off/landing, up high it looked much better than what FSX or even GEX had in places. Last night I flew my first flight (737NGX) in FTXG with Dense autogen and i was impressed. I took off from KTLH in Florida where I have MSE V2 photoscenery to KATL in Georgia where FTXG was on. The FTXG textures looked great and the autogen had no real impact on my frames either. While flying over the border you can really see how washed out and dull the photoreal scenery is while the FTXG scenery was lush and vibrant looking. It's nice seeing a filled city too when coming in on approach. So far I'm liking what I see with FTXG and will probably not use photoreal anymore either. Oh, and the FTXG lightning at night is amazing as well.

Using DX9 right now. I've tried switching to DX10 twice following the DX10 guide and all the patches/tools but I always ended up with horrible performance. My frame rate would be in the single digits where as DX9 I'm locked in at 30 pretty much. I always wonder if it's my nvidia surround setup or something, but so far I haven't had much luck with it. Now that I'm flying the 737NGX in 2D cockpit and not in VC I may give it another shot to see if that will help the frame rate.

There's a "custom landclass" in UTX you might want to disable too. At night time you can see a big difference in this landclass's lightning (it's white) versus the FTX Global lightning. The lightning difference looked a little too patchy too me so I turned off the landclass.

Hi All, This is for anyone using A2A's 3D lights with the 737NGX. Do the landing lights look the same in both the VC and when in the 2D cockpit? (pics would be appreciate) Here's why I ask. I typically fly in 2D mode on my desktop cockpit. It wasn't until recently I noticed the 737NGX has it's own Landing Light texture that looks great in the VC. However, in 2D cockpit mode the default FSX landing lights are shown (or rather the REX landing light texture). These lights just really mute the runway texture in a sea of gray. So if the A2A lights work well in 2D mode I might switch to those.

RUNWAY_LIGHTS_SURFACE_SCALAR //scales edge, center, end, touchdown, runways RUNWAY_LIGHTS_VASI_SCALAR // scales VASI lights RUNWAY_LIGHTS_APPROACH_SCALAR // scales approach light bars RUNWAY_LIGHTS_STROBE_SCALAR //scales RAILs and ODALs

I used the NGX control Codes with FSUIPC for the cutoff levers on my JetMax TQ. Engine 1 = 70320 Engine 2 = 70321 Parameter 0 is off, 1 is on. Just be sure to add [sDK] EnableDataBroadcast=1 to the 737NGX_Options.ini file

Since you're stretching the view across 3 monitors now, you need to divide the first number in the panel's "window_size" by 3. For example instead of "window_size=1.000, 1.000", you'd used "window_size=0.333, 1.000"

Thanks! I don't really follow you either, but... The external view on the top 3 monitors is the default 2D cockpit view, just with no 2D panels. It spans all three monitors (primary monitor, single monitor resolution of 5760x1080). I didn't undock and move that view. The bottom monitor contains the 3 pop-up panels that appear when you click on each MIP display. Those are undocked and moved. The FMC monitor contains the FMC panel with the just the screen showing. That is undocked and moved. You will always have the external forward view, it's a default FSX view. It really just depends on how far PMDG takes the "no 2D panels" stance. As long as they still allow the MIP displays to "Pop Out" then you're fine. No sense in arguing about though until ithe 777 is released and we know for sure.

Hmmm... When you adda new 'VAR X' line and change the "0" to 1,2, etc... are you also changing the v1 to match the var # it's inside?

You should be able to get 32 buttons on 9 virtual joysticks. The number after "changebit" is the button # and the offset is the Joystick number.

Whoops, pasted the the link wrong. Shoud've been http://www.blueskies737.com/737ngx-control-codes/ With Opencockpits IOCards and SIOC you can have it trigger a virtual joystick button in FSUIPC with code like this: Var 1 Link IOCARD_SW device 1 Input 55 Type I { &FO_JoyStick64 = CHANGEBIT 0 v1 // toggle button 0 of joystick 64 - STBY Mode } Var 2 name FO_JoyStick64 Link FSUIPC_OUT Offset $3340 Length 4