FSX Version Problems

[jxs]

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

[byork]

Hi John,Hard to guess... no one else has reported that, and those are pretty major and obvious.And the FSX version uses the exactly same code as FS9. It's the same gauge file.Are you starting on the ground?

[jxs]

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

[byork]

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

John,Are you sure you've read the manual?I'll throw out some guesses:V1: Was V1 entered in the FMC? I suspect it may not have been. Same with Trans Altitude call.That might explain the erroneous calls.You need to use the FMC for each flight as FS2Crew pulls a lot of required data from it.CDU pre-flight warning: This also goes back to the FMC... the FMC needs to be setup in full. If not, the FO will tell you during the checklist as you experienced.Did you run the "Before Start Procedure"?Where the engines already running before you tried to start the engines?If using APU, was the power source on the FS2Crew Config panel set to APU?Cheers,

[jxs]

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

[byork]

Hi John,It's all done via the iFly SDK.The mechanism between FS9 and FSX is identical.I'm sorry, I'm at loss for this one. No one else has reported it and we had a good size beta team.Something on your system is maybe "blocking" interaction between FS2Crew and the iFly???What that could be, I have no idea.Email me if you like and we can do a remote desktop. Maybe I can see what the problem is.Cheers,

[Guest sda222]

I've got the same problem.

[byork]

I've got the same problem.

Same answer as above.Please email and we can do a remote desktop so I can "see" what's happening.Assuming you're not using a cracked version of the iFly 737 or FS2Crew, which could result in all sorts of weird side effects, I can see no reason why it shouldn't work.Best,

[jxs]

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

[byork]

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

Hi John,I'm GMT + 9.... about 9 hours "ahead" of you.Pls email me at admin ** at ** fs2crew.comCheers,

[Joe L]

Same issues here. At CLEARED FO calls transition altitude and resets the altimeter, then calls V1 immediately. Both transition altitude and V-speeds were set in FMC, been flyiny the AC w/o FS2Crew for some time.