Why do airplanes start at 0% RPM lever position at start?

May 20, 2023

It is really simple imho.

Takeoff from parking - configure aircraft to take off configuration.

Takeoff from runway - aircraft should already be at take off configuraion ready to go.

May 21, 2023

I don't see how that works well with HOTAS. The second I touch my throttle, rpm lever, various engine controls the sim/PC will then read those inputs and set to those overriding preset takeoff settings.

Also the way it currently is, is the way its been for every ww2 air combat sim I've played since I was a kid.

Edited May 21, 2023 by FuriousMeow

May 21, 2023

Tempest in a tea cup, like so many other things on this forum.

May 21, 2023

I'm confused about what you guys are bitching about. I just took a P-47D-28 and did a runway start. Took it out of Pause and didn't touch any of my controls. Throttle and Boost are full back; Mixture is at Auto Rich; Prop full forward; Oil Radiator is at Neutral; Intercooler is at Full Open; Trim is at take-off position. Is that not what you want at take-off? Of course your physical controls won't be sync'd with this settings because you need to move them so the Sim knows where they are in their physical range. I always "exercise" my controls when starting a cold, hot, or air start to sync my physical controls and the Sim controls.

In answer to the question about where the Prop control would be in the parked aircraft, it would most often be in full forward, 100% rpm. That's because when you throttle down in the pattern you set the Prop full forward so that when you're flaring on a night landing and that 1,500 lb elk runs out on the runway in front of you, you can firewall the throttle and shart worrying about milking up the flaps. You don't have to think about the Prop setting.

May 21, 2023

Nuts. The programmers made it that way, just because they did, so touch your levers to make hem synch. Hard to believe it’s a two page thread.

May 21, 2023

I always do a synch with all three levers regardless when just going “live” yeah that includes not just IL2 but MSFS2020 as well. It’s never been a huge issue for me personally - not going on to three pages worth anyways - of which ironically I’m also helping it to be.

May 21, 2023

18 hours ago, SeaSerpent said:

Nuts. The programmers made it that way, just because they did, so touch your levers to make hem synch. Hard to believe it’s a two page thread.

This

May 21, 2023

On 5/8/2023 at 3:41 PM, FTC_Frederf said:

I don't know any reason why the RPM lever in all (applicable) GB planes starts at the 0% maximum coarse setting position. Why would this be done in real life? What benefit does parking the airplane and/or handing the airplane over to the pilot for start up in the maximum coarse/minimum RPM condition have?

So it doesn't over rev a cold engine? So you can set it where you want it? Don't know honestly, but seems like 0% would be good to prevent accidents, and ensure the pilot is in control when the engine actually starts.

May 21, 2023

?☠️

May 22, 2023

On 5/9/2023 at 2:41 AM, FTC_Frederf said:

I don't know any reason why the RPM lever in all (applicable) GB planes starts at the 0% maximum coarse setting position. Why would this be done in real life? What benefit does parking the airplane and/or handing the airplane over to the pilot for start up in the maximum coarse/minimum RPM condition have?

Let me explain a few reasons why this is done in real life:

Safety: By starting the engine in the maximum coarse/minimum RPM condition, it minimizes the chances of an accidental or unexpected engine surge. If the lever were initially set at a higher RPM, there would be a risk of a sudden increase in power during startup, which could be dangerous, especially if the brakes are not firmly applied.

Engine Protection: Starting the engine at a low RPM reduces the stress on various engine components. It allows the oil to circulate and lubricate the engine properly before the RPM is increased, ensuring that all moving parts are adequately lubricated and reducing wear and tear.

Control: Starting with the RPM lever at the 0% position gives the pilot greater control over the engine's initial response. This allows them to monitor the engine's behavior closely during startup and detect any anomalies or issues that may arise, such as abnormal vibrations or noises.

