ThePutzer Posted March 28, 2016 Posted March 28, 2016 In 2 separate missions(1.5beta)(Newb City), the auto start for Ka-50,has stopped working,(spools up both engines, #1 stays running and #2 dies) error right transmission oil pressure warning. The guys that know the manual start up procedures can get them runnin and stay runnin. The auto start worked just fine until yesterday(both missions)...How can I repair Ka ?? Did a dcs repair,, didnt help. ThePutzer
BodyOrgan Posted March 28, 2016 Posted March 28, 2016 I've run into this bug recently too. I'm lucky to have learned how to manually start the chopper before encountering it though. I don't think there is anything wrong with your game. Probably some update broke something. Here's how to fix it. Once the auto start completes all your switches should be where you need them to be except you'll have to turn your APU back on to crank the #2 engine, so on the right hand side of your chopper turn the APU fuel cut off switch back on, and then on left hand side of the cockpit find the APU shutoff button that has a red circle around it. There is a switch below it that you need to flip to APU setting. Once done press the start button which is two buttons to the left of the APU shutoff button. Wait 10 seconds or so for the APU to crank. There is a led light which will illuminate "APU ON" to the left of the collective to indicate this. Now go back to the switch that you flipped to APU, and click it twice to flip it to the right engine (#2), then click the start button again. It will take about 20-30 seconds for the #2 engine to fully start. Once it's up and running press the APU shutoff button, and turn off the APU fuel cutoff switch. That should do it. Good luck.
huzar Posted November 6, 2016 Posted November 6, 2016 I noticed why this is happening: after starting left engine, changing engine selector switch to right engine causes it to start without pressing the start button. Not every time, maybe in 20-25% of cases. It does happen in manual and auto start mode. Looks like a minor bug? Not a problem with manual start up but auto mode ends with only one engine running, can be confusing for a new players.
ShuRugal Posted December 16, 2016 Posted December 16, 2016 sounds like the autostart script is flipping the engine selector switch before the engine-start cycle is complete for the #1 engine. If you flip that switch while the start valve is open (indicated by the light beside the startup switch), then the bleed air will switch over to the other engine. If your timing is perfect, you can use this to shave ~10-15 seconds off your startup by flipping over when the first engine passes 50~55%. However, the helicopter's engine-control unit does not know you've done this, so it does not restart the timer on the engine startup sequence when you select the new engine. TL;DR version: ECU runs starter for a fixed length of time (~30 seconds IIRC). If you switch engines during this time, it does not reset the timer, so the starter could shut off before the engine passes the self-sustaining point.
BaD CrC Posted December 16, 2016 Posted December 16, 2016 Good! Autostart is bad for you! Manual startup or die! :smilewink::smartass: https://www.blacksharkden.com http://discord.gg/blacksharkden
flanker0ne Posted December 18, 2016 Posted December 18, 2016 Good! Autostart is bad for you! Manual startup or die! :smilewink::smartass: We need a "Allow Autostart" new server mission option. SCOPRI DI PIU': https://www.amvi.it/joinus.php DISCORD COMBINEDOPS The Battle Planning Tool
BitMaster Posted December 18, 2016 Posted December 18, 2016 Basically, after you have mastered the basics and dont fall out of the sky like a drunk dove you should learn how to start--stop--restart all your engines in any airframe you fly, that much to basics and what DCS and the missions demand from us. XDespite the Ka looks like very complicated when you get in the pit first time, the engies are rather straight forward to operate and the bug you described happens from time to time across all the missions / servers I have flown. +1 to allow autostart....another move towards forced realism...the way to go for advanced servers imho Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Sapphire Nitro+ 7800XT - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus XG27ACG QHD 180Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X
JG14_Smil Posted April 29, 2017 Posted April 29, 2017 In the macro_sequences.lua file for the Ka-50. The #2 engine attempts to start before the #1 engine start cycle has finished. Note "Start" button is pushed before the green "Start VlV" lamp has gone out. An easy fix, but the file is in Russian. It is a bona-fide bug. The dismissal of it is why it remains unfixed. :smilewink:
Recommended Posts