Jump to content

awralls

Members
  • Posts

    158
  • Joined

  • Last visited

  • Donations

    0.00 USD 

Reputation

5 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. Just to close this out (and to apologise for my tetchy response previously), I should add that I have resolved the issue by the simple expedient of uninstalling 3.0.3.5 and reinstalling 2.9.0.0. I can't say that there is any noticeable reduction in functionality but a huge improvement in stability. Basically, I no longer have any problems. Probably not what you want to read, but dem's da facts, guv'nor. Andy
  2. USB headset. I know that the attenuation routine is supposed to address the issue. For me, it doesn't always - to repeat - it's inconsistent. But I guess if nobody else has reported a probelm, mine must be entirely imaginary. FWIW, I have discovered that if I terminate the mic level check after only a couple of runs of the Peter Piper thing, it seems more reliable. Since I have the mic check to run automatically on startup of MCE, I'll see how it goes if I disable it. Since I am suffering alone, I presume you're not bothered if I fix it, so I'll leave this here. Still love the software, though. Andy
  3. Gerald, Apologies for the late response, but as I mentioned, this is an intermittent issue and I wanted to be thorough in determining if it is fixed. Sadly, it isn't. I played around with mixer settings, but none of that made any difference. To be clear, the issue is that the sound volume varies during a session. It'll start fine, fade, come back, rinse and repeat. Any way to revert to an earlier version? I never experienced the issue before upgrading. Andy
  4. I upgraded to the latest version a few days ago and since then I've suffered an intermittent issue with the FO voice fading. It will restore itself after a while and them repeat the problem. The software is going through it's startup routine of ensuring the comms is set to 'no change'. I also have the mic check implemented durimg startup. Been using MCE since 2013 and never had the issue before. Oh, this is with FSX. Any clues? Andy
  5. Tried to install 0.7.9 - informed me I needed .net 7.0.4 but the link I was sent to only has 7.0.2 which I already have. Then tried to install 0.7.8 - informed I needed to update my SD app to v6.0 - I already have 6.1.0.18521. Grateful for any hints as to how to proceed. Cheers, Andy
  6. As far as I'm aware it's always been an issue that Voxscript won't accept a command like 'flaps twenty'. 'Flags up' and 'flaps down' seems to be OK. Is there any chance that this can be fixed? Andy
  7. Same here...it's a complete pain in the proverbial. I've reinstalled every voicpack I have, but it still does it. Andy
  8. Brilliant. Don't I need to copy fsinsider.dll somewhere within \FS9?? Andy
  9. Hi, I have both FSX and FS9 co-existing happily on the same machine, and MCE is installed for FSX. Is there anyway to be able to install it to and use it with FS9 on the same box? I suspect not, but I'd be interested in a definitive answer. I don't believe it would breach the license terms since there would only be one instance in use at a time. Cheers, Andy
  10. Were you under the GS? Usual procedure for any ILS interception is to capture the LOC first while you're well under the GS and only select APP once the LOC is captured. Check the manual for AFDS operation and the following is helpful. http://www.smartcockpit.com/download.php?path=docs/&file=B737-Automatic_Flight_Systems_Summary.pdf What are the Flight Mode Annunciators on the ADI reading when you're intercepting the ILS? Without more info or a screenshot, it's hard to know what you're doing wrong. Andy
  11. Both NAV radios set to the ILS freq, both course read outs set to the inbound ILS heading per the FMS approach page, APP set on the AFDS and both A and B autopilots selected. Andy
  12. The nav radios default to AUTO mode for INS updating - select the AUTO button to manual and you should be fine. Andy
  13. ...which is the command to, er, disconnect the GPU. Except that when I try it, following a successful "cockpit to ground dialogue", the only word that's recognised is "Disc" as in the power lever setting. Accordingly, the command to the ground crew is never delivered and I have to remove it manually. I'm probably missing something fundamental, somwhat am I doing wrong? This is with 1.5 BTW. Andy
  14. I was referring to the PRO version replacing the panel.cfg rather than FS2Crew. The PRO install overwrites whatever panel.cfg you had before the install. One effect being that there are now no longer any FS2Crew entries. The PRO version is released...I'm flying it now. My question remains; does 1.3 work for the PRO version in FSX:SE without modification? Andy
×
×
  • Create New...