Standardization: Having a consistent starting procedure across different aircraft simplifies training and promotes standardization in aviation. Pilots are accustomed to the practice of starting the engine at the 0% maximum coarse setting position, making it easier for them to transition between different aircraft models.

May 22, 2023

^ This post is somewhat misleading for anyone new trying to understand how these planes usually worked. Unless you're talking about modern turborops, or T-6 Texan with its peculiar counterweight prop, none of the above is correct for pressure-carburetted warbirds with "ordinary" Hamilton Standard/Rotol CSPs, which is all Allied planes in this sim (applies to Curtiss Electrics as well). Granted, we can imagine a situation where a pilot attempts to start such an engine with throttle forward by a gross mistake (the only way to make the engine rev up to rpms where governor starts operating), but I doubt the engine would catch at all.

Take a look at any historical Handbook / Flight Manual of any combat plane with separate RPM lever simulated in this game and try to find a single case of engine startup / shutdown procedure calling for prop RPM lever back. Hint - you won't find any, at least not on Allied side.

May 23, 2023

On 5/9/2023 at 5:41 AM, FTC_Frederf said:

I don't know any reason why the RPM lever in all (applicable) GB planes starts at the 0% maximum coarse setting position. Why would this be done in real life? What benefit does parking the airplane and/or handing the airplane over to the pilot for start up in the maximum coarse/minimum RPM condition have?

Although this may have no bearing on what was reality in World War Two, I’ve flown many aircraft in real life that started in full course. Both free turbine turbo props like the King Air and piston twins and single engines.

Actually, you always start the King Air with the props in the feather range if I remember correctly. One reason was we used to operate on unprepared or remote dirt strips and when the blades were feathered (or full course) they were acting like a big paddle that would blow the dust away from the arc of the propellor before going to full fine to taxi. This reduced the wear on the propellor and reduced the risk of picking up stone chips which would greatly shorten the life of the propellor.

Also, you are leaving the aircraft in its most ‘benign’ state, that way when the next pilot starts the plane they need to take an active step to get the aircraft to move forward to taxi. It means you can’t inadvertently hit the starter and have the engine fire up and propel you forward because you haven’t got the park brake set correctly or haven’t got your feet on the brakes hard enough. It’s a safety measure.

Hope that helps,

KindRegards,

JV44Stacko

Pillar of the Community

May 25, 2023

On 5/20/2023 at 11:00 PM, czech693 said:

In answer to the question about where the Prop control would be in the parked aircraft, it would most often be in full forward, 100% rpm.

I agree.

On 5/20/2023 at 11:00 PM, czech693 said:

Of course your physical controls won't be sync'd with this settings because you need to move them

That's only true when axis controls are bound to joystick axis inputs. When you press a keyboard key or joystick button to increase-decrease a control there is no syncing anything. The concept of syncing doesn't exist in those cases. Plus there are digital controls in some airplanes like Bf 109 E1 where the propeller control is by-nature relative in reality.

On 5/20/2023 at 11:16 PM, SeaSerpent said:

Hard to believe it’s a two page thread.

You may not have an interest in improving the simulation, making it better and more authentic to reality. This excuses you from the discussion.

On 5/22/2023 at 12:02 AM, RoseWard said:

Let me explain a few reasons why this is done in real life:

Safety: By starting the engine in the maximum coarse/minimum RPM condition, it minimizes the chances of an accidental or unexpected engine surge. If the lever were initially set at a higher RPM, there would be a risk of a sudden increase in power during startup, which could be dangerous, especially if the brakes are not firmly applied.

That may be true of some aircraft, but none of the ones I have seen in IL-2 Great Battles. All of the procedures I have read for the airplanes simulated in Great Battles, which is not all of them, have the pilot advance the RPM levers to maximum prior to engine start. From what I know about typical oil-actuated constant speed propellers the engine and propeller behave identically when started with RPM lever as maximum or minimum as long as the actual RPM is below the governed RPM range.

Can you give an example of an airplane simulated in Great Battles which is started in the minimum RPM state?

