FSUIPC 4.9 and Air Hauler

[fs4]

Pete, since installing v4.9, the interface with Air Hauler (AH) has been showing very delayed responsiveness. Pop up messages are appearing 1 or 2 minutes later than they should, the ground proximity verbal alerts are so delayed as to be useless (e.g. 500 feet being reported at touchdown), and the A.H. has been hanging after saving an en route flight. These  problems have been reported by me and at least one other user on the Just flight AH forum. Can you think of a possible reason and a possible work around?

 

Thanks.

 

[Pete Dowson]

Pete, since installing v4.9, the interface with Air Hauler (AH) has been showing very delayed responsiveness. Pop up messages are appearing 1 or 2 minutes later than they should, the ground proximity verbal alerts are so delayed as to be useless (e.g. 500 feet being reported at touchdown), and the A.H. has been hanging after saving an en route flight. These  problems have been reported by me and at least one other user on the Just flight AH forum. Can you think of a possible reason and a possible work around?

 

 

Since the only change between 4.90 and the previous version was the removal of the Signature, which is only checked on loading, I can't se how this can be related to FSUIPC. I think you need Air Hauler support to help.

 

Regards

Pete

[fs4]

Thanks Pete. Yes, I thought that was the only change from the previous version. The trouble is, I don't know what version of FSUIPC I had prior to the upgrade to 4.90. It may well have been quite old and 4.9 may have included a number of accumulated developments that had occurred between the originally installed version and the current one. I installed AH quite a while back off a disk. As I mentioned, another user and I have had identical experiences after upgrading, and we have both mentioned it on the AH Just Flight Forum. Hopefully Duncan will be able to come up with something.

[Pete Dowson]

Thanks Pete. Yes, I thought that was the only change from the previous version. The trouble is, I don't know what version of FSUIPC I had prior to the upgrade to 4.90. It may well have been quite old and 4.9 may have included a number of accumulated developments that had occurred between the originally installed version and the current one. I installed AH quite a while back off a disk. As I mentioned, another user and I have had identical experiences after upgrading, and we have both mentioned it on the AH Just Flight Forum. Hopefully Duncan will be able to come up with something.

 

 

Well, I don't know of any problems afflicting other applications in such ways.  Maybe Air Hauler was making use of something unofficial, or buggy, and that's been changed -- used for something, or fixed. I'm sorry, but without information about what it is doing that isn't wanted I can't help. If the developer looks at it and can tell me what is wrong I can take a look, of course.

 

Pete

[fs4]

Thanks for your thoughts Pete. For the sake of completeness for archival purposes, I can record here that the version of FSUIPC that came with my copy of AH was 4.5. I have re-installed it and it appears to have restored full functionality to AH. This means that the relevant change that has caused the problem has been between 4.6 and 4.8 (since 4.9 changed no functional aspect). I suspect AH users have never bothered to upgrade to these versions since they were only using FSUIPC as a run-time, unregistered interface. This means the issue was never revealed until now when people have been moved to upgrade by the publicity blitz urging upgrade for security reasons (but in fact I suspect this really only applied to the registered version?). Obviously trying to track down all the possible changes that might be relevant would be a fruitless exercise. Best to just let it lie. Thanks again.

[Pete Dowson]

Thanks for your thoughts Pete. For the sake of completeness for archival purposes, I can record here that the version of FSUIPC that came with my copy of AH was 4.5. I have re-installed it and it appears to have restored full functionality to AH. This means that the relevant change that has caused the problem has been between 4.6 and 4.8 (since 4.9 changed no functional aspect). I suspect AH users have never bothered to upgrade to these versions since they were only using FSUIPC as a run-time, unregistered interface. This means the issue was never revealed until now when people have been moved to upgrade by the publicity blitz urging upgrade for security reasons (but in fact I suspect this really only applied to the registered version?). Obviously trying to track down all the possible changes that might be relevant would be a fruitless exercise. Best to just let it lie. Thanks again.

 

 

Well, actually, I would rather not "let it lie", because I cannot support older versions and would like to know what this program is doing which is appearently now either not supported or become faulty. If you have contact with the author or the support folks for it I would like them to contact me with the reasons why so that they can be fixed if possible.

 

Additionally, if or when GlobalSign do actually do as they threatened / promised to do in revoking the signature used on versions before 4.9 then it will affect everyone, as FSUIPC will simply refuse to work any more, complaining of corruption detected by a bad signature. They did say the revocation would occur within a matter of days, and that was weeks ago, so I don't know if it will ever happen, but still ...

 

Regards

Pete

[fs4]

Pete, yes, I and another user have already reported the issue on the AH forum. The creator of the program is presently overseas on vacation, but he has indicated he will follow it up when he returns in a couple of weeks time, to try to determine where the problem is occurring.

[Pete Dowson]

Pete, yes, I and another user have already reported the issue on the AH forum. The creator of the program is presently overseas on vacation, but he has indicated he will follow it up when he returns in a couple of weeks time, to try to determine where the problem is occurring.

 

Okay. I'm on holiday the week after next, so probably we are both back at the same time. :-)

 

Pete