Helge Rasmussen

That explains it I have been been away from FSX for several years and just got the itch again, so was trying to download and install my products, but couldn't get it to work until I noticed that it now is called OpusFSI, is an entirely new product and that I have to pay for it. Too bad the upgrade path does not exist anymore or I would have paid for an upgrade, I doubt I will pay full price again. Helge

Thanks for the answers, I will go upgrade to Reboot asap. The description of Airbus X voice control states: "These products are intended for use with the NEW Aerosoft Airbus Series. " The new Aerosoft Airbus Series is Airbus A318/A319/A320/A321. Does Airbus X work with these?

Hi, I haven't been simming for at least 2 years, but got the itch again. Since last, there's a new version of FSX: FSX-SE that apparently is more stable, so I bought that. I own a bazillion fs2crew products, here are the newer ones: Majestic Dash 8 Q400 Voice Control Airsoft Airbus X Voice Control RAAS professional PMDG 737 NGX Special Bundle Pack Emergency NGX! Are these compatible with FSX-SE if I download the latest version from FS2Crew.com? I see there's a 737 NGX reboot package. Is there a discount for people like me that own the NGX special bundle and emergency pack? Fun to be back, but it will take me quite a while to get everything installed again Helge

You cannot do it until you get your first vector I think. It should show up on the menu if you press 0, but only when it is available.

Very strange that changes to video affects voice... I have no idea what the problem could be, so here are just a few questions to contemplate: In the first post you said that the problem occured just by using VoxPOP. Does VoxATC and its configuration tools still crash if you haven't installed VoxPOP? (i.e. only use microsoft voices) Is there something interesting in the error log? Strange that the developer hasn't responded. I have contacted him 4 or 5 times since I bought VoxATC a couple of years ago, and always got an answer. Helge

What if the FSX plan includes the final altitude instead of the first? Then you just kind of pause at a lower altitudes before reaching the final altitude. I know it isn't perfect, but it is better than the nagging

Say "<callsign> request full ils runway <rwy> approach"

I just do not accept vectors when there are mountains around the airport. What I do is to say something like <callsign> request full ILS runway 22 approach You can find this in the "0" menu, it won't be available until you get your first vector I think. (you can just say it, you do not need to choose from the menu) When I do this, ATC acknowledes that I want to execute a procecure approach and asks me to report at some fixpoint. Helge

Edit: Problem was fixed while I posted this, but I will let it be here anyway. It may help others Glad you got it fixed Hi, Did you try with another plane such as the default Cessna 172? also, post the log here. We might get an idea from seing it. Here is how I initiate a flight using VoxATC, maybe try this?: - Start FSX is started and the plane loaded and placed at the gate and airport I want (I only use VoxATC for IFR). - Open the Flight Planner in the Flights menu and load a plan (I use EFB to create the plan). Answer no to the question about moving the plane. It should already be at the gate. - Choose "Save As..." in the flights menu and save the flight. You wont need the saved flight for anything, I just save it as "a". The important thing is that you save the flight. - Enable VoxATC and after a test of the voices it asks me to tune to ATIS. I have a problem with the majestic Dash Q400 for some reason VOXAtc wont start when I just load it. Thw workaround I found is to load the cessna 172 and start voxatc as described above. Then switch plane to the majestic. I dont know why I have to do this, but it works for me. I had to install the VoxATC panel myself for the Majestic and I probably made an error somewhere. Helge

Hi Dave, Try to contact the developer via the VoxATC.com website

I have ProATC, but does not use it awaiting a new version. Hopefully ProATC will get better, but it is not there yet. Currently I use VoxATC which reacts on speech. I like it a lot.

Try to contact the developer via his home page (http://voxatc.com) and ask.

Hi Paul VoxATC uses the same data as the LevelD 767 FMS data, so if Nav Data Pro supports that plane, then I think it should be ok. Edit: Ah, I see Mike beat me to it

Very nice! The flight number is visible in the popup. It would be fun to also see departure and arrival airport as well,

Where are the maps from? Is it people online on AVSIM?

Ok, I will try again.

When reading the after start checklist, the PNF does not wait for a response for "ANTI ICE" before continuing to "ECAM STATUS". I tried it twice, so I don't think it was because the mic picked up some noise as response tor "ANTI ICE". Helge

The configurator is buggy as it apparently does not check what window numbers are in use already and just expects that it can use 8-13. VoxATC had always placed its windows as Window08 and Window09, and after the configurator was run there were to sets of Window08 and Window09. The solution was to manually rename VoxATC Window08 to Window14 and VoxATC Window09 to WIndow15 in all the panel.cfg files for the Airbus.

First of all: Thanks for the new FS2Crew version, I have really been looking forward to this. I hope you get a lot of customers and may pirates have FSX crashing all the time. My reason for posting this is just to note that it is not neccessary to assign a key to AUTOFEATHER (ARM/OFF) to open the main panel even though the manual states that it is the only way to do so. Just use the FSX menu and chose "Views" / "Instrument Panel" / "FS2Crew Main Panel". If you keep opening/closing the panel, then a key is nifty, but I tend to just open the panel and keep it visible at all times, and then the menu is just fine for opening it. Helge PS. Now get busy with the 777 version :)

If you fly faster at constant altitude under autopilot control, then the autopilot trims down to hold the altitude. Conversely, if I fly slow, then the autopilot will trim up to hold the altitude. At least that is what I think happened. I have seen the trim being moved by the autopilot to way outside the white area.

Thank you, I will try this.

Hi, I want to use MCE together with VoxATC, and read in the manual that the "end" and "space" keys disable MCE temporarily. However this doesn't seem to work, MCE still recognizes commands while I press any of these buttons. I checked the ini file and there is a "UseWithVoxATC=0" line there, which I assume is exactly what I want to use. Can you explain to me how I set this up and what those lines in the ini file are used? I want a keyboard button and/or a joystick button to disable MCE voice recognition while enableing VoxATC voice recognition while the key/button is pressed. If possible I would like both a keyboard button and a joystick button to work, but I can live with only one of them if that isn't possible. Helge

Thank you, do you know what this information is used for?

I have only seen this with the Q400, so you are probably right. I have another question: The co pilot keeps asking me for runway in use, and I cannot figure out what to say. Also, what is he using this information for?

Thanks for the answers. You are probably right that it was the trim that was way off when I took over manually. Guess I will have to keep an eye on how the trim is.