Jump to content

How do you cold start your planes?


How do you cold start?  

77 members have voted

  1. 1. Do you perform all required tests or not?

    • Yes, everything is done by the book to a "T"
      13
    • I do some tests to kill time during start up
      16
    • I don't perform any tests at all unless required for startup
      48


Recommended Posts

Posted (edited)

The topic was brought up with a friend of mine who I am introducing DCS to, and I was curious what the community consensus was.

How many people are starting up BY THE BOOK (doing ALL available tests, and checks like bulbs, warning lights and tones, BIT tests, FLCS tests, even control wash outs etc) vs how many people are just starting the aircraft and knowing that each time you spawn the aircraft is "perfect" and feel that the testing is redundant?

 

Edited by Jetliner
  • Like 2
Posted (edited)
1 hour ago, Jetliner said:

How many people are starting up BY THE BOOK (doing ALL available tests, and checks like bulbs, warning lights and tones, BIT tests, FLCS tests, even control wash outs etc) vs how many people are just starting the aircraft and knowing that each time you spawn the aircraft is "perfect" and feel that the testing is redundant?

 

On my case, I strive to learn the full cold start procedure, including all test steps that are simulated ... but once I have learnt every detail, and done a few full cold starts, for subsequent flights I employ an abbreviated checklist while I learn other aspects of the aircraft. Once I have learnt every system and weapon, I leave the aircraft aside and start learning another Module.  Didn't vote because none of the options covered my case.

 

PS: are you the same Jetliner as this Youtuber?

https://youtu.be/a4VuDetuPmA?si=P24vpH9oyEt-YKHk

... if true, then just wanted to express my appreciation for that superb tutorial.

Edited by Rudel_chw
  • Like 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

Yeah I know the tests aren’t really testing anything unless you have failures enabled. I do them anyways since they’re all part of the flow. 

  • Like 1

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted

I'd do it by the book (if time allows) but the F-14 nor F-15E doesn't have all tests implemented, nor there is any penalty for not doing it, even basic stuff like avionics malfunction due to lack of cooling (ECS off). I always have random failures on but it's rare to experience any random failure, idk if there is any at the startup possible. There'd be way more sense, incentive and motivation for full cold start if all the systems and failures were actually simulated.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Rift S   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

I launch without checking systems. i don’t want to waste time on such procedures, since I have little time for flights.

im under verification of all my messages. even if I do not agree with u, i will not be able to object 2 u.
нахожусь под проверкой всех моих сообщений. даже если я не согласен с тобой, то не смогу тебе возразить.

Posted

I always learn the most detailed startup procedure with each new module. If its simulated, I'll include it in my cold start flow and will create a lengthy checklist featuring every step. Whatever knob I touch, I then learn all the underlying devices on the side while getting used to this startup flow.
This procedure helps immensely with learning and understanding the aircraft.

I see that many people are too impatient or simply not interested in learning these things and only focus on how to get into launching weapons as fast and with the least amount of switches to press as possible. Only these comrades are usually those who then don't have any clue what to do if something's not working or any damage demands system knowledge to solve an issue.

When I know my detailed startup flow by heart, I usually create an abbreviated checklist. From then on I'll do the lengthy checklist with each first flight of the day on that specific module and the abbreviated checklist with any flight in thus module afterwards for the rest of the day. This assists me in keeping me proficient with the entire range of onboard systems, while cutting down the checks for all but the first flight.

  • Like 3
Posted

I'll do some tests while waiting for alignments, etc. depending on the aircraft.    They do seem rather pointless however, given failures aren't really modelled to any meaningful extent, and if you do get a failure, there is no mechanism within the game to rectify it or run to the spare jet.

I'll never know why running some BITs is the 'gold standard' of realism, while every other aspect is sorely lacking.  Comms (both inter-flight and ATC), weather interaction, tactics, weapons release parameters, operations tempo, arming and fuelling arrangements, etc. are all given a pass, but if you miss out a checklist item then you aren't doing it right!

Digital Cockpit Simulator indeed.

 

  • Like 4

Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP &MFDs,  pit WIP (XBox360 when traveling). Rift S.

NTTR, SoH, Syria, Sinai, Channel, South Atlantic, Kola, Afghanistan, Iraq, CA, Supercarrier, FC3, A-10CII, F-5, F-14, F-15E, F-16, F/A-18, F-86, Harrier, M2000, F1, Viggen, MiG-21, Yak-52, L-39, MB-339, CE2, Gazelle, Ka-50, Mi-8, Mi-24, Huey, Apache, OH-58, CH-47, Spitfire, Mossie. 

Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.

Posted

I prefer to cold start everything, I rarely use hot or air starts. There are fewer tests or things to check on most prop aircraft and I fly those more than others.

