FSUIPC 3.40

[RichardL]

Hi Pete,

FSHotSeat is having problems with AI engine reverse sound when using FSUIPC higher than 3.40. Is 3.40 available on your site? I would like to roll back to 3.40 until the problem is resolved.

Thanks,

Richard

[Pete Dowson]

FSHotSeat is having problems with AI engine reverse sound when using FSUIPC higher than 3.40.

FSUIPC does not touch sound or have anything whatsoever to do with it.

If you have a problem with >3.40 which isn't present in 3.40 then the most likely cause is an incorrect user Key. Try removing the FSUIPC.KEY file from the FS Modules folder. If that fixes it, then I need to see the KEY file -- do NOT show it here, ZIP it and send it to me at petedowson@btconnect.com.

Is 3.40 available on your site? I would like to roll back to 3.40 until the problem is resolved.

[\quote]

I don't have a site, and there is only ever one version of FSUIPC, currently 3.45. The resolution of a problem specific to your system is in your hands.

Pete

[RichardL]

Pete,

I'll give your suggestion a try.

I just wrote what FSHotSeat has posted on their support page http://fshotseat.com/ . I have no idea what is causing the problem. All I know is many FSHotSeat users are affected. FSHotSeat is telling affected users to go back to 3.40 if no AI reverse sound is heard. They are not supplying or linking to 3.40 so I decided to ask you.

Would you mind if I posted your reply to their support forum? Wouldn't be fair to blame you if FSUIPC is not causing the problem.

Richard

[Pete Dowson]

I just wrote what FSHotSeat has posted on their support page http://fshotseat.com/ . I have no idea what is causing the problem. All I know is many FSHotSeat users are affected. FSHotSeat is telling affected users to go back to 3.40 if no AI reverse sound is heard. They are not supplying or linking to 3.40 so I decided to ask you.

The FSHotSeat author has not contacted me, and I have absolutely no details about such a problem. I am afraid that it will never be "fixed" if no one seeks a solution. Going back to an old unsupported release really solves nothing.

Would you mind if I posted your reply to their support forum? Wouldn't be fair to blame you if FSUIPC is not causing the problem.

I'd really rather you check the KEY file first please. The suggestion I made to you was merely to ascertain whether it was due to a bad user key, but. I'm sorry, I omitted to ask whether you are FSUIPC user registered first. If you are not, then my earlier post is completely irrelevant so shouldn't be repeated in any case.

If you do have a bad key (that is a stolen or counterfeit FSUIPC user key) then most things using FSUIPC won't work in any case. What happened after 3.40 is that the user key checking was tightened. So far there's been no case at all of any good non-time limited keys falling foul of the checks, but about forty cases of counterfeit keys discovered and one good but time-limited key.

If you do go back to the FSHotKey support site then the best thing to do would be to have the FSHotSeat person responsible for this suggestion contact me directly, and discuss what is happening so a solution can possibly be found. Maybe FSHotSeat is writing to an undocumented part of the FSUIPC offsets, the function of which I am not aware of, and that area has been re-mapped elsewhere. If this is the case I'm sure it can be located and rectified quite quickly.

It has been several months since version 3.40 was superseded (five months at least, in fact), with as many intermediate releases. To let a problem go for so long with no one botthering to try to get it fixed doesn't really bode well. Why not see if it can be dealt with, even if belatedly?

Thanks & Regards,

Pete

[RichardL]

Pete,

Zipped .key and .log files emailed to you yesterday. No reply yet from FSHotSeat support.

Richard

[Pete Dowson]

Pete,

Zipped .key and .log files emailed to you yesterday. No reply yet from FSHotSeat support.

Richard

Not arrived yet. Can you re-check?

Pete

[RichardL]

FSHotSeat support replied to my email. They indicated that a change in FSUIPC created a bug in their software. No mention of what changed or how if affected the software. Hopefully they will contact Pete to resolve the problem.

Richard

[lthorsson]

Probably this change is the problem "5. On FS2004, AI traffic is now generally classified as "on ground" or "airborne" according to its state and not only its "on ground" flag" :?

[Pete Dowson]