May 25, 2023

Quote

You may not have an interest in improving the simulation, making it better and more authentic to reality. This excuses you from the discussion.

does it?

?

P.S. touch your stupid levers like a real pilot, and have the sim synchronize to wherever you last left your hardware. WTF am I not understanding with the concerns here?

I went off the runway in a Pe-2 once or twice because the rpm required a rocker switch, not my levers, and I’d left it at fully coarse. So I stopped doing that.

Edited May 25, 2023 by SeaSerpent

May 25, 2023

It's clear that you have no interest in making a better simulation which is more accurate to reality. This has become some kind of immature egotistical and emotional contest for you where it's more important to look down on change instead of evaluating improvements to the software objectively. It's not a good look.

May 25, 2023

Who is this making it more accurate for? Anyone that cares about accuracy has a HOTAS, and has been stated several times - the HOTAS will override the game the second the controls are touched. Anyone with keyboard and mouse that would notice this doesn't care about accuracy, they are on keyboard and mouse so their interest in aviation is middling at best.

May 25, 2023

17 hours ago, SeaSerpent said:

does it?

?

P.S. touch your stupid levers like a real pilot, and have the sim synchronize to wherever you last left your hardware. WTF am I not understanding with the concerns here?

I went off the runway in a Pe-2 once or twice because the rpm required a rocker switch, not my levers, and I’d left it at fully coarse. So I stopped doing that.

You are hereby NOT excused from this conversation mister.

May 25, 2023

It makes it more accurate for everyone, joystick or not. Not everyone has every axis-assignable control bound to a joystick axis. I personally have hundreds of dollars in flight control hardware. I am not a casual user. I still have to adjust the RPM because my RPM controls on most airplanes is bound to a joystick button. There are many, many users which use these kinds of inputs and they deserve to have the best possible experience. At worst it makes little to no difference to those who have an axis control over everything. Everything starts at its default value until synced with an axis anyway. Even the user with an axis bound will not have the correct input until the axis is moved for the first time. The discussion about joystick axes and synchronization is a complete side track. It might seem like it's related, but it's not. By initializing the airplane in an unrealistic state, nothing of value is created. By the same logic the aileron trim could be set fully right wing down at start. The user could still fix it, but why?

Please follow this thinking: It's 1944. Computerized flight sims won't be invented for many years. You walk your human pilot body and get into a real metal airplane. You look to the control levers. What do you see? That's what you should see in the computerized simulation. I don't want it easy, I want it real.

Please follow this thinking: IL-2 Great Battles already does this behavior that I describe, initializing the airplane in a realistic state. Someone comes along as asks that the simulation is changed so that RPM levers are started at 0% instead of the current 100%. Imagine the number of people chiming in that "well akshully, the levers should start at 100% realistically"? I can. By the same logic that the simulation should not be changed from accurate to inaccurate, it should not remain inaccurate.

Being told that this inaccuracy shouldn't be changed because the inaccuracy is "no bid deal to me" is very tiresome. I can only question the motivation behind such negativity.

Edited May 25, 2023 by FTC_Frederf

May 25, 2023

If you’ve found a bug in the default state of an aircraft, then you should submit a bug report in the appropriate forum section. You’ve passed the threshold at which a reasonable question regarding a minor complaint becomes nothing more than concern-trolling.

May 25, 2023

3 minutes ago, FTC_Frederf said:

"well akshully...

What were you saying above about "not a good look" ?

People have been nothing but respectful to you in this thread...and this is how you respond to them.

Pot, Kettle...all that.

May 25, 2023

Instead of engaging with the idea itself, several people have gone out of their way to argue against what I think is a good and helpful idea. I won't belabor the details. This change may have little effect for any particular user. That is fine and good for you, but is no reason that it should not be changed for the benefit of people that it will help and to objectively make a more accurate simulation. I can think of no situation in which a change as suggested detracts from the experience of any user. It only improves or makes negligible difference.