Flying helis and jets I still like to cold start and go through everything. There are jets I have that I can cold start, take off and land that I’ve never fired a weapon from. I’ll learn the weapons & systems if and when I want to but getting to know the aircraft is what I’m more interested in. Learning the systems is another chapter. Once I’ve learnt to use everything, I’ll move on and learn another module.

There are tests and checks I’m probably missing in a couple of things but I try not to take short-cuts if I can help it. I haven’t voted as none really apply to me.

  • Like 1
Posted
2 часа назад, Rongor сказал:

I always learn the most detailed startup procedure with each new module. If its simulated, I'll include it in my cold start flow and will create a lengthy checklist featuring every step. Whatever knob I touch, I then learn all the underlying devices on the side while getting used to this startup flow.
This procedure helps immensely with learning and understanding the aircraft.

I see that many people are too impatient or simply not interested in learning these things and only focus on how to get into launching weapons as fast and with the least amount of switches to press as possible. Only these comrades are usually those who then don't have any clue what to do if something's not working or any damage demands system knowledge to solve an issue.

When I know my detailed startup flow by heart, I usually create an abbreviated checklist. From then on I'll do the lengthy checklist with each first flight of the day on that specific module and the abbreviated checklist with any flight in thus module afterwards for the rest of the day. This assists me in keeping me proficient with the entire range of onboard systems, while cutting down the checks for all but the first flight.

If you have time for such procedures, you fly offline - then it makes sense.

im under verification of all my messages. even if I do not agree with u, i will not be able to object 2 u.
нахожусь под проверкой всех моих сообщений. даже если я не согласен с тобой, то не смогу тебе возразить.

Posted
1 minute ago, pjbunnyru said:

If you have time for such procedures, you fly offline - then it makes sense.

 

Seems you missed the part where he "usually create an abbreviated checklist". 

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
2 минуты назад, Rudel_chw сказал:

 

Seems you missed the part where he "usually create an abbreviated checklist". 

long list or short, it doesnt matter, he does verification procedures.🤷‍♂️
true, I don't understand why. but, its his decision.
he likes it, the other doesnt. everyone decides for themselves. dcs give such oportunities to both parties.👍

  • Like 2

im under verification of all my messages. even if I do not agree with u, i will not be able to object 2 u.
нахожусь под проверкой всех моих сообщений. даже если я не согласен с тобой, то не смогу тебе возразить.

Posted

I set up a Voice Attack "Auto Start" command to speed things up. This works most of the time and I can do other tasks while that is running.

  • Like 1

PC specs:

Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/SSD Drives/T.Flight HOTAS X/HP Reverb G2

Posted
3 hours ago, Lace said:

Comms (both inter-flight and ATC), weather interaction, tactics, weapons release parameters, operations tempo, arming and fuelling arrangements, etc. are all given a pass...

Depends who you ask.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Rift S   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
On 10/13/2024 at 3:29 PM, Jetliner said:

The topic was brought up with a friend of mine who I am introducing DCS to, and I was curious what the community consensus was.

How many people are starting up BY THE BOOK (doing ALL available tests, and checks like bulbs, warning lights and tones, BIT tests, FLCS tests, even control wash outs etc) vs how many people are just starting the aircraft and knowing that each time you spawn the aircraft is "perfect" and feel that the testing is redundant?

 

 

I usually do a cold start on new modules I purchase just to learn it. After that I don’t do the cold starts at all. In fact I don’t even like doing them and will vote for a Hot start any day. It’s sorta fun at first when you’re learning the jet or helo but quickly looses its appeal for me. If I want to go through procedures and Check lists I will do them at my local airport and fly for real. Then it matters and I don’t do short cuts Ever, but in DCS I just want to get in and go! DCS for me, is for relaxing and enjoying some time flying and blowing stuff up, NOT for learning procedures or pretending to be something like a fighter pilot. If you want to experience being a pilot, then become a pilot. DCS, MSFS & other sims pushed me into going after one of my dreams and that was to get my PPL. I’m glad I did and it was money well spent. So if I want to do checklist, briefing, safety checks etc., I’ll do them at the airport and Not on my PC. I will admit that MSFS was a big help in learning procedures and I could practice them before I would go fly & VR was very helpful with this as well. For example flying in controlled airspace and holding altitude or another thing i practiced was flying over Tampa Intl. since there’s a specific way to do this and I could practice that before doing it in RL the same goes for practicing maneuvers like circling around a point with crosswinds or landing with cross winds. But I do not do this in DCS! I’ll do crosswind landings and things in DCs for fun and practice bombing or dogfighting but the cold start is just a waste of time for me. I Hope that answered your question. Sorry for the long winded reply. I know first hand how some people get their feathers ruffled when people mention Hot starts or not doing things by the book.How “it’s a study sim” and stuff like that. People need to realize that people fly DCS for different reasons and use it differently than they do.  Its a game or simulation game for me and I use it to relax and make content videos for YouTube, nothing else. Thanks…

  • Like 1
