Sorry if some of these have already been mentioned but a few things I've noticed on my last flights.1. The FO won't set the transponder to TA/RA during the runway entry procedure2. The FO didn't switch the flight directors OFF after I said it was OK to clean up before vacating the rwy and nor did he switch them OFF during his shutdown flow. Switching them OFF is indicated both during his after landing flow and shutdown flow...?3. The FO left both the wheel well light and the pos light ON even after securing the a/c, is that standard procedure IRL?

Sorry if some of these have already been mentioned but a few things I've noticed on my last flights.1. The FO won't set the transponder to TA/RA during the runway entry procedure2. The FO didn't switch the flight directors OFF after I said it was OK to clean up before vacating the rwy and nor did he switch them OFF during his shutdown flow. Switching them OFF is indicated both during his after landing flow and shutdown flow...?3. The FO left both the wheel well light and the pos light ON even after securing the a/c, is that standard procedure IRL?

I'm pretty sure he does, this is an area where we tested extensively and it works for me, try again and see.The F/D thing is a bug and is fixed for the SPThe wheel well lights are a bug as well and fixed for a SP.

Works fine for me too in the Button version. He switches the TA/RA when asked for at 'Runway Entry Procedures', and switches off the the FD and all the lights as per script.

I'm pretty sure he does, this is an area where we tested extensively and it works for me, try again and see.The F/D thing is a bug and is fixed for the SPThe wheel well lights are a bug as well and fixed for a SP.

I guess I've done about 5 flights or so and I'm positive my FO never set the transponder to TA/RA however he always set it to standby...strange. Maybe I should mention I have ASDE-X disabled since I'm doing all my flying online on IVAO and ATC doesn't like when you have the transponder set to anything but standby when you're not on an active rwy.Good to hear the other things will be addressed in the SP and does that also include the POS LIGHT?

Works fine for me too in the Button version. He switches the TA/RA when asked for at 'Runway Entry Procedures', and switches off the the FD and all the lights as per script.

Ok, that's great! Wonder if it could be because you're using the button-controlled version and I'm the voice-controlled version but I always thought they were the same except for how you control them...using buttons or voice?

I think the TARA issue is associated with the IVAO pilot client.It's out of our control.SP1 will likely remove FS2Crew's attempt to control the Xponder in the IVAO pilot client for this very reason.Other bugs you've noted have been fixed in the upcoming SP1.Cheers,