I could submit this as a bug but it's not a bug in the sense that it is clearly the developer's intended behavior as is. That didn't seem the right avenue. This is more of a request for an improved simulation, a new perspective on how to simulate the airplanes, and of course all the opportunity for someone to educate me that such and such an airplane was parked not according to how I think it was.

May 25, 2023

1) There's far more important inaccuracies or missing features that should take programming priority over this.

II) Its been this way for years, clearly it isn't impacting that many people other than the one/two vocal individuals in this topic.

c) You have hundreds of dollars in sim equipment and have the RPM on buttons rather than a lever or axis?

I have a X56 throttle and have everything worth assigning to a rotary or axis for engine management.

May 25, 2023

2 minutes ago, FTC_Frederf said:

I could submit this as a bug but it's not a bug in the sense that it is clearly the developer's intended behavior as is.

well, your attempts to convince people that it’s a significant issue are failing miserably. So it’s probably time for Plan B. Go with the bug report and move on with your life.

May 25, 2023

1. I'm sure there are.

2. I disagree. This is something which affects almost all users almost every flight. It should be improved according to whatever priority the developers decide, not you.

3. Yes, I have a Thrustmaster Warthog and I use the speed brake switch as RPM control in almost every situation. Here is my joystick script.

Spoiler

}

include "target.tmh" 
	char flagEngine1;									//Engine Control Flags
	char flagEngine2;
	char flagEngine3;
