Jump to content

DavidV935

Members
  • Posts

    23
  • Joined

  • Last visited

Profile Information

  • Location
    KSTL

DavidV935's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I read this AFTER I posted my note above. Thanks again!
  2. Problem finally solved. For the benefit of other readers of this thread, this is what I did. It may not be the easiest method, but it worked. 1. I uninstalled v1.6.3, and then deleted the two X-Aviation folders in XP11 (the standalone folder and the subfolder in Aircraft) 2. Restarted XP11. Oddly enough, it asked me to reenter my X-Aviation email address and password to "activate." 3. Clicked on Settings and saw my previous LES folder still listed as before. 4. At the bottom, I hit RESET BINDINGS TO DEFAULT for XP11. 5. Restarted XP11 and saw LES gone from the Keyboard Settings 6. Reinstalled Saab v1.6.3 and saw the keyboard menu as shown in Mr. Gregory's screenshot. SUCCESS!! Thanks again for posting your screenshot so that I knew what to look for.
  3. Do you know which specific version deprecated those commands? I have v1.6.1 and v1.6.2, but not v1.6. Should I delete my current v1.6.3 and reinstall v1.6.1 and then the two updates to v1.6.3?
  4. Do you which specific release deprecated those commands? Would the solution be to delete v1.6.3 and install that specific version, then progressively the updates leading to v1.6.3?
  5. By comparing screenshots, it's obvious I do not have an "sf34a" subfolder under LES. Since the Saab v1.6.3 is installed and I can select and fly it, can you suggest what I should do to remedy this discrepancy? Thanks for posting your screenshot - I just don't know how to get there from where I'm at.
  6. I installed the latest LES Saab 340A v1.6.3 and set the keyboard shortcuts for AP engage/disengage; Door; and Tiller engage/disengage as shown in the attached screenshot. After I launched the plane, none of these 3 keyboard shortcuts worked when I attempted to use them at the appropriate time. Is there a step I am missing? I had no issues with these shortcuts with previous versions. Appreciate any advice. Thanks.
  7. I downloaded and installed this A380-800 yesterday, but when I launched XP11, it didn't show up in the XP-11 listing of aircraft for selection. After exploring the file structure, I noticed all the file dates were 2012 and 2013, there were no aircraft icons, no 3-d cockpit folder, no plugins folder. In my opinion, this file should be removed as incompatible with XP11.
  8. DavidV935

    Licenc

    I had the same issue when I tried installing v1.6.3 yesterday. I also got a GIZMO64 error message along with the X-Aviation licensing error. See attached screenshot. After spending a frustrating hour trying to figure out a solution, I ended up using the uninstall.exe, then deleted X-Aviation folders in the XP directory (the Saab is the only aircraft in that folder), then reinstalled from scratch. That gave me the normal original prompts for my X-Aviation user email address and password and that worked. I did not have to do any of that when going from v1.5 to v1.5.1 to v1.6 etc.
  9. @Ben Russell I don't have any special characters in my x-aviation password - just letters and numbers, but I have to re-enter it every time I choose a different airplane.
  10. Cameron... I don't fly every XP every day or multiple times in one day, so can't answer the first part of your question. My last time was last Friday before I posted this thread, and just now it did not ask for my userid and password. But, it happens often enough when I launch XP, select an airplane, then click on Start Flight. I'll try to pay more attention to the details of timing and see if I can make some kind of correlation. I know that kind of answer doesn't help you troubleshoot, sorry.
  11. I bought the LES Saab340 in the spring, and when I launch XP11, it asks for my X-aviation userid and password for the license, but it does not save it for future use. The window pops up no matter which airplane I fly and I can't get rid of it without looking up the email with my X-Aviation userid and password. If I fly the Zibo 737-800, the X-Aviation window pops up. I should not have to enter it so many times. If the developer is monitoring this, this is very annoying.
  12. Fair enough, Goran. I can certainly understand your perspective and agree with it. I've seen posts in other forums about troubles using xEnviro and none were about the Saab.
  13. To the LES team members on this thread. Your answer(s) worked for me, so I won't get xEnviro until you post the issue has been resolved. My recommendation: Post a pinned item labeled "Issues between xEnviro and LES Saab 340A" or similar wording, explain what you've explained here, and state you will post again whenever the issue is resolved. Then, get rid of this thread so the community doesn't have to wade through all this. When resolved, simply post the date/time of the resolution into that pinned thread and how people should proceed if they own xEnviro. Just a thought... BTW, while this Saab 340A has been a lot harder to learn than the one I flew in FSX, I love it, and kinda like that it hasn't been so easy. Perverse, I know! ;-)
  14. To find the Nosewheel Steering Toggle, under Keyboard Setting, on the left pane select ALL. Then on the right pane, expand "Flight Controls," and under Flight Controls, expand "Basics." See attached jpgs. Then under Basics, scroll down until you see "Nosewheel steer toggle." It will not have an assigned key, but my jpg shows that I assigned the letter "n" on my keyboard to toggle the tiller on/off. Under LES/CMD/Gear there is also a toggle for "tiller_hyd_on_off."
  15. Just did a few different scenarios with nosewheel steering engaged (tiller pressed down) and with it locked. Image #28 is the plan entered into BetterPushBack both times. The result was the same in both scenarios. During the second scenario with the nosewheel steering locked, after seeing the plane going the same direction as the first scenario, I went to the BPB dropdown and selected "Stop Pushback," at which point the plane was turned 90 degrees left and then came to a stop before hitting the gates from the opposite terminal.
×
×
  • Create New...