I need version 4.2 of FSUIPC

[jetboy23]

Hello! Due to some minor problems with FSX between a couple airplane malfunctions, I was told to swap out the current FSUIPC dll file for the dll file from versino 4.2. Does anyone know where I can find this version?

Thanks!

[Pete Dowson]

Hello! Due to some minor problems with FSX between a couple airplane malfunctions, I was told to swap out the current FSUIPC dll file for the dll file from versino 4.2. Does anyone know where I can find this version?

No. Use 4.745 or later. The earliest supported FSUIPC4 is 4.70. If there's some problem it needs fixing, not retreating from.

Regards

Pete

[jetboy23]

No. Use 4.745 or later. The earliest supported FSUIPC4 is 4.70. If there's some problem it needs fixing, not retreating from.

Regards

Pete

Hmmm, well thanks for reply Pete! But do you think that resorting back to 4.745 will solve the problems I'm facing like everyone says?

[Pete Dowson]

Hmmm, well thanks for reply Pete! But do you think that resorting back to 4.745 will solve the problems I'm facing like everyone says?

Since I have no idea what your problems are, I cannot possibly answer that. But I can say that if you do have problems with 4.745 or later which weren't present in 4.2 (which is four years out of date and many many versions ago), then they need to be made known so i can fix them! Going backwards is never the right answer.

Who are these "everyone" who are telling you all this stuff? Who says you should use 4.2? That's insane advice!

Regards

Pete

[jetboy23]

I wish I could give you a direct link, but I can't find it anywhere on the internet. The problem is with the Captainsim 757, when disengaging the autopilot. When the pilot (me) disengages the autopilot by either pressing the disengage bar, or by turning off the flight director, the plane is suppposed to disengage the autopilot, and switch control over to the yoke (Just like any other plane). With this plane, when trying to disengage, the yoke has no control for about 10-30 seconds, then, randomly, it gives me control. Captainsim is not releasing any updates to fix this problem, which is crazy. This is a very known problem on all of the captainsim forums, and probably other forums. Everyone (as in the people who have fixed the problem themselves) say that resorting to 4.2 fixed the autopilot problem. I don't know why, but that's what they say.

Thanks for your time Pete

-J

Edited November 16, 2011 by jetboy23

[Pete Dowson]

The problem is with the Captainsim 757, when disengaging the autopilot. When the pilot (me) disengages the autopilot by either pressing the disengage bar, or by turning off the flight director, the plane is suppposed to disengage the autopilot, and switch control over to the yoke (Just like any other plane). With this plane, when trying to disengage, the yoke has no control for about 10-30 seconds, then, randomly, it gives me control.

Sounds like it uses FSUIPC to disconnect the controls, but doesn't tell it to reconnect them afterwards. FSUIPC times out the disconnection when it isn't refreshed for about 12 seconds (if it's going up to 30 seconds your system is rather overloaded).

You can fix this either by programming a key or button to reconnect controls, or by using a Lua plug-in which does it automatically when it sees the autopilot disconnect. I can probably make such a plug-in for you, but I'd need to know how to detect the A/P going off. Can you tell me how you are programming the A/P disconnect or FS off actions? I assume they are not the default FS actions / controls? Maybe you can enable FSUIPC event logging and do such an action so we can see if it uses anything in FS which FSUIPC detects.

To program a button or switch to do the job just assign it to "Offset byte set" then set the offset to x310A and the parameter to 0. Try that first.

If your A/P disconnect is a toggle you could add it to the actions carried out when you toggled it off. Or, actually, you could add it anyway as it wouldn't matter doing that when turning the A/P on, because the aircraft code would be setting it as it needs afterwards in any case.

Regards

Pete

[jetboy23]

Sounds like it uses FSUIPC to disconnect the controls, but doesn't tell it to reconnect them afterwards. FSUIPC times out the disconnection when it isn't refreshed for about 12 seconds (if it's going up to 30 seconds your system is rather overloaded).

You can fix this either by programming a key or button to reconnect controls, or by using a Lua plug-in which does it automatically when it sees the autopilot disconnect. I can probably make such a plug-in for you, but I'd need to know how to detect the A/P going off. Can you tell me how you are programming the A/P disconnect or FS off actions? I assume they are not the default FS actions / controls? Maybe you can enable FSUIPC event logging and do such an action so we can see if it uses anything in FS which FSUIPC detects.

To program a button or switch to do the job just assign it to "Offset byte set" then set the offset to x310A and the parameter to 0. Try that first.

If your A/P disconnect is a toggle you could add it to the actions carried out when you toggled it off. Or, actually, you could add it anyway as it wouldn't matter doing that when turning the A/P on, because the aircraft code would be setting it as it needs afterwards in any case.

Regards

Pete

Thanks for your reply Pete!I use my mouse to hover over and click the autopilot disconnect bar. However, the "Z" key on my keyboard also toggles back and forth the autopilot. I guess this is what you mean about "programming the autopilot disconnect". Also, in my FSUIPC options and settings, I only have the about tab, and logging tab. Is this supposed to happen?About the plug-in, I would really appreciate if you could make such plug-in for me, as long as it doesn't take too much of your time.Thanks-J

[Pete Dowson]

Thanks for your reply Pete!I use my mouse to hover over and click the autopilot disconnect bar. However, the "Z" key on my keyboard also toggles back and forth the autopilot. I guess this is what you mean about "programming the autopilot disconnect".

It is using the FS autopilot, then, so it shouldn't even need to disconnect the controls as FS does that automatically.

Anyway, it makes it easier to add a plug-in to do the reconnection automatically. It can simply test for the A/P going off.

Also, in my FSUIPC options and settings, I only have the about tab, and logging tab. Is this supposed to happen?About the plug-in, I would really appreciate if you could make such plug-in for me, as long as it doesn't take too much of your time.

Oh dear. If you don't have an FSUIPC registration then you can't do key/button assignments, nor will plug-ins work. These are parts of the wide number of FSUIPC features you get after purchase. I'm sorry, but I can't offer such support for an unpurchased FSUIPC. It rather defeats the object of such provisions.

Regards

Pete

[jetboy23]

It is using the FS autopilot, then, so it shouldn't even need to disconnect the controls as FS does that automatically.

Anyway, it makes it easier to add a plug-in to do the reconnection automatically. It can simply test for the A/P going off.

Oh dear. If you don't have an FSUIPC registration then you can't do key/button assignments, nor will plug-ins work. These are parts of the wide number of FSUIPC features you get after purchase. I'm sorry, but I can't offer such support for an unpurchased FSUIPC. It rather defeats the object of such provisions.

Regards

Pete

Hmmmm, alright then. So I should register then??????

[Pete Dowson]

Hmmmm, alright then. So I should register then??????

Well, if you think it is worth it. Best review the User Guide, make sure you think it is worth the cost for you first.

If you do, get back and we'll sort out the plug-in fix for you.

Regards

Pete