Screenshots WALL : Tack up your pictures!

[AADX]

AADX LJX 10 into Wasilla Alaksa (PAWS) -9000 fpm drop in.

---

Thanks for the comment Bob. I think we've exchanged similar comments before. That the panels are open format and people can change and rearrange however they prefer. Akin to an owner going out on the weekend and tinkering with their plane and moving this switch here, that switch there, this radio above or below that radio for preference. I flew the CTJ for a ~700 nm trip and was entirely content with the location of things. I tend to feel that where I have controls at seem to be the most natural and logical place to me, but like many things that is also subject to my opinion and perception. I think I also may have my FOV high enough that things are on screen in front of me without moving the view, whereas at lower FOV things may be out of view and require moving it.

Depending on the computer display, I tend to be up in the 80-90° FOV setting, that being on the 16:9 type of wide screen. then plus & minus zoom the view in for more drawn into view, focus in, sort of view. i'll put another couple of the CTJ panel in the next post to show the zoomed in to just the pod, versus the widened out normal setting I use for bigger better wider view.

All that said, most typical radio stack layout is (top to bottom) audio panel up top, navcomgps(s), secondary radios (adf, dme), ancillary equipment (transponder, autopilot, radar, etc). status display items like ap mode displays are central heights, off to the sides. and panel mount switches, rotaries, knobs, are near what they relate to. in rare case would a switch be far away from what it relates to, such as putting the switch directly near where the hand rests natrually for quick/natural operation. But in any event, the panels are able to be changed and rearranged by the owner in their hangar on the proverbial saturday morning or wednesday evening tinker sessions. See if you think differently if you try going up to higher FOV setting for normal view, and zoomed in for the more ideal panel/instrument view. Also get familiar with the keyboard keys to look at "full screen without hud" (and with hud if you like). which as I have settings entered for, gives you the horizon centered, cockpit in view, "eyes up" view. (I myself use that w/hud, akin to 'google glasses' like HUD view)

[AADX]

Normal "W" view, _FOVx 90.000000

Shift-W, full screen w/HUD. 'eyes up' sort of view.

Normal "W" view, plus+ zoom.

Normal "W" view, _FOVx 90.000000
- minus, zoomed back out, or 'w' reset.

Normal "w" view @90FOV, @IMC

in v10. Shift-9 to enter 3D view.
then F key to roll the view down some. View movement Q, E, F, D.

to the "in the office" view, including the secondary screen to validate the PFD horizon,
and include all controls, including physical fuel gauge, OAT & Timer.

CIRRUS CTJ SJ-50 10X

[AO-2208871]

Jason: Not to belabor the point, but my comments were not about a change to CTJ, its stack being perfect for my way of operating and manipulating both the radio controls and the autopilot. My comments pertain to the Learfan and Learjet where the radio switches are mounted in the center console below the GPS display, and require a separate switch of view to change back and forth from com1 to com2 since the switching panel is there, and the GPS's with their frequency settings are another screen view above that location. If the problem is about room on the panel, swapping the positions of the transponder and the radio com/nav switches will facilitate the operation I described without requiring this extra X-plane view manipulation at times when things are really busy in the cockpit under ATC control procedures and responses.
In X-Plane flying, I find that the presets of all communication frequencies required can be made by using the four frequency settings available on the two GPS units, in combination with the switching between com1 and com2 provided by the switch panel. Often X-Plane pingpongs between two controller frequencies when you are in an approach, and I setup these two frequencies on com2. Com1 is used for airport ground and tower frequencies presets both for origination and destination airports.
At takeoff and especially in landing approaches, the switching between these frequencies, then can be done purely by hitting the switches on the GPS's and the radio switch panel to get and change between the correct preset frequencies required.
To switch the view to make this possible requires two extra operations if the units are separated as described and makes a pause a essential requirement if things get busy or when you get a waveoff or have a missed approach.
I hesitate to fiddle with your good work myself... and I can live with the way things are set up... so this is the last flack you will get on this subject from me.
Best Regards
Bob

[Ralf]

The old LJ25 is looking better and better.

[AADX]

