Nieuport 28 throttle problem

[Hot_Rod]

I’m curious if anyone else is experiencing this.

 

While trying out the new Nieuport 28, I came across an issue where the engine speed will become stuck, repeatedly cycling between ignition mode position 4 and 3 (which means that the engine will be constantly switching between full speed and 3/4 speed every 3 - 5 seconds).

 

For those who may not be aware, the Nieuport doesn’t have a throttle, rather the engine speed is controlled by a 4 position ignition mode switch - located on the left side wall of the cockpit - which is controlled by your throttle input device.

 

Once this cycling begins, there doesn’t seem to be any way to make it stop.  The “blip” switch has the normal effect on the engine, but as soon as the blip switch is released, the cycling will start back up.

 

Pushing the throttle fully forward will put the engine into position 4 for as long as the throttle is kept fully forward - however, if the throttle is reduced (even fully), the cycling will start back up again.

 

I’ve found this issue very easy to replicate in flight - just move the throttle so that you are in ignition mode position 3.  Fly along for about 1 minute, and suddenly the engine will start cycling between positions 3 and 4 (the engine will sound like it’s being blipped).

 

I have found that if you can land the plane (relying heavily on the blip switch) - once the plane stops rolling, the throttle will be functioning properly again!

 

This has been in single player (I’m not a multiplayer user) - QMB (Arras and Bodenplatte maps).

Engine mixture settings (manual or automatic) had no effect on this issue.

I’ve also tried using different throttle devices (two different joysticks), as well as using the “-“ and “=“ buttons for speed control, but again these made no difference.

 

I have submitted a bug report on this issue - but again, I’m curious if anyone else is experiencing this as well.

[Cynic_Al]

What you're describing is the way the sequencer switch would have to be used in reality.  If it were left in any intermediate position for too long, the accumulation of unburned fuel in the cowl would be at increasing risk of ingnition by flames from the exhaust ports.  Therefore to avoid the risk of cowl fire, it would be necessary to switch regularly to full ignition.  I suspect the action seen in-game to be deliberate and likely to be confirmed in due course.

[Todt_Von_Oben]

 

 

(I'm using a CH Fighterstick; the throttle is a thumb wheel to which I've added a push-pull cable and knob; as in my 1946 Luscombe 8E.)

 

Different throttle settings seem to produce three distinct power settings for the N28: seems like IDLE, HALF, and FULL POWER.  

 

But when I cut back to idle and use the joystick's starter button as a blip switch during short-final approach to landing; it'll be idling and then give a surge of power; forcing me to kill the mill and land deadstick!    

 

If I leave it off too long during the rollout (maybe five seconds or so) the starter button won't get her running again.  

 

And when I try shorter off-periods: she roars back to full power and I have to squelch it again!  

 

Makes landings interesting.  I like to control power during the rollout and that's harder to do with this runaway engine thing going on.

 

I've never actually flown a rotary engine airplane and for all I know the fault here could be mine; but that's what I'm experiencing when landing the N28.

 

 

 

 

 

 

 

 

 

 

[Cynic_Al]

2 hours ago, Todt_Von_Oben said:

Different throttle settings seem to produce three distinct power settings for the N28: seems like IDLE, HALF, and FULL POWER.  

 

 

The settings are : 1/1, 1/2, 1/4 and 1/8

 

2 hours ago, Todt_Von_Oben said:

But when I cut back to idle and use the joystick's starter button as a blip switch during short-final approach to landing; it'll be idling and then give a surge of power; forcing me to kill the mill and land deadstick!    

.

As previously explained, such action (on the part of the pilot) would be needed to prevent an accumulation of unburned fuel in the cowl.

 

 

2 hours ago, Todt_Von_Oben said:

If I leave it off too long during the rollout (maybe five seconds or so) the starter button won't get her running again.  

 

That's a simulation of spark plug fouling.

 

 

 

[hsthhsth]

I still find the Requiem videos for ROF very informative on flying these FC planes. =IRFC= Requiem - YouTube

 

I know that FC (IL-2) has a newer engine as ROF but I learned for example about landing the Nieuport 28.

[Hot_Rod]

20 hours ago, Cynic_Al said:

 

What you're describing is the way the sequencer switch would have to be used in reality.  If it were left in any intermediate position for too long, the accumulation of unburned fuel in the cowl would be at increasing risk of ingnition by flames from the exhaust ports.  Therefore to avoid the risk of cowl fire, it would be necessary to switch regularly to full ignition.  I suspect the action seen in-game to be deliberate and likely to be confirmed in due course.

 

