FSUIPC throttle issue Honeycomb Bravo only with FSS Aircraft

[Flusi2004]

Hi, 

I have been using FSUIPC since the beginning, but I can't solve this problem. FSUIPC doesn't work with the throttle axis of the FSS planes in MSFS (Embraer 170, B 727 Super). All other AC works fine and also the MSFS axis assignment works,  all throttle axis are recognised. But the throttle axis (no movement).of the FSS planes doesn't work with FSUIPC 7. I have tried serveral settings and calibrations, but no success.

Thanks for help. 

Klaus

Test 727 FSUIPC7.log FSUIPC7.JoyScan.csv

[John Dowson]

How have you assigned the throttle axis? Which controls have you tried? e.g. have you tried the *_EX1 throttle controls?

If assigning using 'Send direct to FSUIPC calibration' doesn't work, switch to using  'Send to FS as normal axis' and try the various throttle controls there. Best to remove any calibration when trying this, at least until you find an axes control that works. If you find one that works, you can then try to see if this can be calibrated.

You can also try logging  Axes Controls, move the throttle in the VC, and see what control is logged. You can then try that assignment, but there is still no guarantee that this will work.

You can also try setting logging for Input Events and move the throttle, to see if any Input Events are logged. If so, I can how you how to assign an axis to control an Input Event.

Also list the available lvars - do any of them look like they control the throttle? If so, there are various methods that you can use to assign an axis to control an lvar.

Finally, if the standard controls don't work when assigned outside of MSFS, it may be possible to define a preset to control the throttle.
I can also help with this, but I need to know what control is logged when you move the throttle in the VC (with logging for Axes Controls set in FSUIPC).

I don't have any FSS aircraft, so cannot look into this here. Try the above and report back what you find (attaching any relevant log files) and I can possibly help further.

John

[John Dowson]

Also, check the EFB to see if there is a throttle calibration page - you may need to configure there first...

[Flusi2004]

Hi John,

thanks for the quick reply. I have tried all axis settings : direct FSUIPC, MSFS throttle, MSFS throttle ex1  etc. but the same issue. Throttle lever in the VC doesn't move but I hear  the 

upspooling engine for a millisecond and then the engine goes in idle again. I disable all MSFS axis with an emty profile, same issue. I create an emty FSUIPC ini, but same issue. Only if

I assign the axis with MSFS settings all works fine. Sure, I can always change my profile in MSFS if I want to fly  FSS AC, but I love FSUIPC, because FSUIPC change his profile automatically.

The logfile is the last try with an emty FSUIPC ini.

Thanks for help again.

Klaus

FSUIPC7.ini LOG.zip

[John Dowson]

Your log shows many Throttle 1/2/3 Set controls logged, but for some reason this is using 2 parameters and both are 0. Very strange as these controls only take one parameter...

Can you please re-read my earlier posts carefully and look into what I have advised. Namely:
   - check the EFB throttle configuration
   - log Input Events (also list them) and see if any are applicable
   - list the lvars to see if any of them look applicable

The log file you attached shows no lvars or input events.

Also, please remove any throttle assignments (and calibration) you currently have and just move the throttle in the VC (i.e. using the mouse) for the time being.

John

[Flusi2004]

Sorry, although I have been using FSUIPC since FS98 I am not a profi, but I have done "my very best" ;). The  B727  Super doesn't have a calibration option in the EFB, for this time I used the mouse to move the throttles in the VC, here the result.

Klaus

FSUIPC7.log

[John Dowson]

Please attach files only, not screenshors (unless specifically requested). The lvars are not listed in the log you provided. Please show me a log file that lists the lvars.

However, your log does show some input events that may be of interest:

Quote

     5078 InputEvent found: 'ENGINE_Throttle_1' with hash=5200770593375785755 [type=0]
     5078 InputEvent found: 'ENGINE_Throttle_Reverser_1' with hash=16985579028055341929 [type=0]
     5078 InputEvent found: 'ENGINE_Throttle_2' with hash=10321682380435769518 [type=0]
     5078 InputEvent found: 'ENGINE_Throttle_3' with hash=14829538403500064317 [type=0]
     5078 InputEvent found: 'ENGINE_Throttle_Reverser_3' with hash=7951428358750099023 [type=0]

