Jump to content

Vauban

Members
  • Content Count

    154
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vauban

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That's great, thank you. I love the hat analogy. I'll take a look at creating a button assignment for switching between layers.
  2. I have V 3.60. Many thanks for taking the time to explain all that - I completely misunderstood the concept. I have now edited all the button assignments to put them "in" (😉) control layer 1. Now, when I select Layer 1 (between '+' and '-') I see all my assigments, tagged in yellow as being in (belonging to) Layer 1. And my problem is solved - my button/key assignments go only to the sim. I just have to remember to switch to Layer 1 after I fire up the sim, and switch to a different layer when I want to type. To my surprise, when I select Layer 2 (or 3, or Default) and expect to see a blank list of assigments, I see the same list of my Layer 1 assignments. So I still haven't quite grasped the concept, but job done. Thanks again.
  3. Thanks for the tip - it's what I was looking for. But I've run into a problem at the first step. I have all my buttons assigned in layer 0, meaning the actions go to the keyboard driver, regardless of which layer is active. I exported them to a template, intending to import them back into layer 1 and then delete them all from layer 0. This was my workaround for copying from layer 0 to layer 1. However, after exporting the actions to a template, I find all my button assignments are now not only in the layer 0, but also duplicated in layers 1, 2 and 3. This happened without me importing the template back into a layer. By trhe way, I also found that layer 0 is now called 'Default', which I can understand, but I don't know what happened to change it. Is this the right approach, and can I safely remove all my assignments now from layers 0, 2 and 3? When that's clear, I'll turn my attention to switching between layers 1 and 0 (page 15). Thanks for your help so far.
  4. Hello, I imagine this problem has been reported but I'm finding the topic difficult to locate. I'd appreciate a pointer. I have many keyboard keys assigned to cockpit actions. When I shift away from the sim to type some text in a different app, those key strokes are still recognised by the sim, even when the sim doesn't have focus. It plays havoc with the cockpit setup . Surely I don't have to precede every script with (FOCUS:flightsimulator). 😦 On page 100 of the manual, there's a note: On Windows systems, only the app that has the focus will receive keyboard events. Cheers and thanks
  5. Hello, I was offered V 3.61 as a download from DropBox which I don't use. Is there another way I can get to download it? Thanks
  6. Now I have it. I didn't have the button assignment set up correctly - I wasn't using the Assigned combo field, so it was just luck that I got it working at all. I misread section 3.7.7 in the manual and thought the Combo key was only to be used with axes, as it is in the example. I wanted to set up a keyboard key 'a' to switch a light on, and Ctrl+a to switch it off. (I particularly didn't want a toggle.) Here's how I now do it, as described in a round about way in the example in the manual: In the Change Button Assignment window for the script that runs when key 'a' is pressed: - Enter 'a' in the Assigned button/key field. - Enter Ctrl in the Assigned Combo field. - Check the box 'suppress Key Down Event'. For the Ctrl+a assignment, do exactly the same, but do NOT check 'suppress Key Down Event'. That works for me - I hope it's the way AAO intended it to be done. 😥
  7. Now it's working. I cleaned up the scripts and removed some 'wait's that were purely for aesthetics. Somehow it all came right. I hope I haven't wasted your time - and many thanks for your quick response.
  8. In the Add Button Assignment window, I have script X as the Key Down Event. I use the Assigned button/key field to assign key 'a' to that event. I then repeat the process for script Y, assigning key combination Ctrl+a, specifying Ctrl and 'a' using separate key presses. I'm new to AAO and haven't yet looked into 'Combo keys'.
  9. Hello, I'm having a problem assigning a key combination, say Ctrl+a, to a script. For example, I assign a single keyboard key, let's say the 'a' key, to run a script I'll call X. Then I assign a key combination, Ctrl+b, to run a script Y. Both of those assignments work fine, so I seem to be assigning them correctly. Now I edit the second assignment so that instead of using Ctrl+b to run script Y, I use Ctrl+a instead. Here's the problem: for some reason Ctrl+a doesn't run script Y as you'd expect - it runs script X. It's as if the Ctrl key is ignored and only key 'a' (which runs script X) is processed. If I then unassign key 'a' from script X, the combination Ctrl+a runs script Y as it should. (I've blacklisted all devices to avoid any unwanted input signals.) The general case is that if the second key ('a' in the example) is assigned to its own script (X), then you can't use that key in a key combination to run a different script (Y). The problem is not limited to the Ctrl key for the combination - any other key causes the same effect. Geoff
  10. Mine does the same, and the pedals,too. It's not a controller problem - the WIndows USB Game Controller window (Properties) show the controller is giving the correct output. Have you heard of a fix since you posted?
  11. LOL, now I'm on track. Thank you Kyle! Geoff Kent
  12. Thanks for your swift response Kyle, I really appreciate it. As you suggested, I uninstalled NGX completely as per your instructions and ran the latest installation file. Now I have the Operations Centre which is what I was looking for when I had the installation problem. But I still have a strange version number when I click: Add-ons > PMDG > About PMDG... It tells me "Version (App): 10,0,61355,62" Am I looking in the right place to see what version of NGX I'm running? I'm expecting to see 1.10.6461 Thanks Geoff Kent
  13. Duplicate - sorry, can't see how to delete this. Cheers Geoff Kent
  14. Duplicate, sorry - can't see how to delete this. Cheers Geoff Kent
×
×
  • Create New...