I’m thinking that you may be correct regarding the cause of the engine speed cycling.

I’ve found that even idling while on the ground will initiate the engine cycling between positions 3 & 4.

It seems that the best way to avoid this condition is to keep the switch in position 4 at all times while flying, and use the blip switch whenever it’s necessary to slow down (and if idling while on the ground or taxiing, I’d recommend revving the engine  up to position 4 briefly, every few seconds).

 

If the in-game engine speed cycling is a feature that the developers implemented to mimic the action a knowledgeable pilot would take (to prevent the buildup of unburned fuel under the cowl, and prevent a potential cowl fire), I’d recommend that they add a cautionary note on the “Specifications” page for the Nieuport 28, advising to avoid prolonged use of lower power settings (greater than xx seconds).

 

[Cynic_Al]

As if to fly in the face of what I said previously, this Gnome-Powered Pup flew for over three minutes at half ignition with no ill effects.  Maybe the design of the cowl plays a part. 

[Jack59]

The following quote is from Andrew King, a pilot and WWI enthusiast who has flown three Gnome-powered planes and, at the time of the writing of the article in which he is quoted, was in the process of building a Nieuport 28 replica to house his own Gnome:

 

“The 160 was ‘throttled’ using an ignition interrupter. There are five positions on the switch: 4-3-2-1-0; 4 is full power and normal firing order 1-3-5-7-9-2-4-6-8, and 0 is off. On position 3 every other ignition pulse is skipped, so the firing order is 1-5-9-4-8-3-7-2-6, and it takes four revolutions instead or two for all cylinders to fire—this is half speed. On position 2 it takes eight revolutions to fire all cylinders, 1 (skip 3-5-7), 9 (skip 2-4-6), 8 and so on. On position 1 it’s one eighth speed, and takes 16 revolutions to complete the firing order—it sounds like it’s running on one cylinder.”

 

It is easy for me to understand why fuel accumulates in the cowl while blipping: the ignition is completely shut off while the fuel is still on. But using the selector switch to control power still results in all the cylinders regularly firing. It's just that a given cylinder fires less or more times for a given amount of engine revolutions, depending on the switch position. I am somewhat doubtful that this would result in significant, if any, fuel accumulating in the cowl, especially on switch position 3. But I am no expert, and could be wrong.

[Cynic_Al]

13 hours ago, Jack59 said:

But using the selector switch to control power still results in all the cylinders regularly firing. It's just that a given cylinder fires less or more times for a given amount of engine revolutions, depending on the switch position. I am somewhat doubtful that this would result in significant, if any, fuel accumulating in the cowl, especially on switch position 3.

 

To take the example of position 3, each cylinder misses one beat, so half the mixture being delivered to each cylinder fails to burn, resulting in it being expelled into the cowled area.  There may be several factors determining the risk igniting un-burned fuel mixture within the cowl.

[unreasonable]

Not an expert either, so this is all just a thought experiment, please correct! 

 

Danger = fuel build up in cowl = fuel loss into cowl - fuel escape from cowl.

 

I see no reason why the fuel loss per unburnt cylinder cycle should be any different between different ways of suppressing the ignition.

 

When you run the engine at a lower setting than 4 you will (usually) be at a reduced rpm in level flight. So the quantity of unburnt fuel loss per time unit will be roughly proportional to the rpm times the proportion of cylinders that are not firing on each cycle. So at setting 3, you will usually have about 3/4 of full rpm, with 1/2 of cylinders unburnt per cycle, ie 3/8 of the fuel loss compared to blipping for the same amount of time at full rpm.

 

Fuel escape from cowl may not be rpm related, or at least not entirely, but perhaps speed related?  If it is a more constant quantity than the fuel loss, then we would have a pronounced gearing effect: so it might be the case that there was no build up at all at the lower settings.   

 

 

[Dragon1-1]

IMO, that should not be automated. If you blip/cut throttle for too long, you get a fire in the cowling, simple as that. Let the player make sure this doesn't happen, not introduce another silly automated system that we can't control manually. TBH, automatic switching of anything shouldn't be a thing, unless it was so historically.

Edited May 17, 2021 by Dragon1-1

[Chief_Mouser]

2 hours ago, Dragon1-1 said:

TBH, automatic switching of anything shouldn't be a thing, unless it was so historically.

 

Especially fuel gauges. How annoying that is!

[Jack59]

I remain convinced that that this engine/throttle behavior is a bug.

 