Posted
On 10/14/2024 at 9:40 AM, plott1964 said:

I set up a Voice Attack "Auto Start" command to speed things up. This works most of the time and I can do other tasks while that is running.

THAT is a Great idea!!! I’ve gotta set this upon VA as well. Maybe some other functions too!!

Posted
On 10/15/2024 at 2:40 AM, plott1964 said:

I set up a Voice Attack "Auto Start" command to speed things up. This works most of the time and I can do other tasks while that is running.

Is this a special command, or just triggers the normal DCS keybind (LWin + Home) for auto starting a plane?

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted

I learn the full procedure for some jets, and do it when I feel like it, but most of the time I start up with the bare minimum.

In MP public servers, I just quick start with the cheat - I just want to get in the action, I might die in 10 minutes, so it would be silly to do a proper start with all the tests that might take longer.

  • Like 1
Posted
9 hours ago, sleighzy said:

Is this a special command, or just triggers the normal DCS keybind (LWin + Home) for auto starting a plane?

No. Just setup a VA command to use a series of keybinds or other already existing commands.

You have to do a few things first, like setting up keybinds that may not have been there to start with. What I do after that is go through the (successful) start up sequence and document each step (i.e. wait times and flipping switches), then go into VA and create a new entry for "Auto Start" or "Engine(s) Start", or something like that using what I just documented and then test it out. Be careful not to use too many combos with ALT and CTRL. For instance, if you have a combo that requires a toggle like Nosewheel Steering and you have to hold that combo down until you release, if you use other keys while toggling with ALT/CTRL you will introduce other functions that will most likely cause problems.

This method works best with Jets and Rotorwing aircraft. Prop aircraft take a little more finesse to start up.

PC specs:

Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/SSD Drives/T.Flight HOTAS X/HP Reverb G2

Posted
1 hour ago, plott1964 said:

No. Just setup a VA command to use a series of keybinds or other already existing commands.

You have to do a few things first, like setting up keybinds that may not have been there to start with. What I do after that is go through the (successful) start up sequence and document each step (i.e. wait times and flipping switches), then go into VA and create a new entry for "Auto Start" or "Engine(s) Start", or something like that using what I just documented and then test it out. Be careful not to use too many combos with ALT and CTRL. For instance, if you have a combo that requires a toggle like Nosewheel Steering and you have to hold that combo down until you release, if you use other keys while toggling with ALT/CTRL you will introduce other functions that will most likely cause problems.

This method works best with Jets and Rotorwing aircraft. Prop aircraft take a little more finesse to start up.

I imagine this has to be different for each jet, right?

Posted
5 hours ago, plott1964 said:

No. Just setup a VA command to use a series of keybinds or other already existing commands.

You have to do a few things first, like setting up keybinds that may not have been there to start with. What I do after that is go through the (successful) start up sequence and document each step (i.e. wait times and flipping switches), then go into VA and create a new entry for "Auto Start" or "Engine(s) Start", or something like that using what I just documented and then test it out. Be careful not to use too many combos with ALT and CTRL. For instance, if you have a combo that requires a toggle like Nosewheel Steering and you have to hold that combo down until you release, if you use other keys while toggling with ALT/CTRL you will introduce other functions that will most likely cause problems.

This method works best with Jets and Rotorwing aircraft. Prop aircraft take a little more finesse to start up.

Why this approach as opposed to the existing auto-start in DCS which does the same thing?

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted

Not all aircraft have an autostart feature and you may want to optimize your own.

3 hours ago, Keith Briscoe said:

I imagine this has to be different for each jet, right?

Yes.

  • Like 1

PC specs:

Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/SSD Drives/T.Flight HOTAS X/HP Reverb G2

Posted (edited)
8 hours ago, sleighzy said:

Why this approach as opposed to the existing auto-start in DCS which does the same thing?

It doesn’t do the same thing. Game auto start is whatever the developer decides and are usually far too slow and stop without performing any post start switch flipping. 
 

Building your own start macros can significantly reduce start time and do all the post start switch flipping. 
 

I used to mod the in game ones until some dope at ED decided to put them in IC. Now I use VoiceAttack. Not as nice as modding the lua file but serviceable. 

Edited by =475FG= Dawger
  • Like 2
  • Thanks 1

 

 

 

 

EDsignaturefleet.jpg

Posted

Depends of the available time and the type of mission. If I want to fly realistic and do some pìlot roleplay, I follow every step, but most of the times when I cold start the aircraft, I just do the basic tests, like FCS or fuel, and get going🕵️‍♂️

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...