MarioB

After a long Xmas interlude...I am back to MCE and the Q400. The black selector knobs on the overhead panel (e.g. windshield wiper, bleed air mode selector) don't seem to work, while the ones from the center console (e.g. ARCDU mode, MFD modes) do. Are they different for MCE? edit: The engine start ignition knobs are the only ones working

Comments noted. I though something was amiss with the flat buttons. I am thinking modifying the flows to match the detailed tutorial by Brendan Ratchford. This will be a good opportunity to practice with VoxScript. For now, I may modify the flows so me, the PIC, will have to manipulate the flat buttons. Quesrions: Where is the Q400 flows file located? I may use as a template. Does the Aerosoft Airbus flat buttons also give issues to MCE? BTW this is a fun piece of software. Lots to learn and play with. Thanks!

A few things are not working on the Q400 powerup with APU flow: Start APU APU Gen On Disconnecting th GPU (mentioned in another post) Check FDR (no test performed) Chceck Fire Detection - no test performed Check Smoke Detection - no test performed I did a cold & dark reset (using MCE command) and re-strted the PU APU flow, same result. As a general question: what is the course of actions to take when commands are not performed? Thanks!

I'll second that. I used a SteelSeries Siberia V2 with the Pro Clip. More stable than the hat clip. As for the wires, I wrap the headset/Pro Clip wires together. Used it for 3+ years, no issues. Works fine.

The RealAir folder location is exactly the issue. No problem - no rush. I will keep monitoring this forum. Thanks ScotFlieger.

How can I create a new aircraft module with the RealAir Lancair V2? The aircraft search string gives me aircraft that are in the SimObjects folder. In the case of RealAir, their default installation folder now resides in Drive "C". The "Create" button is only available when I select an aircraft from the "Aircraft Search String" list. Not sure how this works. Thanks!

The problem was solved by plugging my USB headset (2.0) into a 2.0 USB port instead of 3.0. Windows 10 has issues with this.

This is interesting. With W 8.1 and P3D v2.5 the voice commands worked. I installed W10 this summer, updated to P3Dv3.1. Just got back to the Q400 (pro) installed FS2CREW and no voice commands. Microphone working, English, audio test OK, usb headset, speech recognition training done. No mute. Latest FS2CREW installed What am I missing?

Yes, it works great.

Now fixed with the 1.018 beta 2 patch with P3D3.1 compatibility. Download in the user area.

Roger that. Thank you for looking into this.

Yes, that is correct, it's for a faster trim on the A2A aircraft. The FSUIPC works beautifully. I was wondering if there's a way to program this for LINDA.

Is there a way to program this in LINDA? This is how it looks in FSUIPC Many thanks!

Although I would have bought v3 anyway, this video was very informative. Thank you.

Hello, At about 05:40 in the video Josh has a little trick for the FMS and draw a line in the nav display along runway 27. He uses NAV/MNVR/PVOR and enter option 3 "CI27" in WPT, then 270 in the OTBD radial and presses enter/accept. When I enter the outbound radial 270, after filling the WPT entry, all my entries disappear and no ACCEPT option is possible. Question: Is that an FMS glitch, a new FMS version? Thanks!

Thanks for the info Harry; this is true, I also noticed the creation of these folders in my documents. I got confirmation from the developer that MT6 did not create the 1.4 registry keys. So it's still a mystery as to how they were created. Going to KLXV, Lake Co. CO, the highest airport in the continental USA.

In the end, deleting the 1.4 P3D registry keys did the trick, 6.52 installed correctly

After a failed VOXATC update, I was told that the cause was that my 1.4 registry key also pointed to the P3DV2 setup path. No biggie, I can work with the earlier VOXATC version. But I have never had anything less than P3D 2.0, so obviously, I never uninstalled a 1.4 version. I am no expert in registry matters. I believe the 1.4 keys are: HKEY_CURRENT_USER\Software\Wow6432Node\LockheedMartin\P3D HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\P3D A FSUIPC installation log also confirms a V 1.4. was found Questions: Was these 1.4 keys added by some add-on? Should I bother removing them if they are not required? If yes, how should they be removed? Thank you kindly.

Thank for this Harry. After Tegwyn examined my add-ons, he found nothing suspicious. He still believes the failed 6.52 installation is due to that P3D V1.4 registry entry. He told me to use 6.50 instead for now since there are no major changes. Something has changed in the 6.52 installer (apparently "improved" for all P3D, FSX and FSX-SE sims) that prevents a correct install for P3D 2.5. So, for all of you that have ORBX products and P3D2.5 as the only sim installed, the VOXATC 6.50 version may be the best option for now.

Tegwyn wrote back saying that the issue was due to a registry entry for P3D 1.4 that is set to the same folder as P3D V2.5. He asked me to change that. My knowledge of registry entries is poor. I have never had anything less than 2.0. Maybe it was created by an add-on (I never used Estonia). The FSUIPC install log also indicates that a path for 1.4 was found. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v2 are the key names I found. If I am to change that, what should I do, delete the LM folder that contains the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D ? Why is the 1.4 entry in my registry and why did VOXATC 6.50 work correctly?

What is the sum of all you walk aways?

Thanks Gregg. There's days where I feel: Let's help the developper - we are a community after all. He does his best, so should I Other days: I spent $80 on this, but worse I spend hours figuring out what is wrong. Tired of fiddling around... I am no Beta tester unless I choose to! BTW - With limited free time, it would be nice to fly instead of playing with installations...

I meant that it would save Tegwyn numerous emails if he would take part in this forum and take note of the issues we have. For example, there was no mention on his webpage or any readme accompanying the download, that 6.51 would not work with P3D when it is the only sim installed. So when he annouced 6.51, I installed it. Got problems and then found out in his subsequent email that 6.51 was not made to work for P3D installed alone. Come On Man - provide instructions in the first place, save yourself some emails and better still save your customer headaches and wasted time! For my 6.52 installation, I told him In my first email that the installer would not show the indexer popup nor the sim select popup. He replied with a generic email to run the VOXATC tool and send him the error. There's no FATAL ERROR in the VOXATC window. The installer just doesn't complete properly. I installed 6.52 yesterday again and found out it works, but the runway updater, simselector.exe and indexer don't run and give me the "This program has stopped working" generic windows message. He sent me another tool veryfying my sim install - I have only P3DV2 installed - no tools required. This is where we stand. What bugs me in all this is the everlasting back and forth emails when problems arise. He's somewhere in the UK and I am in Western Canada. An exchange of info can take many days. I know it's a one man show, but he could either 1. provide detail installation instructions and/or 2. participate in these forums and get some customer feedback.

Installed it yesterday, over the 6.50 version... a no-no according to Tegwyn. FATAL ERROR in the sim's VOXATC window Uninstalled with Revo, deleted the leftover Internal Workings folders (the main install folder and App Data folder). Deleted tha extra Vox Pop. Reinstalled. Now, I cannot get passed the P3D/Weather/Themes folder in the indexer... But I was impatient and closed the window quickly. Also I noticed that the Sim selector window opens and closes immediately and tha the indexer doesn't pop-up automatically during the install. Will fiddle with the install when able. 6.50 worked correctly with MT6 in P3D 2.5 Just too bad that Tegwyn doesn't hang around here. Sent him an email yesterday - got a partial answer this morning saying that you always have to unistall the earlier version. He did not adress my other issues. It's a great software when it works, but I just wish there would be implication from his part and it's starting to imply too much time fiddling with it on my part.

select Views - Instrument Panel - VoxATC.