Toumal Posted March 17, 2022 Share Posted March 17, 2022 I have a peculiar problem: I can start engine 1 no problem, but engine 2 goes up to NG of 52% and then drops back to 0. I do the same procedure on both engines, following wags' tutorial video and the quickstart guide. Any suggestions? Anyone have a similar problem? 2 Link to comment Share on other sites More sharing options...
mattprice693 Posted March 17, 2022 Share Posted March 17, 2022 I had the same issue. Found that if you advance the power lever soon after starting engine two instead of waiting for 20% as the tutorial advises, worked for me. Link to comment Share on other sites More sharing options...
Toumal Posted March 17, 2022 Author Share Posted March 17, 2022 I had a different cause: I waited too long after starting engine 1. If you give it like 20 seconds to settle, starting engine 2 won't work anymore. You have to get a fresh bird. Feels like a bug, but what do I know Link to comment Share on other sites More sharing options...
Aerovenator Posted March 18, 2022 Share Posted March 18, 2022 Had the same issue. In my case the cause was the collective. It was slightly raised. 1 1 I7-9700K -- 32GB RAM -- RTX 4070 -- Virpil T-50CM3 Throttle + WarBRD Base -- Thrustmaster TPR -- Quest 3 Link to comment Share on other sites More sharing options...
mmoccio Posted March 18, 2022 Share Posted March 18, 2022 7 hours ago, Aerovenator said: Had the same issue. In my case the cause was the collective. It was slightly raised. Thank You! That was my issue as well. This was driving me nuts F/A-18C | F-16C | JF-17 | F-14 | FC3 | AV-8B | AJS-37 | F-5E | M-2000C | Mig 15bis | C-101 | F-86 | A-10C | P-51D | Fw 190 A-8 | Christen Eagle II | Bf 109 K-4 | Ryzen 5 2600 | MSI RTX 2070 Super | ASROCK B450m Pro | 16GB G.SKill Ripjaws 3200 DDR4 | 500GB WD Blue Internal SSD | 1TB Samsung Evo 860 SSD | Logitech X56 HOTAS | PSEYE Track IR | Delan Clip | :joystick: Link to comment Share on other sites More sharing options...
garyjacques Posted March 19, 2022 Share Posted March 19, 2022 (edited) I bought AH-64D module today today and not able to start engine 2, once the engine 2 gets 52% it started to shutdown Edited March 19, 2022 by garyjacques Link to comment Share on other sites More sharing options...
Sacarino111 Posted March 19, 2022 Share Posted March 19, 2022 HI. Same issue here, but apparently the problem was too much time between eng1 and eng2 starting procedures. It is true I had to pick up a new bird, but since that moment I can start the 2nd engine no problem. I also tried the collective thing, but no joy! Saludos Saca111 Link to comment Share on other sites More sharing options...
dotChuckles Posted March 20, 2022 Share Posted March 20, 2022 The weird thing is that it all works fine for ages and then suddenly it doesn't. Been starting up all grand and then after a while, hung start doing everything exactly the same. It makes no sense. It's not the collective thing for me either. I've verified in the control window and physically. 2 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
dotChuckles Posted March 20, 2022 Share Posted March 20, 2022 Ok. I think I know what causes it. Is everyone with this problem got rudder pedals that don't return to centre like real anti torque pedals? Because I can 100% replicate the issue if my rudder pedals are centred. Centred normal start, not centred hung start. 2 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
McNasty_UK Posted March 25, 2022 Share Posted March 25, 2022 I have posted about 4 pages after this. I have had the same exact issue. I discovered my collective wasn't fully down ( in real world). Floor the collective...sorted. Wags replied to my post. Move all control surfaces / axis before starting. Hope this helps. 1 Link to comment Share on other sites More sharing options...
Balu010 Posted March 25, 2022 Share Posted March 25, 2022 On 3/17/2022 at 9:47 PM, Toumal said: I have a peculiar problem: I can start engine 1 no problem, but engine 2 goes up to NG of 52% and then drops back to 0. I do the same procedure on both engines, following wags' tutorial video and the quickstart guide. Any suggestions? Anyone have a similar problem? Happened to me today, it was because i was pulling some collective and the starter can't overpower the torque. Make sure your collective is all the way down on startup. Link to comment Share on other sites More sharing options...
tech_op2000 Posted March 25, 2022 Share Posted March 25, 2022 (edited) On 3/20/2022 at 2:05 PM, dotChuckles said: Ok. I think I know what causes it. Is everyone with this problem got rudder pedals that don't return to centre like real anti torque pedals? Because I can 100% replicate the issue if my rudder pedals are centred. Centred normal start, not centred hung start. @BIGNEWYI have duplicated DotChuckles report. If I hold full left rudder when attempting to start engine #2, it has a hung start. this also Happens if collective is up during start, but does not happen if cyclic is fully to one side or back. In the following very short track I demonstrate it failing to start with full rudder, then starting with rudder neutral. Further test had it happening about 75 percent rudder and with me holding the rudder or by pressing the trimmer and having it hold the rudder in. Additionally at the end of the track I demonstrate a potential bug with the parking brake. Set by pushing toe brakes then pulling out handle and releasing brakes. then just tap brakes and parking brake gets disabled even though the lever is still out. Rudder start fail and parking brake.trk Edited March 25, 2022 by tech_op2000 1 Link to comment Share on other sites More sharing options...
FalcoGer Posted March 31, 2022 Share Posted March 31, 2022 When trying to start engine 2 in hot weather, boost pump fail caution shows up. Engine will stop starting at 52% and spool back. Sometimes cross bleed starting works, sometimes it doesn't. no_hot_engine2_start.trk Link to comment Share on other sites More sharing options...
Japo32 Posted March 31, 2022 Share Posted March 31, 2022 I posted about the fuel boost problem... and the post was closed to further replies, because I posted that the boost was failured after a cold start. BUT this also happens with a HOT start. Here is the track, and this didn't happen previously this last patch: AH64_FuelBoostFailure_HotStart.trk Link to comment Share on other sites More sharing options...
kiss4luna Posted April 1, 2022 Share Posted April 1, 2022 me too here. once started engine 1 i have to almost immediately start engine 2, otherwise engine 2 won't go pass 53% and failed to start. RTX 3070 Link to comment Share on other sites More sharing options...
Supmua Posted April 1, 2022 Share Posted April 1, 2022 Had this engine 2 issue in MP tonight also, I was playing CP/G so not sure if it was DCS or player's error but my friend was able to get it working eventually. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/ Link to comment Share on other sites More sharing options...
whirly_nerd Posted April 1, 2022 Share Posted April 1, 2022 For me, the one thing that seems to consistently make #2 startup fail is starting in hot weather (+30C). Link to comment Share on other sites More sharing options...
nachomaga Posted April 1, 2022 Share Posted April 1, 2022 (edited) Already reported, the solution for now is to start both engines at the same time, both start switches, wait a bit, and both power levers to idle. Edited April 1, 2022 by nachomaga 1 Link to comment Share on other sites More sharing options...
shastasm Posted April 1, 2022 Share Posted April 1, 2022 Having this issue too, so glad I'm not alone. Thanks for the advise above. I will try starting Eng 2 sooner and also make sure my collective is fully down. I had to modify my Thrustmaster throttle to account for my AB detent so maybe that shows it as not fully down. 2020 Rig Chasse: bequiet! Darkbase 700 MBoard: Asus b550-F Gaming CPU: Ryzen 9 3900XT DIMM: HyperZ 3200 64 GB (16x4) GPU: Asus Strix 2070 - 8GB Storage: 2x Samsung EVO 1TB m.2 (1 dedicated for DCS) OS: Windows 10 Link to comment Share on other sites More sharing options...
imacken Posted April 1, 2022 Share Posted April 1, 2022 Guys, there is at least one other thread on this already and BN has said it has been fixed internally. It missed the cut in this week’s patch. 1 Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
Senchay Posted April 1, 2022 Share Posted April 1, 2022 It also works with llever 1 to flight position. So start eng 1, set to idle at ~18, wait for spoolup, put lever to fly and now start eng 2. Will work too. Link to comment Share on other sites More sharing options...
McNasty_UK Posted April 1, 2022 Share Posted April 1, 2022 If engine #2 starts to spool back, push throttle forward 1/2 and click engine restart. It pushes #2 back over 55% and then catches up. I'm not sure if this is how it's done in real World or what technical issues it would cause but it works. Link to comment Share on other sites More sharing options...
imacken Posted April 1, 2022 Share Posted April 1, 2022 Sorry to repeat myself, but this is a bug. It's been fixed internally as NL has said here Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
corb Posted October 16, 2022 Share Posted October 16, 2022 Thanks! It was my Collective that didnt sync with DCS. Link to comment Share on other sites More sharing options...
corbu1 Posted October 16, 2022 Share Posted October 16, 2022 vor einer Stunde schrieb corb: Thanks! It was my Collective that didnt sync with DCS. Yes, be sure your collective is synched correctly in the sim. Therefore I always move my controls a bit around… DCS MT : 2.9.4.53707 Modules: UH-1H - SA342 - KA-50 BS3 - MI-24P - MI-8MTV2 - AH-64D - UH-60L(Mod) - A-10CII - F-16C - F/A-18C - FC3 -Combined Arms - Supercarrier - NTTR - Normandy2.0 - Persian Gulf - Syria - SA - Sinai - Afghanistan(Preorder) — Waiting for: OH-58D - BO-105 - CH-47F - AH-1G/F(Mod) - OH-6(Mod) - Kola - Australia - Iraq DCS-Client: 10900K, 64GB 3600, RTX3090, 500GB M2 NVMe(win10), 2TB M2 NVMe(DCS), VR VivePro2, PointCTRL, VaicomPro, Wacom Intuos S with VRK v2Beta DCS-DServer: 11600KF, 32GB 3600, GTX1080, 1TB M2 NVMe(win10), 2TB M2 NVMe(DCSDServer), DCS Olympus Simpit: NLR Flightsim Pro, TM Warthog(40cm Ext., Dampers) + Throttle, Komodo Pedals with Dampers, VPC Rotorplus+CBkit+AH-64D Grip, NLR HF8, Buttkicker (3*MiniConcert), TotalControls AH64D MPD‘s, TM 2*MFD‘s, Streamdecks (1*32,3*15,1*6), VPC CP#1 Link to comment Share on other sites More sharing options...
Recommended Posts