int main()
{
    Configure(&Joystick, MODE_EXCLUDED);
    
    if(Init(&EventHandle)) return 1;
	
	SetKBRate(250, 100); //PULSE, DELAY
	SetKBLayout(KB_ENG);
	
	flagEngine1=1;
	flagEngine2=1;
	MapKey(&Throttle, BSB, EXEC("flagEngine1=1; flagEngine2=0;") );
	MapKey(&Throttle, BSM, EXEC("flagEngine1=1; flagEngine2=1;") );
	MapKey(&Throttle, BSF, EXEC("flagEngine1=0; flagEngine2=1;") );
														//PILOT HEAD CONTROL
	MapKey(&Throttle, MSR, DX1);							//Pilot head: zoom in
	MapKey(&Throttle, MSL, DX2);							//Pilot head: zoom out
	MapKey(&Throttle, MSP, DX3);							//Quick look: maximum
	
	//KeyAxis(&Throttle, SCX, 0, AXMAP2(5, USB[0x54],0, 0, 0,USB[0x55]));	//Snap View Left-Right Nacelle
	
														//PLANE CONTROLS
	MapKey(&Throttle, CSR, DX4);							//Rudder trim axis
	MapKey(&Throttle, CSL, DX5);
	MapKey(&Throttle, FLAPU, DX6);							//Flaps up
	MapKey(&Throttle, FLAPD, DX7);							//Flaps down
	KeyAxis(&Throttle, THR_FC, 0, AXMAP2(3, DX8, 0, DX9)); 	
															//Gear up, Gear down, Wheels parking brakes on/off
	MapKey(&Throttle, RDRNRM, PULSE+DX11);					//Landing lights on/off
	MapKeyR(&Throttle, RDRNRM, DX11);
	MapKey(&Throttle, EACON, PULSE+DX12);					//Navigation lights on/off
	MapKeyR(&Throttle, EACON, DX12);
	MapKey(&Throttle, APENG, TEMPO(DX13,DX14,500));			//Cockpit light on/off
															//Formation lights on/off
															
														//PLANE ENGINE CONTROLS
															
															//Engage sengine 1 start procedure / Stop engine
	MapKeyR(&Throttle, IDLELON, EXEC("if(!Throttle[EOLMOTOR]) ActKey(KEYON+PULSE+DX19);") );
	MapKey(&Throttle, IDLELON, EXEC("if(!Throttle[EOLMOTOR]) ActKey(KEYON+PULSE+DX19);") );
															//Engage sengine 2 start procedure / Stop engine
	MapKeyR(&Throttle, IDLERON, EXEC("if(!Throttle[EORMOTOR]) ActKey(KEYON+PULSE+DX20);") );
	MapKey(&Throttle, IDLERON, EXEC("if(!Throttle[EORMOTOR]) ActKey(KEYON+PULSE+DX20);") );
	
	MapAxis(&Throttle, THR_LEFT, DX_Z_AXIS);				//Engine 1 throttle control (Z)
	SetCustomCurve(&Throttle, THR_LEFT, LIST(0,100, 65,0, 100,0));
	
	MapAxis(&Throttle, THR_RIGHT, DX_ZROT_AXIS);			//Engine 2 throttle control (ZROT)
	SetCustomCurve(&Throttle, THR_RIGHT, LIST(0,100, 65,0, 100,0));
	
															//Engine 1,2 mixture control
	MapKey(&Throttle, PSF, EXEC("if(flagEngine1) ActKey(KEYON+DX15); if(flagEngine2) ActKey(KEYON+DX17);"));
	MapKeyR(&Throttle, PSF, EXEC("ActKey(DX15); ActKey(DX17);"));
	MapKey(&Throttle, PSB, EXEC("if(flagEngine1) ActKey(KEYON+DX16); if(flagEngine2) ActKey(KEYON+DX18);"));
	MapKeyR(&Throttle, PSB, EXEC("ActKey(DX16); ActKey(DX18);"));
  	MapKey(&Throttle, PSM, PULSE+LED(&Throttle, LED_INTENSITY, 0));
  	
	MapKey(&Throttle, EFLNORM, PULSE+DX21);  				//Engine 1 supercharger mode switch
	MapKeyR(&Throttle, EFLNORM, DX21);
	MapKey(&Throttle, EFRNORM, PULSE+DX22);					//Engine 2 supercharger mode switch
	MapKeyR(&Throttle, EFRNORM, DX22);
															//Engine 1,2 propeller RPM control
	MapKey(&Throttle, SPDF, EXEC("if(flagEngine1) ActKey(KEYON+DX23); if(flagEngine2) ActKey(KEYON+DX25);"));
	MapKeyR(&Throttle, SPDF, EXEC("ActKey(DX23); ActKey(DX25);"));
	MapKey(&Throttle, SPDB, EXEC("if(flagEngine1) ActKey(KEYON+DX24); if(flagEngine2) ActKey(KEYON+DX26);"));
	MapKeyR(&Throttle, SPDB, EXEC("ActKey(DX24); ActKey(DX26);"));
	
	MapKey(&Throttle, SC, 0);								//Engines (all inlet; 1,2 outlet) cowl shutters control
	MapKey(&Throttle, CHF, EXEC("if(Throttle[SC]) ActKey(KEYON+USB[0x68]); if(flagEngine1 & !Throttle[SC]) ActKey(KEYON+DX27); if(flagEngine2 & !Throttle[SC]) ActKey(KEYON+DX29);"));
	MapKeyR(&Throttle, CHF, EXEC("ActKey(USB[0x68]); ActKey(DX27); ActKey(DX29);"));
	MapKey(&Throttle, CHB, EXEC("if(Throttle[SC]) ActKey(KEYON+USB[0x69]); if(flagEngine1 & !Throttle[SC]) ActKey(KEYON+DX28); if(flagEngine2 & !Throttle[SC]) ActKey(KEYON+DX30);"));
	MapKeyR(&Throttle, CHB, EXEC("ActKey(USB[0x69]); ActKey(DX28); ActKey(DX30);"));
	
															//Feather Propellers
	MapKey(&Throttle, EOLIGN, EXEC("ActKey(KEYON+PULSE+CHAIN(PULSE+'-',D(100),PULSE+L_CTL+'f',D(100),PULSE+'0'));")	);														
	MapKey(&Throttle, EORIGN, EXEC("ActKey(KEYON+PULSE+CHAIN(PULSE+'=',D(100),PULSE+L_CTL+'f',D(100),PULSE+'0'));")	);

														//NON-GAME CONTROLS
	MapKey(&Throttle, CSD, L_ALT);							//TS3 PTT
	MapKey(&Throttle, CSU, R_CTL);							//SRS #1
	MapKey(&Throttle, LTB, '9');							//SRS Select Intercom
	MapKey(&Throttle, SC, 0);								//SRS Channel Switch Next/Previous
	KeyAxis(&Throttle, SCY, 0, AXMAP2(5, REXEC(0,333,"ActKey(KEYON+PULSE+PGDN);"),0,0,0,REXEC(1,333,"ActKey(KEYON+PULSE+PGUP);")) );
															//SRS Radio Select First/Second
	KeyAxis(&Throttle, SCX, 0, AXMAP2(5, REXEC(2,333,"ActKey(KEYON+PULSE+L_SHIFT+'9');"),0,0,0,REXEC(3,333,"ActKey(KEYON+PULSE+L_CTL+'9');")) );

	MapKey(&Throttle, LDGH, 0);
	MapKey(&Throttle, APPAT, 0);
	MapKey(&Throttle, APALT, 0);
	MapKey(&Throttle, MSU, 0);
	MapKey(&Throttle, MSD, SCRLCK);							//TrackIR Center
	MapKey(&Throttle, EOLMOTOR, 0);
	MapKey(&Throttle, EORMOTOR, 0);
}

