November 26, 201411 yr I was flying a very good approach profile in the new Aerosoft Airbus A320 using FS2Crew voice command to change altitude, heading and speed. At 3000ft with the height step set to 1000, I called 'Set Altitude 2500' in order to capture the Glideslope. The FO's setting of the altitude was all over the place including negative altitudes. I have to Cancel Last Command to regain control. I wonder if the STEP setting on the FCU was taken into account by FS2Crew. There is no separate command for the 100/1000 step switch behind the ALT knob. Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
November 27, 201411 yr Commercial Member What command was actually heard, namely, what you saw in the Green Bar? B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
November 27, 201411 yr Author Unfortunately, due to another issue, nothing was displayed in the green bar. Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
November 27, 201411 yr Commercial Member Unfortunately, due to another issue, nothing was displayed in the green bar. What issue is that? If you have DSP selected on the FS2Crew Main panel, you should see everything the speech recognition system "hears" in the green bar. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
November 27, 201411 yr Author Hi byork The issue I had was with Steve's DX10 fix which had set the DSP to x3 meaning that nothing could be seen in the green line. Having corrected that problem this morning I can now see all my commands and FO responses in the green line. As a result I could not see any text response for the reported problem. Sorry. Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
December 1, 201411 yr Author Further Information. I managed to repeat the reported problem last night. Flying at 3000ft with Altitude Step set to 1000, I called 'Set Altitude Two Five Zero Zero' only to see the input go up and down (including below 0 feet). I immediately called 'Cancel Last Command' to stop the action and manual switched to Step = 100. On reissuing the 'Set Altitude Two Five Zero Zero', the FO correctly set 2500ft no problem. The Airbus unlike Boeing has this shortcut to change the FCU Altitude in 100 or 1000 feet steps. Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
December 2, 201411 yr Commercial Member In that case, pls leave the altitude selector at 100 until I can sort this in an update. With the alt selector at 1000 you're confusing the simulation by calling for an altitude that is not an even 1000. Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
December 2, 201411 yr Author Good point Brian. For interest, the Lvar concerned is AB_AP_ALTSTEP (0=100,1=1000). Andrew Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
Create an account or sign in to comment