FSUIPC4 version 4.023 Issues

[BenBaron]

Hi Pete,

tried the PSS A330 in FSX with the above-mentioned version of FSUIPC and wondered why I wasn't able to move the flight controls at all. Got some strange autothrottle behaviour, too. Now, I read your post about the problems with SimConnect. Tried to remove all security/firewall stuff but wasn't able to solve the problem (if I remove FSUIPC, all controls work as supposed to do). With one of the previous version, the PSS Bus worked just fine...so what has changed and could you provide this version until a workaround was found so I can fly at least one complex aircraft in FSX :roll: ?

[Pete Dowson]

tried the PSS A330 in FSX with the above-mentioned version of FSUIPC and wondered why I wasn't able to move the flight controls at all. Got some strange autothrottle behaviour, too.

Any log for me to look at? I know of no issues with any axes in this version.

Now, I read your post about the problems with SimConnect. Tried to remove all security/firewall stuff but wasn't able to solve the problem

The only possible problems I know of with SAimconnect at present are:

1) FSUIPC cannot run at all -- no Add-Ons menu, nothing. In this case there would obviously be no effect of having it there.

2) Intercepted controls, like axes is intercpeted by a Registered install of FSUIPC for joystick calibrations, can, on a very few systems (so far) appear to be delayed, with a delay increasing from a few seconds up to 30, as has been reported. I've not managed to reproduce this on any system so far, but it has been reported to MS.

You don't say whether either of these things are happening, nor even if your FSUIPC is registered. Can you give some more information, please?

If you have registered it, have you been calibrating your controls in FSUIPC or not?

With one of the previous version, the PSS Bus worked just fine...so what has changed

The main change is that in an unregistered FSUIPC none of the axes are now intercepted by FSUIPC, so that it has no influence at all. Only if you register FSUIPC do you get an interception, but then you can still add a parameter to the INI file to stop it if your system suffers delays because of the Simconnect problems.

In other words, the change (which actually occurred in 4.02, the current official user release) is to avoid problems with axes, not to create them! ;-)

and could you provide this version until a workaround was found so I can fly at least one complex aircraft in FSX :roll: ?

The current official version is 4.02, but that will be replaced by 4.03 when I am sure there are no known problems with 4.023 etcHowever, to make any progress I need information when folks do get problems.

So, could you please tell me:

1. Is there an Add-Ons menu containing the FSUIPC entry?

2. Have you registered your copy of FSUIPC4?

If yes to those:

3. Have you been calibrating your joysticks using FSUIPC4?

4. Can I see your FSUIPC4.INI file please?

5. Can you, briefly, enable Axis logging (in the Logging tab of FSUIPC options), and use your axes a little, first with a default aircraft, and then with the PSS aircraft, seeing it not respond whilst the default one does?

If any of the files are too long to show here, ZIP then up and send to petedowson@btconnect.com.

Also, could you tell me, is this PSS aircraft actually one converted to work correctly in FSX, or just one transposed from FS9? I may need help from PSS to get to the bottom of this in any case, so have you also posted on their site -- you can point out that you have me looking too.

Regards

Pete

[BenBaron]

Wow...you are so quick in replying...incredible :D . Well, at first yes, there is an Addon Menu listing FSUIPC and no, I have not yet registered FSUIPC.

The PSS Bus is converted from FS9 and used there FSUIPC. Let me explain to you what happens.

Without FSUIPC, I am able to move ailerons and elevators as usual. Unfortunately, especially the autopilot doesn't like flying without FSUIPC.

With FSUIPC, none of these controls work. I sometimes see "spikes" of little deflection when I fight the stick but the control surfaces come back to neutral immediately. The rudder works fine, though. Autopilot and all displays work normal.

I don't know why, but with your first release for FSX I was able to use the PSS Airbus without any problems. After having upgraded to the newest one (and having deleted the old one :cry: ) I get these problems. Thanks for your help, it is really highly appreciated, Pete.

[Pete Dowson]

Wow...you are so quick in replying...incredible :D . Well, at first yes, there is an Addon Menu listing FSUIPC and no, I have not yet registered FSUIPC.

In that case the main change for you in FSUIPC, in 4.02, is that it doesn't touch the axes -- like the other controls it monitors them for logging, but it doesn't intercept them.

Before 4.02 they were being stopped in FSUIPC and then re-issued, after possibly being calibrated or re-shaped.

All that is now not invoked for unregistered users.

The PSS Bus is converted from FS9 and used there FSUIPC.

It uses FSUIPC? do you know what for? I'll be needing information from PSS then. You say it works better WITHOUT FSUIPC, so what is it using it for?

Without FSUIPC, I am able to move ailerons and elevators as usual. Unfortunately, especially the autopilot doesn't like flying without FSUIPC.

Oh, right.

But with FSUIPC you can move ailerons etc in other aircraft?

I don't know why, but with your first release for FSX I was able to use the PSS Airbus without any problems.

The very first release, 4.00, was only available for a few hours. The only two official user releases have been 4.01 and 4.02. The 4.023 you are using is an interim version.

I need the Logs in any case, please, as described. And some information really about what PSS is doing with those controls. It is presumably part of their "fly-by-wire" system, but I need to know what so I can see what'sc changed.

Could you also try with the official 4.02 release please in case it is only a side-effect of something in the streamlining I did, for better frame rates?

Oh, one more thing -- could you enable IPC Write logging as well, when you try the Airbus. I have an idea what is might be, but i need to see where they are writing.

I've also a strong feeling that, if my idea is correct, you'd actually have no such trouble if FSUIPC4 were registeredif you can send me the logs this evening so I can check, I may be able to email you a test version later tonight.

