Hi there. Pete Dowson suggested that I draw your attention to a problem in the way AS6 is using FSUIPC. The post is here (saving me a long resume!). If you want more information, please let me know.http://forums.simflight.com/viewtopic.php?p=365600#365600Thanks,Martin :-)

We know FSHotSeat interfered with the FSUIPC processes Radar Contact uses and it is listed as causing incompatibilities. FSHotSeat is described as including the functionality of FSHotSeatFX. Perhaps a similar case is occurring.As I recall it affected the way FSUIPC reported some parameters.(Crossposted to the FSUIPC forum.)

Hi,Thanks for this.. we are looking into it..Best,

Hi,Just an update... We did find the potential cause of this but are unable to duplicate to confirm our suspicions. May I please ask that the full log with WRITE option enabled (nothing else) be sent to me at damianc AT hifisim.com ?Just some technical info about this: It is confirmed that the AS code should always be sending the registration key before any write, regardless of threading. In each potential thread that writes anything, the reg key is sent IN that thread. Without being able to duplicate (and no other reports of this) we suspect that something is getting 'hung up' somehow in the communications process.Also, you should be able to circumvent this problem entirely by adding the reg key via FSUIPC options manually, which is: 9G9LCNT2MDUYBest,

Hi,I made the log file that I sent to Peter D. back in November - I don't have it any more I'm afraid (maybe Pete kept a copy), and since I have installed the latest FSUIPC.dll file I haven't had the error occur again. I also stopped FSHotSFX loading automatically (as it seemed to be hogging things) and now only start it up after AS6 has finished loading all its data.That said, I was away for most of the time since November, so it's not sure that the problem is truly solved. It was only intermittent in any case, but if the same thing reoccurs, I'll post back and send you the log file.Sorry not to be more helpful.Martin