> 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 sledgehamm
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 worka
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 k
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
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 navigat
On 4 Mar 2013, at 14:54, AJ MacLeod wrote:
Aha, and instantly we get a usability discussion:
> Just sticking in my 2p worth... I would say I use z/Z almost every flight.
> It can be useful for "cheating", as Thorsten said, but more usually as a
> means of adjusting performance. Often airpo
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 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 stic
On 3 Mar 2013, at 07:07, Renk Thorsten wrote:
> Personally, I think reserving key binding for things which you can really do
> in a real cockpit is not a bad concept. And I would really like to understand
> why some people think it's necessary to change the visibility so often that a
> menu o
Hi AJ
hello Franz,
first of all: I have never seen such a good organized code and system
like fgfs! Also the community is really cooperatively. Thanks to all!
On Wed, Oct 25, 2006 at 11:08:57AM +0100, AJ MacLeod wrote:
[...]
>
>C
>Catapult Launch Command.
>
> property-assign
>
* Holger Wirtz -- Wednesday 25 October 2006 11:27:
> I want to set a property when pressing the key
> and I want to reset the property when releasing the key.
C
PTT key
nasal
print("C key pressed")
nasal
Hi all,
I am searching for a way to implement a PTT (push to talk) key in fgfs.
I found the file "keyboard.xml" where key bindings and their functions
are defined.
As I understand this file, you can set/reset properties inside the
property-tree. The definitons in this file explain what to be done
12 matches
Mail list logo