The connection between the transponder switch in the NGX and IvAp (the IVAO pilot client) actually works perfectly fine so I don't think there's any issue there. When I move the transponder switch in the NGX that is also reflected in IvAp and when I (or FS2Crew's FO) move(s) the NGX transponder switch in the NGX to STANDBY that is also reflected in IvAp. What I've seen is just like I said above that for some reason my FS2Crew FO doesn't move the NGX switch to TA/RA during the runway entry procedure and I'm pretty sure if he would that would also move the IvAp transponder switch to TA/RA.So...to sum up I can't see why you would have to bother about the IvAp client since the connection between the NGX and IvAp already is there and is working just fine. As I see it all you should need to worry about is to have the FO work the NGX transponder switch and when he does that should also "automatically" move the IvAp transponder switch just like when I work the NGX transponder switch myself. And again...this already works when the FO moves the switch to STANDBY after landing and cleaning up so I can't see why it wouldn't work in the opposite direction moving it to TA/RA during the runway entry procedure.

Please help with the diff startcrew> > options regarding Pushback as i cant find it in the manual.I do not have problems with ground on arrivals, only departures will not respond to my voice.ThanksMichael M

The connection between the transponder switch in the NGX and IvAp (the IVAO pilot client) actually works perfectly fine so I don't think there's any issue there. When I move the transponder switch in the NGX that is also reflected in IvAp and when I (or FS2Crew's FO) move(s) the NGX transponder switch in the NGX to STANDBY that is also reflected in IvAp. What I've seen is just like I said above that for some reason my FS2Crew FO doesn't move the NGX switch to TA/RA during the runway entry procedure and I'm pretty sure if he would that would also move the IvAp transponder switch to TA/RA.So...to sum up I can't see why you would have to bother about the IvAp client since the connection between the NGX and IvAp already is there and is working just fine. As I see it all you should need to worry about is to have the FO work the NGX transponder switch and when he does that should also "automatically" move the IvAp transponder switch just like when I work the NGX transponder switch myself. And again...this already works when the FO moves the switch to STANDBY after landing and cleaning up so I can't see why it wouldn't work in the opposite direction moving it to TA/RA during the runway entry procedure.

1) It's not as simple as you put it, we tested this for hours but the ivap transponder wouldn't set correctly. But,..if what you say is correct the transponder would be set correctly without any input from FS2Crew so there really isn't any issue.2) I can assure you,..the F/O sets the transponder correctly,..again,..we tested this dozens of times and I and the rest of the beta team have not found any issues with it. The only other reason could be some system specific issue. Try reinstalling FS2Crew.

Take in account that there are 2 versions (FSX internal and external) from the IVAP-Client !

Just took off for another flight and this time I watched the transponder switch closely after announcing rwy entry procedure and found something interesting...the FO did move it to TA/RA just as you said but it only remained in that position for a split second, then it went back to STANDBY by itself....hmm...? I then moved it back to TA/RA myself and it stayed in that position.This is just wild guessing on my part, I noticed when the FO moved the switch it went directly from STANDBY to TA/RA skipping the modes between...maybe if you could get the FO to actually move the switch from STBY to the next mode and so on all the way to the last position (TA/RA) in the same way you move the switch when you do it manually it would work better.Would be great if this could be fixed but if not not a big deal, I'll just remember to move the switch to TA/RA myself.

Just took off for another flight and this time I watched the transponder switch closely after announcing rwy entry procedure and found something interesting...the FO did move it to TA/RA just as you said but it only remained in that position for a split second, then it went back to STANDBY by itself....hmm...? I then moved it back to TA/RA myself and it stayed in that position.This is just wild guessing on my part, I noticed when the FO moved the switch it went directly from STANDBY to TA/RA skipping the modes between...maybe if you could get the FO to actually move the switch from STBY to the next mode and so on all the way to the last position (TA/RA) in the same way you move the switch when you do it manually it would work better.Would be great if this could be fixed but if not not a big deal, I'll just remember to move the switch to TA/RA myself.

I've seen this, i saw a video of it, you were using ivap when it happened correct ?

I've seen this, i saw a video of it, you were using ivap when it happened correct ?

Yes I was, I do all my flying online on IVAO. From your question I presume it's IvAp that somehow gets confused when the FO switches the transponder directly to TA/RA and moves the switch back to STBY?I fully understand if you feel this issue is "out of your scope" but as I suggested above it might be the fact that the FO moves the switch directly from SDBY to TA/RA skipping the modes in between (at least it looked that way) and if that is what gets IvAp react by returning the switch to STBY maybe a simple? solution would be to let the FO not skip the modes between SDBY and TA/RA - any chance you could try this? I'm sure we are quite a number of people using FS2Crew when flying online on IVAO so I'm pretty sure I wouldn't be the only one who would be thrilled if this could be solved.

The F/D thing is a bug and is fixed for the SP

On my last flight I also kept a close eye on the flight directors after landing and I noticed the FO did switch them OFF during his clean-up procedure after vacating the rwy but then before I was about to call for the secure a/c procedure I noticed they were back ON again so my guess is the problem is switching them OFF is included both in the FO's after landing flow and shutdown flow making him switching them OFF during the after landing flow and then when he does it again during the shutting down flow he actually switches them back ON when he believes he switches them OFF since they already were OFF...

Yes I was, I do all my flying online on IVAO. From your question I presume it's IvAp that somehow gets confused when the FO switches the transponder directly to TA/RA and moves the switch back to STBY?I fully understand if you feel this issue is "out of your scope" but as I suggested above it might be the fact that the FO moves the switch directly from SDBY to TA/RA skipping the modes in between (at least it looked that way) and if that is what gets IvAp react by returning the switch to STBY maybe a simple? solution would be to let the FO not skip the modes between SDBY and TA/RA - any chance you could try this? I'm sure we are quite a number of people using FS2Crew when flying online on IVAO so I'm pretty sure I wouldn't be the only one who would be thrilled if this could be solved.

Try it without ivap and see how it goes.

Try it without ivap and see how it goes.

Sure, will do and report back but as I understood it from your previous answers it's pretty clear already it will work just fine when not using IvAp.Will report back tomorrow.

Ok, tried running the rwy entry procedure now without before I started IvAp and sure enough the transponder switch stayed at TA/RA when the FO moved it into that position. I then started IvAp and tried the rwy entry procedure again and the problem was back with the transponder switch jumping back to STBY right after the FO set it to TA/RA. I then tried ending IvAp and did the test again but the problem remained so it seems once you've started IvAp once you will have to restart FSX to get rid of the problem.Could you tell how you programmed the FO to move the switch to TA/RA, does he move it directly from STBY to TA/RA skipping the positions between or does he actually move the switch through all different modes?