Loss of controls after SU10

[Berzerker]

6 minutes ago, John Dowson said:

Ok, I will check this in the PMDG - presume you mean the 737-700? Better to specify the exact aircraft to avoid confusion. Anyway, I only have the 737-700 from PMDG, and don't have the Fenix, so will check in that.

I only tested in the 800, but I would be absolutely floored if the systems didn't work identically enough to detect issues for both products

[John Dowson]

16 minutes ago, Berzerker said:

I only tested in the 800, but I would be absolutely floored if the systems didn't work identically enough to detect issues for both products

Yes, should be the same...but you could possibly have been using the DC-6...! As I say, always better to specify the aircraft, as well as the provider.

[John Dowson]

2 hours ago, John Dowson said:

I see you are also using the A320ParkBrake.lua - is that working for you? I ask as I have had reports that this is no linger working, but have not had time to look into this yet...

Checked this now and still working fine...

[John Dowson]

54 minutes ago, John Dowson said:

1 hour ago, amicodepla said:

I tried the latest beta with C172 default. The toe brakes in my situation do not work with calibration.

I will check this as well....

Checked this and none of the toe brake assignments seem to be working with the C172. I can also check if directly updating the Brake Left/Right Position has any effect...

Id it possible to apply the toe brakes in the VC with the mouse? Would be helpful if that was possible (so that I can monitor values), but doesn't seem so...

[John Dowson]

@amicodepla

35 minutes ago, John Dowson said:

Checked this and none of the toe brake assignments seem to be working with the C172.

Sorry, made the same mistake again - had the parking brake set! The toe brakes work both when assigned to send direct to fsuipc calibration and calibrated, and also when assigned as send to fs without calibration.

There is one strange thing with your toe brake assignments:

Quote

3=CX,256,D,7,0,0,0,*-1    -{ DIRECT: LeftBrake }-
4=CY,256,D,8,0,0,0,*-1    -{ DIRECT: RightBrake }-

You are scaling with '*-1' to reverse. But, as you are assigning to FSUIPC7 calibration, you shouldn't do this - you should reverse in the calibration panel. Can you remove those '*-1' and calibrate to reverse instead and try again. Also, check that the parking brake is released!

 

[John Dowson]

@Cloud8.5 Your files show that you are using an old and unsupported version of FSUIPC7 - 7.3.6. The current released version is 7.3.8, and the latest beta with the SU10 fixes is 7.3.9h. Please update to the latest beta (available from the Announcements sub-forum) and try again, then post if you have issues.

John

[Cloud8.5]

Thx. Wilco

UPDATE:

FSUIPC Version 7.3.9h

Even here no changes. Same, same.

Used another Poti at the second BU Board (free) in/out -16383  16383. Futher it makes no difference if i gonna use the calibration or as normal axis.

Actual Logs attached.

Cheers

 

FSUIPC7.log FSUIPC7.ini

[amicodepla]

Hi John I will try it tommorrow.

[Chad P]

13 hours ago, John Dowson said:

Now I am confused....are you saying that you are not using profiles? Thats fine if you only fly one aircraft, but is really needed, especially in MSFS, if using various aircraft.

You have now set the profile aircraft name to 'FBW' - this will not catch the FBW aircraft as that string is not in the name, and so your general assignments that will be used. And as the A320ParkBrake.lua is only started in the profile, it won't be started.

Do you want to use profiles or not? I really suggest you do, if you have any intention of using any other aircraft with FSUIPC7. Decide on that, and then we can correct your FSUIPC7.ini accordingly.

John

Sorry, missed this:

I think only the Steering Set axis is exposed via SimConnect, but will check....

Hi John,

perhaps I am using profiles without knowing it 🙂

I want to have the same settings in every aircraft at the moment, I am just flying the FBW A320 and the Fenix A320. For the FBW A320 I need the LUA Script to start a flight for my VA, because I need to release the parking brake to start a flight.

The Steering Set don't work via FSUIPC.

[Chad P]

btw

the lua script for the parking brake stopped working with the latest fsuipc updates.

It wont start anymore, there is also no logging if I activte it and it's also not mentioned in the fsuipc log file.

I hadn't change anything there for the last months.

 

edit

When I reload WASM in the FSUIPC Menu it works with the brake

edit 2

