awralls

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

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

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

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

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

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

Same here...it's a complete pain in the proverbial. I've reinstalled every voicpack I have, but it still does it. Andy

Cheers, Gerald. Andy

Brilliant. Don't I need to copy fsinsider.dll somewhere within \FS9?? Andy

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

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

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

The nav radios default to AUTO mode for INS updating - select the AUTO button to manual and you should be fine. Andy

...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

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

…and what about FSX or FSX:SE with the PRO version of the Q400? Hardly surprising, but the install replaces the old panel.cfg, taking out the FS2Crew entries. I could just reinstall the panel.cfg entries but I'm a bit reluctant since there is so much that has changed from the PILOT version. Andy

I'd find it had to imagine they could work together because VOXATC injects its own AI so that it can control them directly and I would guess that that would cause all sorts of conflicts as the two applications both try to control them. Andy

I have it working across a network more or less as advertised. I found that if you set the network paths in the dialogue using the browse function, it needs a backslash added to the path for it work OK, but with that exception, and one other that I can't fix, it's fine. The other issue is that even though I've used the paths dialogue to copy the wpnavrte.txt file, it still cannot allocate aircraft to jet routes. I've reported it to Roland. I'm using UT2 so I don't know if that's an issue. UT2 has been enabled in the options and the spawn distance adjusted to 70 miles, but still no joy on jet route allocation. All other functions seem fine. A thoroughly brilliant piece of work and deserving of some sort of contribution from the users. Andy

Dave, thanks for your work. Just an observation, not a criticism - in reality, the sound through headsets used by flight deck crews to talk to ground engineers is far less distorted than this given that the other end is plugged directly into the flight deck audio. It's broadcast audio and far clearer than ground to air comms. I was doing this in the 80s talking to RAF transport crews, and I would imagine the technology is far better now. Cheers, Andy

It does make you wonder why anybody actually asks for any advice. Andy

The process is that it looks at the traffic at the departure an destination airfields and then populates your route with a selection of those types and liveries. If either or both of those airfields are small with few schedules, you'll get a limited choice, but the quantity is determined by the option selection for the number of AI. Andy

OK, I'll address the OP. My advice is to give serious consideration to any other ATC add-on other than ProATC. ProATC is still under-developed and more likely to induce frustration than satisfaction. You have spotted one problem; there are many others. I suggest a read through of the ProATC forum to gauge the level of satisfaction or otherwise of those who have purchased it so far. Andy

The FO handling comms is also provided by RCv4.3, PFE and VoxATC. It's certainly not unique to ProATC-X and I would contend that is hardly sufficient to make up for all of the other glaring deficiencies in the latter. Andy

Sportsfan, you need to use the free UT2 Power Pack from F1. Then, install the WoAI package for your chosen airline into FSX. My personal preference is then to remove the newly installed WoAi traffic bgl form FSX\scenery\world\scenery. I them use TTools to decompile this into it.'s constituent .txt files and import this as a schedule into the Power Pack. Follow the power pack instructions to create the ut2 schedule for the new airline and import it into UT2. Once that's all done, to into UT2 and you can then allocate individual WoAI paints to the aircraft you've set up for the airline in the Power Pack. I realise that this skims over the process, but if you follow the Power Pack instructions, it'll all make sense. Andy

How do you know what weight he was, therefore any talk of vREF is pointless. Andy