veldthui

Everything was working fine until I upgraded to P3D V3.1. I have a Saitek Yoke and throttle quadrant. I use FSUIPC for the axis's and Linda for the buttons. I have set up the button at the bottom of the throttle lever to DECR thrust on select and same for repeat. On release sets the throttle to 0. This was working fine. Since 3.1 it works until the release and it sets the throttle to zero but then pulls the reversers back again. Move the lever down and back and same thing over and over. Can't keep it out of the reverser. I deleted the assignments and it stopped. Could not figure out how to stop it so removed them out of Linda and put the exact same thing into FSUIPC and that works fine.

Did you install the latest ORBX libraries? This fixes some elevation issues in some places.

Get the latest ORBX libraries and install those. I found that doing that fixed all my issues with scenery. I too was running OBRX global and Vector.

Okay, I have Linda set to start up via the FSUIPC runif command. This was working perfectly fine at 4Ghz with no error messages from anything. I then increased the CPU to 4.2Ghz and now when P3D starts up and FSUIPC runs the runif to start Linda, then Linda pops up an error message stating that another program has the fsuipc.ini file open. I then have to find the error message (usually hidden behind the P3D window by now) and click the okay button. Linda is still running at this point and it does not seem to affect it so not sure what the error message is about. Starting Linda manually later is messy because it means minimising windows, starting Linda, then restoring the windows. Much nicer if it is done automatically.

Oh it is running. However as it starts up it pops up the error message saying it can't open the fsuipc.ini. I then have to find the window and click okay to get rid of the error message and then refocus on P3D. Starting Linda after is also messy but I don't get the error message. It was all fine before I increased the CPU to 4.2Ghz.

Had Linda working perfectly and PC running at 4Ghz. Bumped it up to 4.2Ghz and now getting a message when starting P3D that Linda cannot open fsuipc4.ini because it is being used by another program. The run command for it is in the fsuipc4.ini. Anyone else come across this or a way to fix it. Currently I have disabled it and am starting it manually after P3D boots up.

I find intersections are too short to take off from. I always use runways. :Kiss:

I have all my axis and buttons through FSUIPC and have no issues. I do not use any of axis for trim. I use the button repeat on one of the yoke buttons. Currently all axis processed by FSUIPC and use them for throttles, yoke, brakes, spoilers, flaps.

It is the weather injection most likely. Best way to fix it is use DCW option. I found this with ASX.

The XPDR usually has its own altimeter and is always set to to standard so that they all give the same altitude regardless of what QNH is set for. This avoids pilots setting incorrect QNH and the XPDR then sending wrong altitude data.

I dont use the Saitek stuff at all. I run everything through FSUIPC and dont have any issues with it at all. I process the axis through it especially with the throttles as each lever gives different results for the same position. I use FSUIPC to make sure they stay in sync.Having said that some report having problems. All you can do is try it. If it works okay, if it doesn't revert back quite easily. The joys of FSUIPC.

Ah that is what I mean. Thanks.

Strange. It seemed to work when I did the Tutorial#2. Certainly could tune it and the transfer button worked from the radio stack itself. This is with the latest service pack. Will have to go back and see again.I also noticed that the Transponder did not seem to change using the MCP Combo2. I guess it is an issue with it as there is nothing mapped to it in Linda.

Tried Tutorial#2 yesterday and found that while I could set the ADF1 with my VRInsight Combo2 and I could select the ADF2 I found that any changes to ADF2 did not make any changes in the actual ADF2. Also the transfer button for the ADF did not work.Is this a known issue? Can it be fixed?Thanks.

It does if the yoke was overpowering the AP and disconnecting it. If recalibrating the yoke solved his problem then you can be almost certain that it was his issue.