//event handler
int EventHandle(int type, alias o, int x)
{
    DefaultMapping(&o, x);
	
	//add event handling code here
}

If that is the work of a casual user which somehow doesn't deserve consideration in game design (why would those correlate?) then I have failed to be convincing.

May 25, 2023

27 minutes ago, FTC_Frederf said:

I have failed to be convincing.

Yes

May 25, 2023

54 minutes ago, FTC_Frederf said:

1. I'm sure there are.

2. I disagree. This is something which affects almost all users almost every flight. It should be improved according to whatever priority the developers decide, not you.

3. Yes, I have a Thrustmaster Warthog and I use the speed brake switch as RPM control in almost every situation. Here is my joystick script.

Reveal hidden contents

}

include "target.tmh" 
	char flagEngine1;									//Engine Control Flags
	char flagEngine2;
	char flagEngine3;
int main()
{
    Configure(&Joystick, MODE_EXCLUDED);
    
    if(Init(&EventHandle)) return 1;
	
	SetKBRate(250, 100); //PULSE, DELAY
	SetKBLayout(KB_ENG);
	
	flagEngine1=1;
	flagEngine2=1;
	MapKey(&Throttle, BSB, EXEC("flagEngine1=1; flagEngine2=0;") );
	MapKey(&Throttle, BSM, EXEC("flagEngine1=1; flagEngine2=1;") );
	MapKey(&Throttle, BSF, EXEC("flagEngine1=0; flagEngine2=1;") );
														//PILOT HEAD CONTROL
	MapKey(&Throttle, MSR, DX1);							//Pilot head: zoom in
	MapKey(&Throttle, MSL, DX2);							//Pilot head: zoom out
	MapKey(&Throttle, MSP, DX3);							//Quick look: maximum
	
	//KeyAxis(&Throttle, SCX, 0, AXMAP2(5, USB[0x54],0, 0, 0,USB[0x55]));	//Snap View Left-Right Nacelle
	
														//PLANE CONTROLS
	MapKey(&Throttle, CSR, DX4);							//Rudder trim axis
	MapKey(&Throttle, CSL, DX5);
	MapKey(&Throttle, FLAPU, DX6);							//Flaps up
	MapKey(&Throttle, FLAPD, DX7);							//Flaps down
	KeyAxis(&Throttle, THR_FC, 0, AXMAP2(3, DX8, 0, DX9)); 	
															//Gear up, Gear down, Wheels parking brakes on/off
	MapKey(&Throttle, RDRNRM, PULSE+DX11);					//Landing lights on/off
	MapKeyR(&Throttle, RDRNRM, DX11);
	MapKey(&Throttle, EACON, PULSE+DX12);					//Navigation lights on/off
	MapKeyR(&Throttle, EACON, DX12);
	MapKey(&Throttle, APENG, TEMPO(DX13,DX14,500));			//Cockpit light on/off
															//Formation lights on/off
															
														//PLANE ENGINE CONTROLS
															
															//Engage sengine 1 start procedure / Stop engine
	MapKeyR(&Throttle, IDLELON, EXEC("if(!Throttle[EOLMOTOR]) ActKey(KEYON+PULSE+DX19);") );
	MapKey(&Throttle, IDLELON, EXEC("if(!Throttle[EOLMOTOR]) ActKey(KEYON+PULSE+DX19);") );
															//Engage sengine 2 start procedure / Stop engine
	MapKeyR(&Throttle, IDLERON, EXEC("if(!Throttle[EORMOTOR]) ActKey(KEYON+PULSE+DX20);") );
	MapKey(&Throttle, IDLERON, EXEC("if(!Throttle[EORMOTOR]) ActKey(KEYON+PULSE+DX20);") );
	
	MapAxis(&Throttle, THR_LEFT, DX_Z_AXIS);				//Engine 1 throttle control (Z)
	SetCustomCurve(&Throttle, THR_LEFT, LIST(0,100, 65,0, 100,0));
	
	MapAxis(&Throttle, THR_RIGHT, DX_ZROT_AXIS);			//Engine 2 throttle control (ZROT)
	SetCustomCurve(&Throttle, THR_RIGHT, LIST(0,100, 65,0, 100,0));
	
															//Engine 1,2 mixture control
	MapKey(&Throttle, PSF, EXEC("if(flagEngine1) ActKey(KEYON+DX15); if(flagEngine2) ActKey(KEYON+DX17);"));
	MapKeyR(&Throttle, PSF, EXEC("ActKey(DX15); ActKey(DX17);"));
	MapKey(&Throttle, PSB, EXEC("if(flagEngine1) ActKey(KEYON+DX16); if(flagEngine2) ActKey(KEYON+DX18);"));
	MapKeyR(&Throttle, PSB, EXEC("ActKey(DX16); ActKey(DX18);"));
  	MapKey(&Throttle, PSM, PULSE+LED(&Throttle, LED_INTENSITY, 0));
  	
	MapKey(&Throttle, EFLNORM, PULSE+DX21);  				//Engine 1 supercharger mode switch
	MapKeyR(&Throttle, EFLNORM, DX21);
	MapKey(&Throttle, EFRNORM, PULSE+DX22);					//Engine 2 supercharger mode switch
	MapKeyR(&Throttle, EFRNORM, DX22);
															//Engine 1,2 propeller RPM control
	MapKey(&Throttle, SPDF, EXEC("if(flagEngine1) ActKey(KEYON+DX23); if(flagEngine2) ActKey(KEYON+DX25);"));
	MapKeyR(&Throttle, SPDF, EXEC("ActKey(DX23); ActKey(DX25);"));
	MapKey(&Throttle, SPDB, EXEC("if(flagEngine1) ActKey(KEYON+DX24); if(flagEngine2) ActKey(KEYON+DX26);"));
	MapKeyR(&Throttle, SPDB, EXEC("ActKey(DX24); ActKey(DX26);"));
	
	MapKey(&Throttle, SC, 0);								//Engines (all inlet; 1,2 outlet) cowl shutters control
	MapKey(&Throttle, CHF, EXEC("if(Throttle[SC]) ActKey(KEYON+USB[0x68]); if(flagEngine1 & !Throttle[SC]) ActKey(KEYON+DX27); if(flagEngine2 & !Throttle[SC]) ActKey(KEYON+DX29);"));
	MapKeyR(&Throttle, CHF, EXEC("ActKey(USB[0x68]); ActKey(DX27); ActKey(DX29);"));
	MapKey(&Throttle, CHB, EXEC("if(Throttle[SC]) ActKey(KEYON+USB[0x69]); if(flagEngine1 & !Throttle[SC]) ActKey(KEYON+DX28); if(flagEngine2 & !Throttle[SC]) ActKey(KEYON+DX30);"));
	MapKeyR(&Throttle, CHB, EXEC("ActKey(USB[0x69]); ActKey(DX28); ActKey(DX30);"));
	
															//Feather Propellers
	MapKey(&Throttle, EOLIGN, EXEC("ActKey(KEYON+PULSE+CHAIN(PULSE+'-',D(100),PULSE+L_CTL+'f',D(100),PULSE+'0'));")	);														
	MapKey(&Throttle, EORIGN, EXEC("ActKey(KEYON+PULSE+CHAIN(PULSE+'=',D(100),PULSE+L_CTL+'f',D(100),PULSE+'0'));")	);

														//NON-GAME CONTROLS
	MapKey(&Throttle, CSD, L_ALT);							//TS3 PTT
	MapKey(&Throttle, CSU, R_CTL);							//SRS #1
	MapKey(&Throttle, LTB, '9');							//SRS Select Intercom
	MapKey(&Throttle, SC, 0);								//SRS Channel Switch Next/Previous
	KeyAxis(&Throttle, SCY, 0, AXMAP2(5, REXEC(0,333,"ActKey(KEYON+PULSE+PGDN);"),0,0,0,REXEC(1,333,"ActKey(KEYON+PULSE+PGUP);")) );
															//SRS Radio Select First/Second
	KeyAxis(&Throttle, SCX, 0, AXMAP2(5, REXEC(2,333,"ActKey(KEYON+PULSE+L_SHIFT+'9');"),0,0,0,REXEC(3,333,"ActKey(KEYON+PULSE+L_CTL+'9');")) );

	MapKey(&Throttle, LDGH, 0);
	MapKey(&Throttle, APPAT, 0);
	MapKey(&Throttle, APALT, 0);
	MapKey(&Throttle, MSU, 0);
	MapKey(&Throttle, MSD, SCRLCK);							//TrackIR Center
	MapKey(&Throttle, EOLMOTOR, 0);
	MapKey(&Throttle, EORMOTOR, 0);
}

