For better or worse, that's me.hesynergy wrote:Hey Mark!
Are you the sterling pilot and writer, Mark Hargrove on Pilotedge? First of all I want to praise you on your contribution to the flight simming world with your recent article about the 3.35 views.
What I found not particularly useful was the "automatic layout" you can get from the ViewGroups (i.e., by specifying your monitor "grid" and allowing P3D itself to calculate the views and view frustrum by looking at your monitor resolutions). I'm definitely not saying that ViewGroups aren't useful! The reason I went into such detail is to show folks how to manually define all the elements that the "auto-layout" will try to do for you.hesynergy wrote: You wrote, "From the little bit of hands-on experience I've had, I don't really see much value in the various automatic layout features, so this tutorial is a fairly deep-dive into creating a view group with fine-grained control of each view. ", so while I congratulate you on a rather lengthy article, would you please help me understand why you spent 22 pages writing about a topic whose worth you perceive to be dubious?
The insurmountable problem with automatic layout is that it assumes your monitors are all co-planar (i.e., lined up in a straight line). If you do an auto-layout and DO have your monitors physically aligned that way, things like runway/taxiway markings and other straight lines will indeed look straight when they cross monitor boundaries. Most of us with multiple monitors, though, tend to angle the "outboard" monitors inwards on each side of the center monitor. If you do that with automatic layout you will NOT see straight lines when things cross monitor boundaries. To get them to align you need to use a heading offset and that can only be done with a manual ViewFrustum definition.