Jump to content

Archived

This topic is now archived and is closed to further replies.

iainsmith

Intermittent problem with ASA & Radar Contact

Recommended Posts

Last night, halfway through a flight from London Stansted (EGSS) to Zurich (LSZH), on FS9.1 with ASA Build 435 and Radar Contact (RC) 4.3, I had a recurrence of a problem that I thought had been fixed. A message came up behind FS saying "FSUIPC_WAIT cannot change 3xxxxxxxx (a 6 or 7 digit number) it remains as 3xxxxxxxxx (the same number)". This causes RC to stop working and ok ing the message doesn't seem to do much as it comes back after a few seconds. FS does keep running and the flight could continue without ATC from RC. Also, the number that is displayed is not always the same.One then has to close RC and re-start it but the problem is that RC does not have a "resume" feature so, in reality, if you want RC for the flight you have to re-start the whole thing.This only happens with ASA, I have never experienced it with ASv6.5 and I thought I saw it listed in bug fixes for ASA. Maybe it was fixed for B433 but it's back with B435?I am also posting this on the RC forum but the consensus before seemed to be that ASA was the cause.Iain Smith

Share this post


Link to post
Share on other sites
Last night, halfway through a flight from London Stansted (EGSS) to Zurich (LSZH), on FS9.1 with ASA Build 435 and Radar Contact (RC) 4.3, I had a recurrence of a problem that I thought had been fixed. A message came up behind FS saying "FSUIPC_WAIT cannot change 3xxxxxxxx (a 6 or 7 digit number) it remains as 3xxxxxxxxx (the same number)". This causes RC to stop working and ok ing the message doesn't seem to do much as it comes back after a few seconds. FS does keep running and the flight could continue without ATC from RC. Also, the number that is displayed is not always the same.One then has to close RC and re-start it but the problem is that RC does not have a "resume" feature so, in reality, if you want RC for the flight you have to re-start the whole thing.This only happens with ASA, I have never experienced it with ASv6.5 and I thought I saw it listed in bug fixes for ASA. Maybe it was fixed for B433 but it's back with B435?I am also posting this on the RC forum but the consensus before seemed to be that ASA was the cause.Iain Smith
Hi Iain,I have sometimes the same problem as you...to go on with radar contact you can do a reset "refresh AI aircraft" in the report screen of ASA. I think it is a problem between ASA, Radar contact and Ai aircraft but it is just a supposition anyway if you do what I told you RC will work again and you can continue you flight with radar contact like before.... :( Christian

Share this post


Link to post
Share on other sites
Hi Iain,I have sometimes the same problem as you...to go on with radar contact you can do a reset "refresh AI aircraft" in the report screen of ASA. I think it is a problem between ASA, Radar contact and Ai aircraft but it is just a supposition anyway if you do what I told you RC will work again and you can continue you flight with radar contact like before.... :( Christian
Hi Christian,Thanks, it had never occurred to me to do that. I will try that next time it happens. :( Iain

Share this post


Link to post
Share on other sites
Hi Christian,Thanks, it had never occurred to me to do that. I will try that next time it happens. :( Iain
Hi,It is an alternative to pass through this bug but there is a problem with ASA and Radar contact, because with ASv6.5 this problem never happened to me........ so the source of conflict is ASA.Christian

Share this post


Link to post
Share on other sites

×
×
  • Create New...