The parking brake only works if I reload manually WASM after every FSUIPC start

[Cloud8.5]

8 minutes ago, Chad P said:

btw

I hadn't change anything there for the last months.

Me too!

And normally the new version of FSUIPC7 (7.3.9h) [installed yesterday] should work with the SU10, but it doesn’t. I haven't (never) changed anything in the settings. Ran hitherto as already mentioned and is known until the SU10. 
 

 

 

[amicodepla]

Hi John today I used  C172 with toe breaks, follwing your advises and the brakes work, using fsuipc's  rev calibration. The *-1 was written for problem that  I had with parking brakes 737 pmdg, but now I no longer have this problem.

[tango3000]

Hi John,

FSUIPC7 (7.3.9h) SU10

same errors as reported before

 

16469 Exception 1 "ERROR", Ref 4830, Index param 2 on TransmitClientEvent, object=1, id=65820 (THROTTLE1_SET), data=1811
    16547 Exception 1 "ERROR", Ref 4831, Index param 2 on TransmitClientEvent, object=1, id=65820 (THROTTLE1_SET), data=886
    16578 Exception 1 "ERROR", Ref 4832, Index param 2 on TransmitClientEvent, object=1, id=66420 (AXIS_THROTTLE1_SET), data=-16384
    16594 Exception 1 "ERROR", Ref 4833, Index param 2 on TransmitClientEvent, object=1, id=65820 (THROTTLE1_SET), data=461
    16625 Exception 1 "ERROR", Ref 4834, Index param 2 on TransmitClientEvent, object=1, id=66420 (AXIS_THROTTLE1_SET), data=-16186

none of the throttle move in the cockpit A320, CS777...

[Agniparvata]

Just adding to the mystery of toe-brakes, I fail to understand why the parking brakes seem to work, whereas toe-brakes do not.
And how is it that known 3rd party add-ons, which employ the brakes via SimConnect, do work without ANY changes, but FSUIPC does not, even if it is supposedly also does that by using SimConnect.

Furthermore, if John doesn't mind it, I'd have a remark on "policy".
John has repeatedly declared that he was reluctant to deal with problems during the long beta period of SU-10, although many users had already reported similar problems.
The LONG beta period was a good opportunity to find out, if the Asobo changes were INTENTIONAL or were simply BUGS.

Now it suddenly turns out that the changes are intentional, but John has not paid any attention to this over the long beta period, which lasted almost THREE MONTHS.
It is not a good practice to wait for the release version and THEN trying to find out that there are changes, changes that touch the very basic functionality - like brakes.

Now our sims, home cockpits, setups, whatever, are simply unusable due to the delay of dealing with intentional changes, that is a tiny bit unacceptable from the users point of view.
Betas are released to deal with changes BEFORE the release and that is exactly what other 3rd party developers did, and that is what the single FSUIPC developing "team" should have done.

It is way too late trying to find out solutions, now, when due to the MS policy, there is no way to turn back to the previous version, a version that everything worked fine in this regard.

Just my 2 cents, but FSUIPC7 is a popular and very useful add-on, thus it would have deserved more attention if after the release our basic functionalities remained the same, or rather we need enter another wait-cycle, when possible solutions are experimented out.
It was nothing else but a waste of time, for both parties involved. Spe3cially so, that half of the millions of MSFS users have already used the free beta for long periods.

regards

[John Dowson]

@Cloud8.5 You have you mixture1 axis assigned to 'send to FS as normal control' but have calibrated:
    Mixture1=-10130,8192,8192,16247/32
Remove that line.
I don't know why the throttle assignment is giving errors - can you try in another/default aircraft.

2 hours ago, Cloud8.5 said:

And normally the new version of FSUIPC7 (7.3.9h) [installed yesterday] should work with the SU10, but it doesn’t. 

No! That has fixed some issues, but not all - I am still working on it. However, I don't think I can do much at the moment except report these issues to Asobo and remove al calibration except when sending direct to FSUIPC calbration. Anyway, I will update and release a new beta at some point....

@Chad P

3 hours ago, Chad P said:

perhaps I am using profiles without knowing it 🙂

You were sort-of using profiles but not correctly, which is responsible for some of your issues (i.e. axes disappearing).
 

 

3 hours ago, Chad P said:

I want to have the same settings in every aircraft at the moment, I am just flying the FBW A320 and the Fenix A320. For the FBW A320 I need the LUA Script to start a flight for my VA, because I need to release the parking brake to start a flight.

If you need a lua script started just for one aircraft, then you need a profile for that aircraft.

3 hours ago, Chad P said:

The Steering Set don't work via FSUIPC.

I will check this.

2 hours ago, Chad P said:

the lua script for the parking brake stopped working with the latest fsuipc updates.

No. This was due to your dodgy ini. Please post your latest ini and I will correct it for you.

@tango3000Did you remove any calibration for axes assigned with 'send to FS as normal axis'? If not, do that and try again, otherwise please show me/attach your FSUIPC7.ini and FSUIPC7.log files.

@Agniparvata

17 minutes ago, Agniparvata said:

I fail to understand why the parking brakes seem to work, whereas toe-brakes do not.

But you said these are now working...

17 minutes ago, Agniparvata said:

And how is it that known 3rd party add-ons, which employ the brakes via SimConnect, do work without ANY changes, but FSUIPC does not, even if it is supposedly also does that by using SimConnect.

This is related to how FSUIPC can calibrate events received from the sim using event masking which seems to have broken in the SU10 update. I guess the other 3-rf party add-ins don't do this, and calibrate before sending to the sim, as FSUIPC does using the 'send direct to FSUIPC calibration', which IS still working.

I will reply to your other points in a separate comment....

John

[Agniparvata]

18 minutes ago, John Dowson said:

 to how FSUIPC can calibrate events received from the sim using event masking which seems to have broken in the SU10 update. I guess the other 3-rf party add-ins don't do this, and calibrate before sending to the sim, as FSUIPC does using the 'send direct to FSUIPC calibration', which IS still working.

I will reply to your other points in a separate comment....

 

The parking brake WORKED fine before the SU-10 release and AFTER that.
It is the toe-brakes that do not work.

Seemingly AXIS_LEFT_BRAKE_SET does not work anymore but AXIS_LEFT_BRAKE_LINEAR_SET does.

 

[John Dowson]

23 minutes ago, Agniparvata said:

Furthermore, if John doesn't mind it, I'd have a remark on "policy".
John has repeatedly declared that he was reluctant to deal with problems during the long beta period of SU-10, although many users had already reported similar problems.
The LONG beta period was a good opportunity to find out, if the Asobo changes were INTENTIONAL or were simply BUGS.

Now it suddenly turns out that the changes are intentional, but John has not paid any attention to this over the long beta period, which lasted almost THREE MONTHS.
It is not a good practice to wait for the release version and THEN trying to find out that there are changes, changes that touch the very basic functionality - like brakes.

Now our sims, home cockpits, setups, whatever, are simply unusable due to the delay of dealing with intentional changes, that is a tiny bit unacceptable from the users point of view.
Betas are released to deal with changes BEFORE the release and that is exactly what other 3rd party developers did, and that is what the single FSUIPC developing "team" should have done.

It is way too late trying to find out solutions, now, when due to the MS policy, there is no way to turn back to the previous version, a version that everything worked fine in this regard.

Just my 2 cents, but FSUIPC7 is a popular and very useful add-on, thus it would have deserved more attention if after the release our basic functionalities remained the same, or rather we need enter another wait-cycle, when possible solutions are experimented out.
It was nothing else but a waste of time, for both parties involved. Spe3cially so, that half of the millions of MSFS users have already used the free beta for long periods.

I know that I should have tested FSUIPC during the beta period, but unfortunately it was/is just not possible at the moment. I have to support the current released version of MSFS, that is the priority. I also support FSUIPC for FSX, P3Dv4 & P3Dv5 (as well as any P3Dv5 betas available, although I cannot obviously discuss this or even confirm if there is one or not). And I also support the various other free utilities and drivers that I provide.

Support, especially for MSFS. is taking up 90% of my time and is leaving little time for development, let alone anything else I have just not had the time to set-up a dual system where I can investigate the beta as well as provide support for the released version, as there are various tricks/hacks you have to perform to be able to run both systems on the same PC. And I currently just don't have the disk space to run  multiple copies of MSFS.

