Jump to content

I B Spectre

NEW MEMBER
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About I B Spectre

  1. I think it may have something to do with my HOTAS. I'm running a gameport interfaced CH Products Pro Throttle and it is calibrated via Window's Control Panel/Game Controller. Calibration is always a bit imprecise and is possible my minimum throttle setting was not minimal enough and LOMAC would not shutdown the engines, thinking I was above idle RPM. After getting a good minimal throttle calibration, LOMAC may have been satisfied with the values representing minimum (idle) throttle position and let me shutdown. This is just a theory, but if LOMAC is designed to prevent inadvertant engine shutdown, disallowing shutdown at any setting other than idle, that may have been the culprit. I've been able to successfully shutdown numerous times now.
  2. Tonight, while flying with some friends online, I was actually able to shutdown engines for the first time! I was pleasantly surprised in that I had tried the exact same procedure many times before both online and off without success. In any event, it worked at least once so I'll hope for a repeat in the future. Thanks again, ruggbutt.
  3. I'm running LO v1.02 and the key reference with the README says engine start (simultaneous) is Pg Up, individual engine start is Alt + Pg Up for left, Shift + Pg Up for right. All those work like a champ. My problem comes with trying to shutdown engines. The reference shows simultaneous shutdown is Pg Dn while individual shutdown for left is Alt + Pg Dn and right is Shift + Pg Dn. If I abort the start, either simultaneous or individual engine, the Pg Dn and Alt/Shift + Pg Dn works. However, if the engine(s) ever reach idle RPM, I cannot shut them down with any key command. I've tried reinstalling, but it always behaves the same way. Any ideas?
  4. Using LOPE

    Agreed, much more user-friendly way of doing the same thing. One odd thing I have noticed, though, for some reason most of the time I check ModMan I see Shepski's mod is showing a yellow status as though it is not fully installed. No biggy, a simple matter of selecting "Install" and the status indicator goes green again and works like a champ!
  5. Using LOPE

    Thanks, ruggbutt, I appreciate the input. I think I'll uninstall LOPE and reinstall Shepski's. It seemed to do what I needed in an easy-to-use manner.
  6. Using LOPE

    One additional question: Prior to downloading LOPE, I had used another download titled "Realistic Weapons Mod for A-10, Su-33, MiG-29A/C and Su-25" that seemed to offer many of the loadout options I see in LOPE. It was ModMan compatible and seemed to expand the in-game payload options, which made it easy to use during mission building. What are your thoughts on the two mod?
  7. Using LOPE

    Thanks. Tried just unzipping/dropping it into the LOMAC folder, but it kept telling me it couldn't find the LOMAC installation folder. Finally, I realized it was prompting me to point to the file in the directory tree and, bingo, it appeared. I appreciate the help.
  8. I downloaded the LO Pylon Editor V1.01 and used MODMAN to install it. MODMAN indications suggest it was successfully installed, but I don't see anything any different. I see a LOPE icon in my LOMAC folder, but when I click on it, it says it cannot locate the LOMAC installation folder. What am I doing wrong and where would I expect to see the LOPE interface? Thanks in advance and Happy New Year!
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..