A-20, La-5 throttle problem with aids

[PaulPaulaner 1]

The throttle on the A-20 and La-5s does not work while the engine aids are activated. Game version 3.001 and 3.002.

[CastorTroy 30]

Shame this has not been fixed or even mentioned.....

[SamVimes 3]

I have this issue too. Looks to me like the problem is that the throttle movement is changing propeller pitch not the throttle.

[Pif-Paf 2]

The same here on version 3.002b. Even when I go to settings>Engine Controls> Throttle and click on the joystick mapping, the joystick is not operational. Throttle buttons (+- in my case) don't work either. It is my new plane and I was confused since I flew it the first time and got it moving only after disabling engine management. I thought I was doing something wrong but then convinced myself to check forum.

I just double checked and when engine management is on, my throttle controls are controlling prop RPM instead of the throttle. When engine management is off, throttle works properly.

Edited April 21, 2018 by =303=Pif-Paf

[4driano 41]

Hello,

 

I have the same issue with the LA-5 Series 8.

I did not try the A-20.

[56RAF_Roblex 921]

 

On 4/18/2018 at 11:21 PM, CastorTroy said:

Shame this has not been fixed or even mentioned.....

 

It was discussed when the first update was released.  You cannot set controls to allow you to manage the engine yourself if you have asked the game to manage your engine for you. There were many posts because the update reset a lot peoples game mode to 'Normal' when previously they had it set to 'Custom' to disable the engine cheats.

[CastorTroy 30]

On 5/5/2018 at 4:16 PM, 56RAF_Roblex said:

 

 

It was discussed when the first update was released.  You cannot set controls to allow you to manage the engine yourself if you have asked the game to manage your engine for you. There were many posts because the update reset a lot peoples game mode to 'Normal' when previously they had it set to 'Custom' to disable the engine cheats.

 

So the Devs are aware, and have not provided a fix yet. Hopefully they will one day.

Edited May 9, 2018 by CastorTroy

[4driano 41]

I tested it last night.

If you set the game to normal the throttle works fine.

I was using custom, the normal settings but the throttle disabled, so I could control it, but that does not work.

But with others aircrafts it works and that was the confusion.

The question is why it works with some airplanes and does not work with others.

Some kind of particularity with engine management?

[Speckfire 8]

Is there an upcoming fix for this issue?

[PaulPaulaner 1]

This issue still isn´t fixed in 3.003. :-( :-( PLEASE developers...

[Tinku74 3]

Ditto dear Devs. Would appreciate a fix to this. 

 

Thanks for this great sim!

[PaulPaulaner 1]

This issue still isn´t fixed in 3.004. 😞 😞 PLEASE developers...

[Silent01 0]

I agree still no fix

[PaulPaulaner 1]

The problem still isn´t fixed in 3.005. 😞 😞 PLEASE developers, is this such an issue?

Please don´t make the Warthunder-mistake, adding content without fixing the existing bugs.

[Speckfire 8]

Problem still lingers... Devs?? Updates?

 

[PaulPaulaner 1]

This issue still isn´t fixed in 3.006. 😞 😞 PLEASE developers...

[-=-THERION 590]

OK - I know this might be a bit annoying to you, yes. But take this "opportunity" to fly without these aides. With the techno chat

you are still able to fly your plane safe... and it's far more realistic, guys.

[peregrine7 167]

It's also pretty much set and forget in the La5.

100% throttle, RPM, mixture

Inlet 100%, 

Oil rad 100% unless freezing cold

Outlet 0% , then after take off look at oil temp and if exceeding 100 (or climbing up like it will) open then. Keep oil temp under 100 degrees.

 

Outlet may need to be opened up if on a hot map and not running the M82F engine. Note that it causes considerable drag, ~35km/h difference 0%-100%.

 

I hope the devs fix this for you, but in the meantime it's not that difficult to fly with engine management on complex.

Edited September 27, 2018 by peregrine7

[jaygee485 69]

After version 3.012 (and 3.012b) this issue persists.