Hi Michael,

 

That display setup is similar to what I have (without the hardware MCP though. Nice!)

Instead of a monitor in the back, I have 46" TV.

 

You are running in windowed mode with two VCs right?

The bottom VC zoomed in on the PFD and ND.

 

The problem with that is that it cuts my frame rate from 20-30fps in half :-(

You dont have that problem?

I now use the PFD + ND + Engine center display pop up panels and moved them to my bottom monitor (just click on the PFD in example and drag it to another display.)

 

This way frame rate stays good. The thing is though, that upon resizing (enlarging) the PFD etc, the instruments become less sharp.

 

Do you have that too (less sharp) when zoomed in on the PFD and ND?

 

 

 

 

No i dont have two VC´s but it looks like it right ? . Its actually just a screenshot and used as a windows desktoptheme :-) creativ right ? :-)

I think ifly (cockpit builders edition) may be the only 737 with the aircraft model and undockable (networkable) gauge panels with no lost of frame rate. I'm also wishing for a NGX cockpit edition, or a way to undock the NGX panels without loss of FPS, but no such luck.

I have PFD, ND, and the FMC undocked within. - 1 fps drop so it can be done. I use Dx10 btw. So smooth

No i dont have two VC´s but it looks like it right ? . Its actually just a screenshot and used as a windows desktoptheme :-) creativ right ? :-)

With undocked PFD/ND on top offcause

Maybe you could use WideView for the outside Visual and just use the NGX with no VC/No Outiside Visual/ undocked gauges on a seperate PC. Once you rid the VC and outside visuals the FPS hit should be minimal.

Maybe you could use WideView for the outside Visual and just use the NGX with no VC/No Outiside Visual/ undocked gauges on a seperate PC. Once you rid the VC and outside visuals the FPS hit should be minimal.

 

That's what I was saying earlier.  But 777simmer is saying WidevieW only works on outside visuals. So I guess this wouldn't work.

 

I don't think a cockpit builder version would open a can of worms.  They already have a better NG systems and flight model than any other out there, and from the way it sounds like they built the NGX platform, something like this might just be a plugin to what they already have.  Of course, what "sounds" easy almost never is, so I guess we'll have to wait and see.

That's what I was saying earlier.  But 777simmer is saying WidevieW only works on outside visuals. So I guess this wouldn't work.

 

I don't think a cockpit builder version would open a can of worms.  They already have a better NG systems and flight model than any other out there, and from the way it sounds like they built the NGX platform, something like this might just be a plugin to what they already have.  Of course, what "sounds" easy almost never is, so I guess we'll have to wait and see.

 

Wideview does only work on outside visuals, but that's all you would want on one monitor I assume.

 

You know the funny thing about flight models is every company swears their flight model is as real as it gets and their resident  pilots swear by it. I just always find that funny. I don't see them doing a cockpit builder's version, but there is a large majority of users who would just like net-workable gauges, nothing as in depth as the competitors, just away to free up screen real estate without a fps hit. 

This turned out to be a kind of a "thinking out loud" post :-) Hope thats ok!

 

I have tried flying with one monitor as outside view (not VC, just outside view) together with one monitor for inside cockpit view (VC zoomed in on instruments or panels but no (or hardly any) outside view visible.

Maybe it is just me, but with that setup I find it difficult to judge weather I am aligned with the runway (crosswind de-crabbing for instance or base to final visual turn) or not.

Because you dont see any part of the aircraft in that outside view.

I just cant tell if the airplanes fuselage is parallel to the runway heading or 10 degrees off or more. (I know I have the instruments to look at, but I want to be able to fly a descending turn to the rwy (downwind to base to final) by just looking outside)

 

Same with judging distance and height to the runway (visual approach).

I just cant get it right (always too high or too low) unless I see some of the cockpit framework. (again, I know papi and instruments help a lot, but that is not the idea)

It all just seems like a big view of outside world with no reference of where my aircraft is going.

Maybe I should have practiced it more?!

 

So I concluded that I need the VC on my outside world monitor.

Zoomed in untill I see basicaly only the Left Fwd Windscreen and some of the top of the cockpit "dashboard".

This view could be done with wideview as far as I know on a secondary PC. (I think in wideview you can choose weather or not you see the VC, but instruments will not work.)

But...this needs to be a strong modern PC to give good performance.

And I have only one strong (ivy) PC!

 

Ok.

Then on the Primary PC I would want to be able to use two monitors.

One monitor that shows the popup PFD + ND + engine instruments (these should always be visible and never be hidden by other panels) and the other one would be used to display the VC (maybe with trackIR) so I can get to the overhead panel, pedestall, FMC etc.

(Note: The secondary display, even though it displays the VC, cannot be used for looking and switching things on the overhead panel, MCP or FMC, etc. it is a view only!)

Now how strong does this Primary PC have to be?

Would my old core 2 duo be sufficient to power:

Joysticks/controls

two displays (one with popup 2D panels and one with the VC)

soundsystem

sending network data via wideview to the secondary PC

I guess I could try.

(dont know if I need to buy another copy of the PMDG 737 NGX?)

 

The last time I tried to network my core 2 duo (@3.8Ghz) I tried it for an outside view (as the secondary PC) with OPUS FSX. Absolutely no chance, stutters stutters and nothing but stutters.

 

But maybe as a primary PC for inside views only, mmmmm....maybe that would work.