flightman27R Posted August 20, 2005 Report Share Posted August 20, 2005 I know this subject has been discussed before, but I have tried installing, uninstalling, re-installing, etc., of Fs Hot Seat/FSSFX and FSUIPC's latest version. I know that reverse thrust sounds made by AI aircraft were supposedly broken when using the latest version of FSUIPC, but some users reported that Pete had done something that corrected the problem. Can someone share this fix with me and end my frustration? I have a registered version of FSUIPC 3.48, along with full copies of FS Hot Seat and FSSFX. Please advise. Thanks!! Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 20, 2005 Report Share Posted August 20, 2005 I know that reverse thrust sounds made by AI aircraft were supposedly broken when using the latest version of FSUIPC, but some users reported that Pete had done something that corrected the problem. The problem was only in one or two versions (3.45/3.46), where the classification of landing AI aircraft was incorrect -- they were still in the Airborne table after touchdown, until they finished "landing" mode. This was fixed in version 3.47, as described in this item of the release details (above and in the History document): 26. The classification of AI traffic into the airborne or ground TCAS tables was partly in error for AI aircraft in "Landing" state. These were classified as airborne even after touch-down. This is fixed in this release. It's been okay since then -- i.e. in both 3.47 and 3.48. The classification of a "Landing" aircraft is now decided according to the "On Ground" flag operated by FS. When the state changes to "Rolling out" they are always in the Ground table. The earlier problem with FSHotSeat was because it only checks the Ground aircraft so didn't see Landing aircraft till the "rolling out" phase, which is either too short for it to see or which it doesn't look for in any case. If you are still having a problem with FSHotSeat you should ask their support. I'm afraid I don't have the program and I really don't know what it is doing. I fixed the original problem as soon as I was notified of it (it didn't affect any other program, as the effect of being in the "wrong table" is so transitionary). Regards, Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now