Not sure there is no ENGINE_Throttle_Reverser_2 though....

Looking at the log of the ENGINE_Throttle_1/2/3 input events, it seems that these take a value between 0 (for idle) and 100 (for full thrust).
You could try using these for your assignments. To do this, you need to assign your throttle to update an FSUIPC offset, then have a lua script that monitors this offset, calibrates the axis value to the 0-100 range, and then send this value using the appropriate Input Event.

I have just realised that I actually have the FSS 727, so I will look into this (and the lvars) and get back to you - but it may take a day or two as I am busy until Friday.

John

 

[Flusi2004]

I will wait,thanks

[John Dowson]

Just took a quick look - I have quite an old version of this aircraft (1.0.7 - latest is 1.1.3) and can't seem to update. I will try and update to the latest version - I have raised a support ticket for this an am awaiting a response.

In the meantime, I am not familiar with this aircraft. If I advance the throttles in the UI, using the mouse, they jump back to idle. Do you know why this is? Is there some sort of throttle lock that I have to disengage first?

[John Dowson]

I have assigned now to get the throttles moving, but I don't think they are actually working, i.e. no sound and no movement in the aircraft.
If you could let me know how to actually use the throttles with the mouse (so I can get the aircraft moving), this may help me...

To move the throttles, I assign your axis using 'Send to FSUIPC Offset', select Offset Dword Set and give an offset - I am using xA030, xA034 and xA038. If you use other offsets, you will need to update the lua script.

Then save the attached lua script to your FSUIPC7 installation folder (or Lua script folder if you have this set differently).
You then need to start the lua - best to have it auto-started by adding this to your ini:

Quote

[Auto.B727 Super]
1=Lua FSS-727Throttle

The script uses the input events to move the throttle lever. I have also tried adding the sending of the Throttle1/2/3_Set control to see if this is also needed (both as a standard control and via calculator code), but I still don't seem to get any thrust.
I will look into this on Friday, and after I have been able to update.

If you can provide me the info on how to use the throttles in the VC, that would be helpful. I really don't want to have to go through the documentation to learn how to move this.....!

John

FSS-727Throttle.lua

[John Dowson]

Also, when clicking to release the parking brake, I hear a clunck sound but the parking brake doesn't seem to be released....and the default key assignment ctrl +num decimal doesn't seem to work. Any ideas?

[Flusi2004]

Sorry for the late reply, I didn't want to check before friday. Yes,I can move the throttle with the mouse and also if I use the axis settings in MSFS. And yes, if I tried to move the throttle with FSUIPC I also have a noise but no movement. I have checked other foren, and found that serveral simmers have problems with the FSS AC. Some means, the reason is the copy protection if  useing a third party add on. May be, because all other AC, and I own many, works very fine with FSUIPC. And this is the main thing for me.
 

Klaus

[John Dowson]

Did you try the lua script I provided? That will move the throttles using the input events.

I have updated to the latest version of this aircraft, and the script looks to be working to control the throttles and I can now move the aircraft.
Seems to work just using the input events, so I have removed the code to also send the throttle set events in the attached lua, so please try this one.

John

FSS-727Throttle.lua

[Flusi2004]

Hi John,

I have tried many hours today. New installation of the 727 and FSUIPC, disable Win Defender, try Lua Script etc. Strange, the original 727-200 works now with the normal FSUIPC axis assignment but the 727-200 Super accepted only the assignment with MSFS axis. I'm giving up now, because all other planes works fine with FSUIPC. Any way, great support and thanks!

Klaus

[John Dowson]

What is the '727-200 Super'? I only have the 727-200F, and that works with the lua script I provided - I did not check with normal assignments.

If the Super variant has the input events ENGINE_Throttle_1/2/3, then you should be able to use that lua script. Have you tried this?

John

[Flusi2004]

FSS released 3 Boeing 727. 727F, 727-200 and 727-200 Super. The " Super" is an extension pack of the 727-200. Of course I have tried to use with the Super the same FSUIPC Profile like the normal 727-200. But doesn't work. I think, it is a problem with the FSS progamming because the ERJ 170 from FSS has the same issue.

Klaus

[John Dowson]

12 minutes ago, Flusi2004 said:

Of course I have tried to use with the Super the same FSUIPC Profile like the normal 727-200.

That is not what I asked...

I asked if the Super has the same input events (or any input events for the throttle). If so, you should try that lua I provided - maybe modified if the input events have different names.
I keep asking if you have tried this but you are not answering this question. If you want me to help you to set this up with FSUIPC, you need to try what i suggest and provide feedback.

John

[John Dowson]

I could possibly get the Super to look into the throttle, but before I do this I would like you to at least check and try what I have already said.
i.e. check the input events for the 727 super and if the throttle ones exist, try the lua I provided. Also, it would be useful if you could attach another log generated when using the 727 super, and showing the input events (i.e. activate logging for Input Events) and the lvars (i.e. list the lvars).

John

[Flusi2004]

Hi John,

you make a really great support but it is quite tiring for me because english is not my native language and I don't unterstood all your instructions. Yes, I have tested also the offset and the lua without succsess. But now the normal 727-200 works with the settings Throttle... ...ex1 . Because most of the time I fly twins, lever one of the Bravo is binding to two axes. I have tried the same FSUIPC settings for the 727 Super but that doesn't work. OK, FSS is only a early access and sure there will be updates in the future. Perhaps they will be a solution.To your interest in the attachment the last log and ini files.

Thanks again,

Klaus

FSUIPC7.ini FSUIPC7.log

[Flusi2004]

Here the log with list lvars

FSUIPC7.log

[John Dowson]

In the first log, you were using the aircraft 'Boeing B727-200 Condor | Retro | D-ABMI' - is that the 'super'? I suspect so, as this is listed under your 'Boeing 727 Super' profile.
But that log shows nothing - no lvars or input events.

The second log was for the aircraft 'Boeing 727-200RE Passenger - Cougar' - is this a 'super'? If so, it is not using your 'Boeing 727 Super' profile. That log shows lvars but no input events.
I would like to see the input events available in the 'super' version, as well as the lvars.

20 minutes ago, Flusi2004 said:

it is quite tiring for me because english is not my native language and I don't unterstood all your instructions.

I understand - but it is better to ask if you don't understand something rather than ignore it. It is difficult to get to the bottom of an issue when my questions are ignored, and I am getting no feedback from the solutions I am providing.

21 minutes ago, Flusi2004 said:

Yes, I have tested also the offset and the lua without succsess.

In what version? What was the issue? I know this works in the standard 727, so you should at least try to get it working there. Once that is working, you can then try in the 'super' version. If you have issues getting this to work in the standard version, please let me know, and attach your ini and log files.

Your latest ini shows that the lua script I provided has not even been installed into your FSUIPC7 installation folder.

John

[Flusi2004]

As I wrote in my last post after a new installation of the normal 727 it works now without lua and offset with the binding Throttle.... ex1. And of course, if I tried the 727 super the lua file was in the fsuipc folder and the correct entry in the ini. And I found out, that throttle bindings in the super moves the reverse axis.. Any way, the normal 727 works and for the 727 Super I will wait for an update from FSS. For now it is ok for me. Thanks again.

Klaus

[John Dowson]

45 minutes ago, Flusi2004 said:

As I wrote in my last post after a new installation of the normal 727 it works now without lua and offset with the binding Throttle.... ex1.

Yes, I know - but it does not work in the super version. I know that the lua + offset assignments work in the basic version of the 727. So I would like you to try to get that working (you can switch back to the _EX1 events afterwards). Once you have it working in the standard version, THEN you can see if it also works in the 'super' variant. I suspect os, bit honestly have no idea as I still have not seen what input events this aircraft is using.

48 minutes ago, Flusi2004 said:

And of course, if I tried the 727 super the lua file was in the fsuipc folder and the correct entry in the ini. And I found out, that throttle bindings in the super moves the reverse axis.

Can you please show me your log and ini for this?
As I said, it would be good if you can confirm it works in the stabdard version, as I know it does here, and then try the super variant. One step at a time....

50 minutes ago, Flusi2004 said:

Any way, the normal 727 works and for the 727 Super I will wait for an update from FSS. For now it is ok for me. Thanks again.

Well, I think that you can get this to work in one way or another. But if you do not want to try, I will consider this closed.

John