I recently received a copy of "Nieuport 28: America's First Fighter" by Theodore Hamady. It includes an appendix which is a description of the the Nieuport 28's airframe and propulsion system "derived from contemporary US Air Service and Royal Air Force documents", translated from the original French materials. Included is a section where the writer cautions the pilot not to use thinning of the mixture to control engine speed, as this can lead to piston and cylinder burn. Incorporated in this section is the following quote (Italics are mine): "Always set the throttle lever for the best possible mixture; that is, the mixture which will give highest possible speed at the altitude and under the weather conditions in which you are flying. To reduce the speed, use the selector switch; and do not hesitate to run for long periods with the selector switch in operation and the engine missing regularly".

 

So the official documents encourage running for long periods on switch positions less that 4. Accordingly, I find it hard to believe that it was in fact an engine fire risk. From what I've read, the two very real engine fire risks for the N28 were extended blipping and fuel line leaks caused by improper annealing of the copper lines.

[Dragon1-1]

Extended blipping was trouble for any rotary without a great big hole in the bottom of the cowling. Running on the lowest setting for a long time could probably be trouble, but 3 should be OK indefinitely, there really wouldn't be that much fuel wasted in this case.

 

3 hours ago, 216th_Cat said:

Especially fuel gauges. How annoying that is!

I'd really love to have that on a button. There's even a button for switching fuel gauges in Tank Crew. I have no idea why we don't have that for planes.

[Chief_Mouser]

10 minutes ago, Dragon1-1 said:

Extended blipping was trouble for any rotary without a great big hole in the bottom of the cowling. Running on the lowest setting for a long time could probably be trouble, but 3 should be OK indefinitely, there really wouldn't be that much fuel wasted in this case.

 

I'd really love to have that on a button. There's even a button for switching fuel gauges in Tank Crew. I have no idea why we don't have that for planes.

 

The fuel management system is being worked on, thank goodness. No timeframe but we have to hope that it's coming along with droptanks for BoN. So we should be able to choose which tanks to use and which to display. Fingers crossed! ?

[unreasonable]

I

Just now, Jack59 said:

I remain convinced that that this engine/throttle behavior is a bug.

 

I recently received a copy of "Nieuport 28: America's First Fighter" by Theodore Hamady. It includes an appendix which is a description of the the Nieuport 28's airframe and propulsion system "derived from contemporary US Air Service and Royal Air Force documents", translated from the original French materials. Included is a section where the writer cautions the pilot not to use thinning of the mixture to control engine speed, as this can lead to piston and cylinder burn. Incorporated in this section is the following quote (Italics are mine): "Always set the throttle lever for the best possible mixture; that is, the mixture which will give highest possible speed at the altitude and under the weather conditions in which you are flying. To reduce the speed, use the selector switch; and do not hesitate to run for long periods with the selector switch in operation and the engine missing regularly".

 

So the official documents encourage running for long periods on switch positions less that 4. Accordingly, I find it hard to believe that it was in fact an engine fire risk. From what I've read, the two very real engine fire risks for the N28 were extended blipping and fuel line leaks caused by improper annealing of the copper lines.

 

Good find, and I believe convincing evidence. I am also convinced that what we are seeing is a bug, possibly two.

 

Evidence:

 

1) The setting can jump down up as well as down. Flying for a few minutes at 3, the setting moved to 2 without my moving the HOTAS throttle. This is not consistent with there being some AI intervention to reduce unburnt fuel flow.

 

2) After removing the game throttle control mapping to HOTAS throttle completely, I flew again using - and = for throttle back and forwards inputs.  At no time did the game throttle setting jump without input. This included running the engine for a few minutes on the ground at the lowest setting.

 

So I suspect that what we are seeing with the player plane is axis throttle spiking up and down - I get that occasionally in the game with aircraft with normal throttle control, which can be irritating if you are trying to stick close to an engine limit. In this case a change when you are close to one of the boundaries would have very obvious consequences. Whether this is entirely due to my horrible old HOTAS or also implicates the game I do not know.

 

The AI could cycle rapidly too. This is a bug in the sense of being an unintended consequence of having the AI target outputs - here speed - rather than inputs. The only way to slow down is to blip or reduce setting: if the mission plan requires a speed not identical to the outcome of having a settings 2-3-4 at their altitude, they will constantly be cycling between the settings as they overshoot and then undershoot the required speed. [edited for clarity].

 

Edited May 17, 2021 by unreasonable

[Dragon1-1]

3 hours ago, unreasonable said:

2) After removing the game throttle control mapping to HOTAS throttle completely, I flew again using - and = for throttle back and forwards inputs.  At no time did the game throttle setting jump without input. This included running the engine for a few minutes on the ground at the lowest setting.

This indicates a "bug" in your HOTAS. If your throttle axis is spiking, then it might be time for a replacement pot.  

 

I don't have FC2, so I can't check. However, this tests suggests either a bug in axis handling, or a hardware issue. Given that other people have experienced this, I'd lean towards the former, but it might be that it doesn't respond well to worn-out throttle pots.

Edited May 17, 2021 by Dragon1-1

[Hot_Rod]

8 hours ago, unreasonable said:

2) After removing the game throttle control mapping to HOTAS throttle completely, I flew again using - and = for throttle back and forwards inputs.  At no time did the game throttle setting jump without input. This included running the engine for a few minutes on the ground at the lowest setting.

 

So I suspect that what we are seeing with the player plane is axis throttle spiking up and down - I get that occasionally in the game with aircraft with normal throttle control, which can be irritating if you are trying to stick close to an engine limit. In this case a change when you are close to one of the boundaries would have very obvious consequences. Whether this is entirely due to my horrible old HOTAS or also implicates the game I do not know.

Hi unreasonable;  I’ve conducted that same test a couple of times (removing the HOTAS throttle from the key mapping and having only the “-“ and “=“ keys assigned for throttle control), and had very different results.

 

Each time, after idling for just over 2 minutes - and not touching the throttle keys at all - the engine went briefly up to position 2, and then started cycling between positions 3 and 4.  I hit the “blip” button, and the engine returned to idle (for over 5 minutes).

I then abvanced the throttle to position 4 and took off.  After gaining a couple hundred feet of altitude, I moved the throttle to position 3, and 40 seconds later the engine started cycling between positions 3 and 4.

 

I then ran the same test using the throttle axis on a Logitech Extreme 3D Pro - and then using a Thrustmaster T16000M.