This is certainly something that I am planning to do, but I just need the time to look into this and re-organise my hard disks or purchase new ones. I will certainly be doing this once the SU10 issues have been resolved.

John

[Cloud8.5]

35 minutes ago, John Dowson said:

35 minutes ago, John Dowson said:

@Cloud8.5 You have you mixture1 axis assigned to 'send to FS as normal control' but have calibrated:
    Mixture1=-10130,8192,8192,16247/32
Remove that line.
I don't know why the throttle assignment is giving errors - can you try in another/default aircraft.

Wilco asap

35 minutes ago, John Dowson said:

No! That has fixed some issues, but not all - I am still worki on it. However, I don't think I can do much at the moment except report these issues to Asobo and remove al calibration except when sending direct to FSUIPC calbration. Anyway, I will update and release a new beta at some point....

ok got it

[John Dowson]

12 minutes ago, Agniparvata said:

It is the toe-brakes that do not work.

Seemingly AXIS_LEFT_BRAKE_SET does not work anymore but AXIS_LEFT_BRAKE_LINEAR_SET does.

Toe brakes are working here with AXIS_LEFT_BRAKE_SET and for other people:

3 hours ago, amicodepla said:

Hi John today I used  C172 with toe breaks, follwing your advises and the brakes work, using fsuipc's  rev calibration. The *-1 was written for problem that  I had with parking brakes 737 pmdg, but now I no longer have this problem.

AXIS_LEFT_BRAKE_LINEAR_SET is not available via simconnect (and so FSUIPC) as far as I am aware - I tried adding this but get a NAME URECOGNIZED response with this, so it was removed. How are you assigning to that event?

[Elad]

hi
@John Dowson

with clean INI Axis throttle  X set is working everything is stopped when trying calibrate

[John Dowson]

1 minute ago, Elad said:

with clean INI Axis throttle  X set is working everything is stopped when trying calibrate

Sorry, but what does this mean? If you mean that assigning using 'send to FS as normal axis' without calibrating is working, but when you calibrate it isn't, then that is the known issue - you cannot currently calibrate any axis if NOT assigned using 'send direct to FSUIPC calibration.

Otherwise, can you please supply more details and also attach your FSUIPC7.ini and FSUIPC7.log files.

John

[Elad]

6 minutes ago, John Dowson said:

Sorry, but what does this mean? If you mean that assigning using 'send to FS as normal axis' without calibrating is working, but when you calibrate it isn't, then that is the known issue - you cannot currently calibrate any axis if NOT assigned using 'send direct to FSUIPC calibration.

Otherwise, can you please supply more details and also attach your FSUIPC7.ini and FSUIPC7.log files.

John

yes this what i meant just wanna know if it known issue, thanks

 

[John Dowson]

33 minutes ago, Elad said:

yes this what i meant just wanna know if it known issue, thanks

Yes, of course it is....that is what this whole thread is about!

[John Dowson]

Could you all try the attached version please, 7.3.9i. In this version, I have prevented any axis assigned to 'send to FS as normal axis' being diverted to FSUIPC's calibration facilities.

Any issues, please supply a brief description of the issue,, specify the aircraft or aircrafts that you are using that give the issue, and attach both your FSUIPC7.ini and FSUIPC7.log files.

I would like to release an official  version today, although I doubt I will have time to completely update the documentation...

John

FSUIPC7.exe

NB. Full installer from the Announcements page also updated, but the only change is the FSUIPC7.exe posted here.

[John Dowson]

1 hour ago, John Dowson said:

AXIS_LEFT_BRAKE_LINEAR_SET is not available via simconnect (and so FSUIPC) as far as I am aware - I tried adding this but get a NAME URECOGNIZED response with this, so it was removed. How are you assigning to that event?

I have re-checked this and get the same:

Quote

     8641 Exception 7 "NAME_UNRECOGNIZED", Ref 4192, Index param 2 on MapClientEventToSimEvent for "AXIS_LEFT_BRAKE_LINEAR_SET", id=67298 [0x106E2]
     8641 Exception 7 "NAME_UNRECOGNIZED", Ref 4194, Index param 2 on MapClientEventToSimEvent for "AXIS_RIGHT_BRAKE_LINEAR_SET", id=67299 [0x106E3]

I therefore don't see how these events can be used except through MSFS assignments at the moment. I will report this to Asobo.

John