Probably this change is the problem "5. On FS2004, AI traffic is now generally classified as "on ground" or "airborne" according to its state and not only its "on ground" flag" :?

Why would that cause a problem for FSHotSeat? All that does is move some TakeOff2 and maybe "Landing" state aircraft from one TCAS table into another. The FS "on ground" flag goes through a bit of on/off indecisiveness when aircraft are bouncing about on the runway.

Regards,

Pete

[lthorsson]

I am not a programer but what I can see is it the only thing who been change in 3.44 and 3.45 concerning landing AI/AC.

FSHotSeat start a reverse sound direct after a AI/AC has landed,

my thought was that FSHotSeat now dont know when the AC is on ground,

and don't start the sound. :oops:

Maybe I am wrong.

Regards

Lars

[Pete Dowson]

I am not a programer but what I can see is it the only thing who been change in 3.44 and 3.45 concerning landing AI/AC.

FSHotSeat start a reverse sound direct after a AI/AC has landed

Is that what the 'bug' is? No one has actually explained it to me yet. In that case it is a possibility! Sorry to have disbelieved you!

my thought was that FSHotSeat now dont know when the AC is on ground, and don't start the sound.

Well, the airborne aircraft are transferred from the airborne TCAS table to the ground TCAS table pretty soon in any case.

Let me check the code:

The actual distinction between airborne and ground, for FS2004 only, is currently:

If state = 138, "Taking off", then the "on ground" flag is used.

If state is one of these, it is on the ground:

128 Initialising

129 Sleeping

130 Filing flight plan

131 Obtaining clearance

132 Pushback (back?)

133 Pushback (turn?)

134 Starting up

135 Preparing to taxi

136 Taxiing out

137 Take off (prep/wait?)

143 Rolling out

145 Taxiing in

146 Shutting down

and it is airborne in these states:

139 Departing

140 Enroute

141 In the pattern

142 Landing

144 Going around

AHA! I see a bug! There's a typo! The first check above should be:

If state = 138, "Taking off", or

If state = 142, "Landing"

then the "on ground" flag is used.

The Landing, like TakeOff2, is a transitional state and I need to determine it by the on ground flag.

In the code the second comparison is actually for state = 114 which doesn't even exist!

This could have been fixed months ago if only folks had reported the details. Your suggestion is the first which even mentioned to me what the problem actually was. Thanks!

I have fixed it in the code here and it will be in the interim test version I will be uploading here in a couple of days.

Apologies again,

Regards,

Pete

[RichardL]

Pete,

I'll email FSHotSeat and ask them to read the post. Still curious why they never contacted you for help. Sort of like being lost and not wanting to ask for directions. One of those "guy" things I guess.

Richard

[Murmur2k]

Thanks Pete for the quick work. It is true that many of us using FSHotSeat have been putting up with the problem for a while, guess the reason why noone up until now mentioned it here is that its FSHotSeat's responsibilty to ensure that its software works even if it is down to an external company's program.

Will you post a link to the updated version here or on your main page?

Once again, thanks for your efforts.

[Pete Dowson]

Will you post a link to the updated version here or on your main page?

I've not really got a "main page". The nearest to that is the page that Enrico Schiratti maintains with all my stuff.

I am not providing full new releases yet. I'm targetting those for the end of the month or early March. I'll just be posting test versions for folks to try and, if applicable, feedback problems and so on. These will be within announcements here, at the top of this forum. They will contain the modules as attachments, if I can keep the size down to what I'm allowed here.

This is an experiment at a wider Beta test period than the very restricted ones I've been operating till now. I'm doing this because there have been some relatively serious problems recently which no one in my normal circles of testers found.

I'm also trying to get folks to expect a slower rate of updates than in the past. Getting a serious update ready, tested and documented every month is exhausting me! :wink:

Regards,

Pete

[lthorsson]

Thanks for the FSUIPC fix, now works FSHotSeat:s revers sound again.

Best Regards

Lars

[RichardL]

Same here.

Thanks,

Pete

PS I also had a problem with the pmRJ fuel panel not displaying fuel usage. It is working again. Not sure if the test build fixed it but I'll report it to Enrico.