Regards

Pete

[BenBaron]

Good morning Pete,

to make it clear, only the ailerons and elevators work as supposed to without FSUIPC in FSX...with FSUIPC they seem to be stuck in the neutral position (although rudder is working fine).

Yes, this only seems to effect the PSS Bus...I am able to move the control surfaces with the standard aircraft without any problems.

Without FSUIPC I tried to fly the PSS Bus with Fly-by-Wire not working at all and with many Autopilot problems.

I have already tried it with the official version 4.02 and then applied the interim one to see if the problem still existed. So, was already existant in 4.02...

Here you have at first the normal FSUIPC log from yesterday evening:

********* FSUIPC4, Version 4.023 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

Running inside FSX

Module base=61000000

LogOptions=00000001

DebugStatus=0

969 System time = 19:59:54

1062 FLT UNC path = "C:\Dokumente und Einstellungen\Benny\Eigene Dateien\Flight Simulator X Files\"

1062 FS UNC path = "G:\Games\Flightsim\FSX\"

2344 SimConnect_Open succeeded: proceeding to initialise interface!

2344 FSUIPC Menu entry added

102781 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)

102781 G:\Games\Flightsim\FSX\FLIGHTS\OTHER\FLTSIM.FLT

102781 G:\Games\Flightsim\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

105937 System time = 20:01:39, FSX time = 20:01:30 (04:01Z)

144547 G:\Games\Flightsim\FSX\aircraft\PSS-A330-300\A333.AIR

241984 Advanced Weather Interface Enabled

254984 AppKey="Y9OI8NKWIP3R", Module="PSS-A330.gau"

301406 System time = 20:04:54, FSX time = 12:21:02 (11:21Z)

301406 *** FSUIPC log file being closed

Memory managed: 17 Allocs, 17 Freed

********* FSUIPC Log file closed ***********

Will send the other log to your mail address.

[Pete Dowson]

Without FSUIPC I tried to fly the PSS Bus with Fly-by-Wire not working at all and with many Autopilot problems.

Okay .... it sounds like the PSS depends upon FSUIPC's interception of the axis controls in order to operate the fly-by-wire. I have options in FSUIPC that allow it to disconnect the main flight controls from FS and interpret them itself.

The default unregistered behaviour in FSUIPC4 since 4.02 is to leave all the axes alone. So any attempt at fly-by-wire in the PSS aircraft, using the FSUIPC facilities, won't work.

This step in FSUIPC is, I hope, temporary, and is there simply to avoid me getting inundated with non-registered users complaining that their joystick response times were ridiculously long, due to the Simconnect security problems.

What I find puzzling still, though, is that you say that you can actually fly the Airbus without FSUIPC and without fly-by-wire? Does that mean you can turn the fly-by-wire action off? If so, then you should be able to do the same with FSUIPC installed, shouldn't you?

I'll add another INI file parameter, "AxisIntercepts" for unregistered users (only -- registered users already have the reverse control, "NoAxisIntercepts" so they can turn them off). Then you can add "AxisIntercepts=Yes" to the [General] section of the FSUIPC4.INI file in order to regain fly-by-wire.

Hopefully there will one day be a Simconnect update and I can discard all these horrible options and make it work out of the box!

Regards

Pete

[BenBaron]

I maybe described it the wrong way...I can fly but with none of the protections working and (most important thing) without autotrim. So the aircraft behaves very weird and autopilot won't work, too.

[Pete Dowson]

to make it clear, only the ailerons and elevators work as supposed to without FSUIPC in FSX...with FSUIPC they seem to be stuck in the neutral position (although rudder is working fine).

...

Will send the other log to your mail address.

Thanks.

I see what is happening. The Airbus is, indeed, using FSUIPC to disable the aileron and elevator axes, and then it reads the axis values I provide, and sends them to FS, again via FSUIPC -- with, presumably, possible modification in the middle according to the fly-by-wire needs.

Because, in the Unregistered version of FSUIPC4, the axes are not being intercepted, it can't disable them. This is why I was confused -- since it couldn't disable them, they should workbut, no! Because FSUIPC isn't intercepting the axes, the values it provides to the Airbus are zero -- they simply never get set. So the Airbus code sends a constant stream of zeros to the aileron and elevator.

This results in what you are seeing -- mostly no movement but with an occasional blip when on of the Joystick scan values gets through.

The only answer is to enable the axis intercepts, which, in an unregistered version of FSUIPC4 needs a change. I'll send you an interim version which supports an "AxisIntercepts=Yes" parameter, which you will need to add.

Regards,

Pete

[BenBaron]

Great Pete...absolutely happy that you found out what is going on! Thanks again for your large effort!

[BenBaron]

Well, fired up the PSS Airbus with your modified version of FSUIPC and I am happy to report that it seems to work, now. While I wasn't able to move the control surfaces before it now works flawlessly 8) .

So great work, Pete! Thank you for your great effort in making the flightsim a better one :D .

P.S. And I want to add that this version of FSUIPC seems to cure another problem with the PSS Bus in FSX, too which I have already encountered in the early times of FS9 some years ago.

Although the A340 variant was chosen, the ECAM only showed 2 engines like the A330 was loaded. Now, with the new interim version, the ECAM showed all 4 engines correctly, again. Dunno what is going on there, but nevertheless it now works like a charm.

[Pete Dowson]

Well, fired up the PSS Airbus with your modified version of FSUIPC and I am happy to report that it seems to work, now. While I wasn't able to move the control surfaces before it now works flawlessly 8)

Good! Thanks for letting me know.

Regards

Pete