//event handler
int EventHandle(int type, alias o, int x)
{
    DefaultMapping(&o, x);
	
	//add event handling code here
}

If that is the work of a casual user which somehow doesn't deserve consideration in game design (why would those correlate?) then I have failed to be convincing.

Fly Luftwaffe (109 or 190), the go faster/slow down lever always starts at 0% on the runway.

And/or map your levers to levers, rather than arcading them with buttons/switches (for full realism and immersion thereof).

May 26, 2023

14 hours ago, Hetzer-JG51 said:

And/or map your levers to levers, rather than arcading them with buttons/switches (for full realism and immersion thereof).

Thank you for the suggestion but this is not related to the suggested.

Sign In

Why do airplanes start at 0% RPM lever position at start?

Recommended Posts

dburne

FuriousMeow

BlitzPig_EL

czech693

Guest deleted@83466

BornToBattle

Gambit21

RNAS10_Mitchell

JG7_X-Man

RoseWard

Art-J

JV44Stacko

FTC_Frederf

Guest deleted@83466

FTC_Frederf

FuriousMeow

Gambit21

FTC_Frederf

Guest deleted@83466

Gambit21

FTC_Frederf

FuriousMeow

BraveSirRobin

FTC_Frederf

Gambit21

Guest

FTC_Frederf

Create an account or sign in to comment

Create an account

Sign in

Browse All

Activity