I do think maybe that if you're talking about x-plane frequency changing, that may be being done at inappropriate times.. in the simulator. IRL, there's no frequency changes once in the airport area airspace, on approach, etc. only frequency change is after landing, switching from tower to ground. the handoff from approach control to tower is usually after established-on-final, prior to FAF. and for that you're exactly right, you have the digital flip-flop for those.

Are you talking about the Audio panel? for which COM channel is active? 1or2.

When time to switch COM frequencies, approach control to tower, digi-flip-flop COM1. In my personal experience, the audio panel is among the least used item, used mostly/only for navaid audio ID, and secondary COM channel like ATIS/AWOS on COM2. Live communications only on COM1, and flip flop those. The risk of "lost com" is made much worse by adding in which audio channel is lined up on the audio-panel.

(different people may have a different workflow and prefer com channel switching.
in that case, they're entirely welcome to swap transponder and audio panel)

Maybe we just have difference of opinion about what belongs where and why.
That's okay.

My workflow is live communications on COM1, retune or flip-flop. ATIS/AWOS on COM2.
Never mixing up where live communication is at. and on COM1. there is present/future, or present/past.
in either case there are valid go-back options for an onset of "lost communication" situation.

There should never be any frequency switching in the critical phase of flight. inside FAF, less than 1000', in the pattern, etc. any frequency changes are outside of critical-phase-of-flight, turned off for a departure, clear on course contact departure control. etc. and those are flip-flop COM1 or re-tune based on written down Freq# on paper in order of freq# assigned/received. Just my workflow, I'd personally never put a live communication channel on COM2. I have similar OCD about navaids, and which is on which NAV1 or NAV2. It's all intended to relieve mental workload by logical processes and lineups. e.g. never fly an instrument approach, primary navigation guidance, on secondary navigation faculties.
primary-primary, secondary-secondary.

But you know, everyone learns the way they do, knows things how they do, has their workflow that works for them. that's totally and entirely expected and ok.

LFX/LJX, this view at also 90° FOV, everything needed here. only thing not in view is audio_panel.
if audio_identifying the morse code of a navaid, is a head-down, listen, and finger on the dot-dot-dash code on the approach_plate.

AADX LJX 10

---

the axiom in aviation is;
aviate, navigate, communicate.

in that order. in that logic. transponder tuned/on/mode_c, supersedes communicate.

in-flight, eyes down, full view. including map and next_level engine instruments.

audio_panel, there near the right hand on the levers. fingertip distance for done-by-feel buttons, IRL, in theory. for much the same "in-the-office" time during navigating for changing to listen to NAV frequency to identify the navaid dot-dot-dash morse code, and then deliberately back to COM. Similarly down in the in-the-office position for while outside of the approach area, switching to COM2 to get ATIS/AWOS, write it down, and then deliberately back to COM1 for live ATC communication, toggled between approach-tower. tower-ground. tower-departure. in the eyes-up, flip flop on G430#1.

[AO-2208871]

Landing on RW 4R at Detroit Metro

Well I finally realized that assigning two audio commands .. for com1 and com2 transmit to my gamepad control keypad provides the instant access to the switching I am looking for for ALL aircraft wihich negates any problem that I have. Here also is a view of the updated lJ25C landing at Detroit Metro in its now Livery.. very slick.
Best Regards Bob

[AADX]

Perfect Bob! that's about exactly how it would be IRL. toggled by touch, like you would the volume knob in the car, two fingers on two buttons for your favorite two radio station presets 1 & 2. finger 1, 1, finger 2, 2. change by touch without looking. doing that with analog control is ideal. probably could set that, if it's not already, to keyboard keys also. When I flew and did that, even with an audio panel top of the deck, was that same two finger, two button, and eyes stayed on other things. my workflow being different, but the finger touch change was just that.

Good looking shot there. as the season comes around I look forward to getting down to your Marathon and Key West scenery and putting it to some storyline use. your shot reminds me of that. Most of all, i'm glad to see you having a good time.

---

AADX LJX 10, PAWS Wasilla AK

[AADX]

BX206B3 10 having a look around Aerosoft Glasgow

[AADX]

T6X 10 - Observations during recent testing. from All_Off condition. A quick circuit flight

[Ralf]

Sarasota to Key West. Clear skies but nice crosswind on final.