In each case the results were virtually identical (the engine speed started cycling after 2 minutes of idling - without any throttle movement. 
And then after taking off and placing the throttle in position 3, the engine started cycling after about 40 seconds.

 

I can’t explain your results - but based on the results of my tests, I don’t see how this condition can be attributed to throttle axis spiking.

[Hot_Rod]

11 hours ago, Jack59 said:

I recently received a copy of "Nieuport 28: America's First Fighter" by Theodore Hamady. It includes an appendix which is a description of the the Nieuport 28's airframe and propulsion system "derived from contemporary US Air Service and Royal Air Force documents", translated from the original French materials. Included is a section where the writer cautions the pilot not to use thinning of the mixture to control engine speed, as this can lead to piston and cylinder burn. Incorporated in this section is the following quote (Italics are mine): "Always set the throttle lever for the best possible mixture; that is, the mixture which will give highest possible speed at the altitude and under the weather conditions in which you are flying. To reduce the speed, use the selector switch; and do not hesitate to run for long periods with the selector switch in operation and the engine missing regularly".

 

So the official documents encourage running for long periods on switch positions less that 4. Accordingly, I find it hard to believe that it was in fact an engine fire risk. From what I've read, the two very real engine fire risks for the N28 were extended blipping and fuel line leaks caused by improper annealing of the copper lines.

I hope you won’t mind, but I quoted your post in the bug report I made on this issue.

 

Thank you for sharing this.

 

 

Rod

[unreasonable]

2 hours ago, Hot_Rod said:

Hi unreasonable;  I’ve conducted that same test a couple of times (removing the HOTAS throttle from the key mapping and having only the “-“ and “=“ keys assigned for throttle control), and had very different results.

 

Each time, after idling for just over 2 minutes - and not touching the throttle keys at all - the engine went briefly up to position 2, and then started cycling between positions 3 and 4.  I hit the “blip” button, and the engine returned to idle (for over 5 minutes).

I then abvanced the throttle to position 4 and took off.  After gaining a couple hundred feet of altitude, I moved the throttle to position 3, and 40 seconds later the engine started cycling between positions 3 and 4.

 

I then ran the same test using the throttle axis on a Logitech Extreme 3D Pro - and then using a Thrustmaster T16000M.

In each case the results were virtually identical (the engine speed started cycling after 2 minutes of idling - without any throttle movement. 
And then after taking off and placing the throttle in position 3, the engine started cycling after about 40 seconds.

 

I can’t explain your results - but based on the results of my tests, I don’t see how this condition can be attributed to throttle axis spiking.

 

Hi - I do not doubt you are seeing what you are seeing: but I have just run the N28 on the ground for 15 minutes with the throttle HOTAS setting disabled. 5 min on 1, 5 on 2, 5 on 3. The only changes in setting were when I pressed the = to increase at the five minute intervals.

 

Can you tell me exactly what map, season and wind settings you were using? Also any helpers enabled in Realism settings? Mixture position? Warmed up engine? Just in case any of these could have made a difference, which seems unlikely but you never know.

Edited May 18, 2021 by unreasonable

[Hot_Rod]

Here are some screenshots showing my game settings.

 

I just ran a test with “Engine Warmed up” unchecked, and I was able to idle (on the ground) for over 6 minutes without the throttle speeding up and cycling.  I then took off, climbed up a couple hundred feet, leveled off and put the throttle in position 3 (I had disabled my HOTAS throttle, and was using the “-“ and “=“ buttons for throttle control).  35 seconds after going to position 3, the engine started cycling between positions 3 and 4.

 

I had noticed in my previous tests that if I idled on the ground until the engine started cycling (this was with “Engine Warmed Up” checked), and then took off and put the engine in position 3 after gaining some altitude, that the engine would start cycling after about 40 seconds - whereas if I took of immediately (gained some altitude, put the engine in position 3), that it would take a bit longer (about 50+ seconds) before the engine started cycling.

 

I’m thinking this situation may have something to do with engine temperature + engine speed (positions 1, 2 or 3).

[unreasonable]

Similar map and weather settings as mine.  Untick "Throttle auto-limit", "Engine auto-control" and "Radiator assist" and have another go with -/= and your stick throttle. 

 

I have none of those ticked: I would put money on one or more of these taking over at some point and causing the switching, when it is not due to horrible old HOTAS, that is, which is my problem. From your product badges I would say that you have been around sims long enough not to need these any more! (I do have engine warmed up ticked - just saves a bit of time, but should have no effect on this issue).

 

 

Edited May 18, 2021 by unreasonable

[Jack59]

10 hours ago, Hot_Rod said:

I hope you won’t mind, but I quoted your post in the bug report I made on this issue.

 

Thank you for sharing this.

 

 

Rod

 No problem at all Rod! I'm glad it could be of help.

[Cynic_Al]

2 hours ago, unreasonable said:

Similar map and weather settings as mine.  Untick "Throttle auto-limit", "Engine auto-control" and "Radiator assist" and have another go with -/= and your stick throttle. 

 

I have none of those ticked: I would put money on one or more of these taking over at some point and causing the switching, when it is not due to horrible old HOTAS, that is, which is my problem. From your product badges I would say that you have been around sims long enough not to need these any more! (I do have engine warmed up ticked - just saves a bit of time, but should have no effect on this issue).

 

 

 

In RoF you get the same cycling effect if "Cruise Control" is enabled, so under IL2 perhaps it's "Engine Auto Control" that does it.  It's easy to forget about offline players; I wonder if anyone has experienced it in multiplayer.

[Hot_Rod]

Hey @unreasonable and @Cynic_Al,

 

It looks you are on to something there.  After posting my settings on my bug report thread, @-DED-Rapidus responded with this:

2 hours ago, -DED-Rapidus said:

@Hot_Rod, switchoff "Engine auto control" and/or "Radiator assist" please.

 

I haven’t had the opportunity to test this yet (I will soon), but I’m thinking this may do the trick.

 

I’ll post back later, after I do some testing.

[Hot_Rod]

And the winner is..(ding, ding, ding, ding):

Untick “Throttle Auto Limit”!

 

I unticked “Engine Auto Control”, and then also “Radiator Assist”, but both times the engine speed cycling started up as usual.

 

I reticked those two, and unticked “Throttle Auto Limit”, and was able to fly around for over 20 minutes in engine position 3 with no issues at all (I also have my HOTAS throttle enabled).

The plane now behaves the way I would expect it to (no unexpected throttle speed cycling).

 

Hopefully this will also work for anyone else who is experiencing this issue (and I see no reason why it shouldn’t).

 

 

Rod

[Hot_Rod]

6 hours ago, -DED-Rapidus said:

@Hot_Rod, watch the engine temperature, the automatic assistant specifically switched the engine to position 4 to "warm up" the engine, rotatives are very "cold" engines.

I thought I’d post this here as well - this explains why the engine speed cycling was occurring, and the advice to watch the engine temperature would be useful to anyone who disables the “Throttle Auto Limit” to resolve the engine speed cycling issue.

 

 

Rod

[SquashmanMikeEH]

Since the last update, has anyone else found that the Nieuport throttle sticks full open on landing and can not be reduced? 

This makes landing the 28.C1 almost impossible 

 

EDIT - Sorry gentlemen - I posted this in the last update thread (moved by Devs), not realizing it was already a topic

Edited May 21, 2021 by SquashmanMikeEH

[Hot_Rod]

Hi SquashmanMikeEH,

 

Check your realism settings - if you’re using “custom” settings, and “Throttle Auto Limit” is checked (far right hand side and circled in the screenshot below) - uncheck it, and that should fix it for you (it did for me anyway).

 

Or, if you’re using the “Normal” realism setting, select the “Custom” setting and uncheck “Throttle Auto Limit” (the “Normal” realism setting apparently has  the “Throttle Auto Limit” enabled).

 

If your issue is the same as the issue I was having - and I believe it is - when you reduce throttle (as you would to land), typically within about 40 to 50 seconds, the “Throttle Auto Limit” feature will automatically increase the throttle settings to prevent an engine “overcooled” condition (which can damage the engine).  

 

I hope this helps.

 

 

Rod

Edited May 20, 2021 by Hot_Rod
Added information about “Normal” realism settings

[Todt_Von_Oben]

POWER:

Confirmed.  I unchecked all the automatic engine function boxes and now the throttle works acceptably.  

 

TRIM:

Not only is the FC N28 tail-heavy, it requires the same amount of corrective trim on my CH Fighterstick as the Dr.1 does: not just a notch or two, but a full 1/8 rotation of the trim wheel.  That's a lot.

 

I want to say I think the Devs should modify the N28 and Dr.1 FM by pitching them down by a significant percentage (so users without trim-adjustable sticks can enjoy flying them, too) but I'm worried what else in the sim that might affect.

 

Both do fly nicely with the CH Fighterstick and Pro Pedals, though.

Edited May 20, 2021 by Todt_Von_Oben

[Cynic_Al]

21 hours ago, SquashmanMikeEH said:

Since the last update, has anyone else found that the Nieuports' throttle sticks full open on landing and can not be reduced? 

This makes landing the 28.C1 impossible 

 

Can you confirm you do not experience this effect in multiplayer?

[Todt_Von_Oben]

I flew one today in QM and Flugpark; with those "automatic engine" features unchecked it's as Hot Rod says; worked for me, anyway.

 

As a fighter, I found her unimpressive; had to work really hard to get anything out of her.  

 

Hard to get the advantage on a DVa in a constant-altitude turn; yo-yo's take up too much sky.  I mean, you can do 'em but if I was up against a man (instead of a bot) in just about any German plane. I don't think he'd have much trouble avoiding me as I claw my way up into a firing solution.

 

The fuel mixture at Flugpark was new to me; figured it out on the fly.  Looks backwards from the Dr.1.   i set it for what looked good at idle; took off; and re-mixed at full power in level flight for best RPM.  Then I did touch-and-goes and full-stop landings carrying 40% fuel and no modifications. 

 

The throttle is operating normally in all four positions now that I have those "automatic" features unchecked.  

 

She takes off and lands without any surprises; pretty tame, actually.  You can be really casual and still look good.  I was three-pointing with the engine in "putt-putt" mode; on the fast taxi portion of a landing roll-out, a brief touch of the the third power setting (coupled with appropriate rudder and aileron) kept me going straight as I slowed down under control.  

 

I really had to be clumsy to drag a wingtip but it's doable.  Don't do that.  That's where the ailerons are.  

 

I think the throttle problem is solved.  If you can find a way to solve the trim problem, and you understand Langewiesche, the present FC Nieuport 28C is one of the nicest, most forgiving, easiest-to-fly planes you'll probably get killed in.

 

Prosit!

[SquashmanMikeEH]

20 hours ago, Cynic_Al said:

 

Can you confirm you do not experience this effect in multiplayer?

 

Sorry - I posted this in the last update thread - it must have been moved here by the developers.

Looks like the problem has been given a lot of consideration here.

[Cynic_Al]

4 hours ago, SquashmanMikeEH said:

Looks like the problem has been given a lot of consideration here.

 

It wasn't a problem, just a misunderstanding regarding a long-standing setting that many of us would never have met.

[SquashmanMikeEH]

15 hours ago, Cynic_Al said:

 

It wasn't a problem, just a misunderstanding regarding a long-standing setting that many of us would never have met.

 

 

Sure thing ?