On 4 Mar 2013, at 07:43, Vic Marriott vic...@btinternet.com wrote:
Hi James,
Personally, I use 'ctrl' a lot when making my own shortcuts (outside FG). I'm
sure I can't be the only Mac user to do this. An example: If you were to
allocate 'ctrl+s' to a common FG function, using 'ctrl+s'
The discussion reminded me of a blog post I once read:
http://www.flightsim.com/vbfs/content.php?11603-Is-The-Default-Keyboard-Layout-Still-Relevant
Might be worth reading, but also might be worth forgetting afterwards.
Sometimes it's good to read someone else’s experience though.
Erik
--
On Sun, 03 Mar 2013 11:24:29 +
James Turner wrote:
My *personal* feeling is that unless it's something the 50% of users use
*each flight*, it shouldn't be a keybinding. So flaps, trim, CDI/HSI heading,
fine, but things to change view distance or FoV seem unnecessary to me.
Just
On Sun, 03 Mar 2013 11:24:29 +
James Turner wrote:
What I'd like to see is the entire 'Ctrl' (Command on Mac) space reserved for
GUI functions, like a normal application - Ctrl-Q for quit, Ctrl-M for map
dialog, Ctrl-A for autopilot dialog, Ctrl-R for replay dialog (or radios
dialog :)
On Monday 04 March 2013 15:38:45 James Turner wrote:
You're the third person to say the same thing. But again, you don't actually
want to change the FoV at all. What you're doing (and everyone else) is
using this feature to look around 3D cockpits, right? In other word, our
cockpit navigation
On Mon, 04 Mar 2013 15:38:45 +
James Turner wrote:
Aha, and instantly we get a usability discussion:
Right, you need the keys because you're working around a simulator bug
(frame-rate drops badly) using manual interaction. The correct fix isn't to
make the workaround-UI easier, it's
Just my 2 cents here.
The primary reason I use the FoV/x binding is to see, read, and be able
to use everything (or as much as I can) in my cockpit. Personally, I
would rather scroll up/down, but that seems to have limits, as I can't
zoom in as far as I want to by scrolling, but can using the
AJ wrote:
On Mon, 04 Mar 2013 15:38:45 +
James Turner wrote:
Aha, and instantly we get a usability discussion:
Right, you need the keys because you're working around a simulator bug
(frame-rate drops badly) using manual interaction. The correct fix isn't
to
make the workaround-UI
Often airports are in or
near very scenery-intensive areas and reducing visibility can help a lot
in making the sim run usably for take-off, whereas once you're up and
away it's nice to be able to open the view back up again for
cross-country flying.
This is applying a sledgehammer
9 matches
Mail list logo
