jxs

I've just tried this out at EGUM, runway 29.It does seem an 'FMC' problem.If you try a raw data approach (ie with no route data entered in the FMC, the button APP works (lights up) and the G/S can be captured ok.If you try the same approach with simply EGUM entered as the destination airport in the FMC, you get this problem, APP does not light when selected and the G/S is not armed.There no need to enter a runway, and there are no ILS approaches listed to select. So although radio is tuned correctly it does not work,John Skipsey

Bryan,Oop -looks like I need a new hearing aid.:( As he does most of the work, I assumed it was the FO getting started.Thanks,John

Bryan,In the Button Control version, when you start the pre flight process from the config panel you hear the FO say 'Let's start setting up"This seems to be missing in the Voice version.Is this deliberate or have I a problem with my setup?Regards,John

Bryan,I've just come across a minor bug in the Before Take-Off Checklist.When making the Stab Trim Call, if you call 'Five Point Zero Units' the voice recognition engine shows it in the green bar as 'Five Point Zero Unit', ie with the plural 's' on unit.This might seem much, but it prevents the checklist from 'clearing', ready for the take-off calls.All other values I've tried seem ok.Regards,John

Being the one that discovered this, I would add, the problems do only seem to occur with the FSX version.In fact, the reason it took so long to find the cause was that I was quite happily resizing the command panel whilst I was using the FS9 version, with no problems. Hence later, when I moved on to the FSX version, I was doing this almost as second nature, and it just didn't occur for a long time that it could be causing the problems I was having.So if you're using FS9, you probably won't have had any problems. Further, it may also only be operating system dependant as I am on Win 7 64bit and as far as know so are all the others who experienced the problem. So those on xp may also be ok.However, I do agree with Bryan that, until a solution can be found to why resizing causes these problems, that the default should be that the panel should be locked.This is because it's too easy resize it inadvertently when trying to move it, and this can cause a system crash.John

Thanks Bryan,I was thinking about that option, but need to resolve the issue I'm having in with FSX first, as in my other thread.John

Bryan,I am still at a loss to understand what could be blocking the FSX version, if the mechanism used is the same for both FS9 and FSX versions, and they are both run on the same computer/operating system!I am a great fan of your program and want to be able to use the FSX version as well as FS9, and am also thinking of migrating to the voice edition.However, I'm wary of doing this incase the same problem exists (and I hate to be beaten by a mere machine), so to try and resolve this, I have adopted the nuclear option, and reformatted my hard drive, thus hoping to remove whatever is causing this blockage.I have re-installed Windows and FSX(sp2) and the latest versions of iFly 737 (1.01) and FS2Crew (1.5) AND YET THE PROBLEM REMAINS!!As there is now no other software installed, this seems to lead to a Driver issue, yet I don't feel my setup is particularly unique, see below:Intel I5-760 (oc @ 3.8GHz)ASUS P7P55D8GB DDR3 1600MHz RAM 1GB NVidia GTX460120GB OCZ Vertex SSD640GB Caviar 72000rpm HDWindows 7 Home Premium 64bit The os and FSX are on the SSD and FSX is in it's own directory c:\FSX So yes, I'd like to take up your offer of a remote desktop (do you mean Windows Remote Assistence?) session and maybe you can spot something.I'm in the uk, where are you time zone wise?How do I contact you by email?Thanks,Johnps absolutely NOT a pirate/cracked version of anything

Bryan/ Damien,Thanks for your replies. I think 767FAN and I are really voicing the same concerns, altthough he has put it a little better than me.I do understand you are trying to pick the 'best' course from the many different scenearos that could exist, but must agree this part is a little 'clumsy', and maybe doesn't follow majority of real world flows, who probably don't have/use the latest FMC VNAV software version anyway.For example, again with NADP1, the Capt calls 'Level Change", yet due to the flow layout cannot call for "Command A" until AFTER he's called "VNAV". Is this realistic?I trust you can find a better answer, because this mars what is an otherwise great program.Thanks,John

Damien,I think the question is, in NADP1, who 'Sets Flaps up Speed'? the implication is the Capt (PF) as it's not part of the FS2Crew Flow for NADP1.John

Bryan,I've read the manual inside out. If you look at earlier posts you'll see I even corrected it for you.As I've said before, I've been using it for a while with FS9 with no problems.If I try exactly the same flight with my FS9 version it works fine!And yes of course all the FMC entries were made!It seems to me that for FSX, FS2Crew is having some problems reading some of the data from iFly (FMC?) which is confusing the flow.Do the two versions use the same mechanisms?Is it just the iFly SDK and/or FSUIPC or something else?What's really confusing is why I seem to be the only one with the problem. What's unique about my set up. I'm on Win7 64 bit and as I've already said, I have done a fresh install of of both FSX and iFly together with FS2Crew.If you've no clue, I guess I'll have to stick with FS9.Thanks,John

Bryan,Yes, I'm on the ground, I'm starting from a cold and dark situation.I'm just as confused, as I've said, the FS9 version works fine, and I waited a few days to see if anyone else reported any problems with FSX.To make matters worse, I've just had to re-install FSX and the ONLY add-ons at the moment are the iFly 737 and FS2Crew and yet the problem persists :( As it's the same download as the FS9 I'm not sure re-downloading would help either.I'm really stuck :( John

Bryan,I've just upgraded to V1.5 and at the same time am trying out the new FSX version.I've got no problems at all with new FS9 version, but have several problems with the flows for FSX.The program loads ok and I can start the PF procedure and everying seems fine until I click the Preflight Checklist after the F/O has completed his preflight procedure.He calls the first item 'Oxygen' but the immediately says 'Transition Altitude 29.92' which the PF repeats. He also sets the STD switch.I can then proceed as normal until, as part of the 'Before Start Checklist', I get an erroneous warning 'I may want to check again' regarding the 'CDU Preflight' item.Again, I can proceed until 'Start Engine 2' (I'm doing APU start) when he repeats the command ok and clicks the starter switch ok, but then immediately responds 'Starter Cutout' (not waiting until the switch actually resets). Further, he had failed to turn the packs off before trying to start!The same for engine1!There are a couple of further minor faults until, when we get to the runway, following 'Cleared', we again get the 'Transition Altitude message' and he again selects STD.Following 'TakeOff' he announces 'V1 ' immediately before the A/C even starts to roll!There are various further faults which I won't go through for the rest of the flight.I've tried a complete re-install of FSX, iFly and FS2Crew but the problem remains.Please help.John

Henri,I was responding to leegra's reference to the manual (FS2Crew), but understand how the confusion arose.John

Actually this isn't covered in the manual (well v1.4 anyway).In the Crew Flow procedure for Climb item 7. actually says: Engage autopilot: "AUTOPILOT ON". Whereas really it should say: Engage autopilot: "Command A". John

Sorry Bryan, I'm still not clear.If I use NADP1 should I get a "SET FLAPS UP SPEED" call?If the answer is yes than then I have a problem because I get "LEVEL CHANGE" insteadIf the answer is no then the manual is wrongThanks,John

:( :( Can nobody help?Bryan,Under what circumstances should 'LEVEL CHANGE' be commanded?It's not mentioned anywhere in the Manual (nor in Julio Cesar's Flow document).John

Hi,I'm using version 1.4 and am having a problem trying to follow the Climb flow described in the user manual.item 4 states:If using the NADP1 profile: Call "SET FLAPS UP SPEED". however, for NDAP1 I only get the option "LEVEL CHANGE""SET FLAPS UP SPEED" only appears if I use NADP2.Is this an error in the manual, am I doing something wrong, or do have I a corrupt system?Thanks,John

I don't think it's a trade secret :( .From my current copy:"For sale in UK shops on April 21." John