Jump to content

1.5 Huey Exhaust Flame


Sk1nn3r

Recommended Posts

Sounds like you had a hot start. I can't speak for the duration that it should last, but if you let the starter get to 100% (~10% N1) before you go to idle, you shouldn't see any fire at all.

LG 34UC97 34" 3440x1440 monitor | 2x GTX-980 G1 Gaming

I7-5820k @ 3.3GHz | 16GB Corsair Vengeance DDR4 @ 2133Mhz

Samsung 840 EVO 120GB & 1TB SSDs | Seagate 3TB HDD

TM Warthog | Saitek Pro Flight Combat Pedals

Link to comment
Share on other sites

Not sure if anyone has ran into this issue yet but after the recent 1.5 update, I was manually starting up my Huey and the flames coming out of the exhaust would not stop, even during flight.

 

Hi,

 

I have the same problem. The flames also don't stop if the engine is off.

And I have no heat blur from the exhaust, only the AI has it.

  • Like 1

DCS Mods and Skins: HiDrive

Use the NAS only if the other Link is not working - it's slow!
My DCS MODs and Skins: NAS

Link to comment
Share on other sites

Not sure if anyone has ran into this issue yet but after the recent 1.5 update, I was manually starting up my Huey and the flames coming out of the exhaust would not stop, even during flight.

 

Same here with an Auto Start.

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

Link to comment
Share on other sites

That could be a hot start meaning your throttle is open causing flame during startup. Try checing your throttle setting making sure it's at the lowest setting (roll it all the way up then down).

 

As for the heat blur, the issue has been raised ever since the release of DCS 1.5, and has been reported :) Hopefully we get a fix soon:)

PINOY PRIDE!!!

 

System Specs: i7-4790, Windows 7 64-Bit, ECS L337 Z87H3-A3X Mobo, HyperX Fury 32Gb, Nvidia Titan (Pascal), TM Warthog and TFRPedals, TrackIR 5

Link to comment
Share on other sites

Got the same issue with the last Update 1.5.1.

Flames don´t vanish but do no harm to the chopper.

I´m starting the Huey correctly.

System Specs: AMD Ryzen 5 3600, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base  VR: HP Reverb G2

Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D  Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis  / F-16C / F-15E / F-4E (soon)  WWII: Spitfire / WWII Assets Pack

Tech.: Combined Arms / NS430 / Supercarrier   Maps:  Nevada / Persian Gulf / Normandie / Syria / South Atlantic  Waiting for:  BO-105 / OH 58D / CH-47 Chinook / G.91R / Tornado IDS / A-7E Corsair II

Link to comment
Share on other sites

  • ED Team

If someone could provide a short track showing the issue it would be very helpfull

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

Hope this quick startup sequence is helpful.

hueystartup.trk

System Specs: AMD Ryzen 5 3600, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base  VR: HP Reverb G2

Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D  Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis  / F-16C / F-15E / F-4E (soon)  WWII: Spitfire / WWII Assets Pack

Tech.: Combined Arms / NS430 / Supercarrier   Maps:  Nevada / Persian Gulf / Normandie / Syria / South Atlantic  Waiting for:  BO-105 / OH 58D / CH-47 Chinook / G.91R / Tornado IDS / A-7E Corsair II

Link to comment
Share on other sites

I tried something different. I open the throttle just half way, then starting the engine up to 70 %. After that i close the throttle for a few seconds while the rpm remain by 70%. The exhaust flame is getting off. When i open the throttle full up there are no more flames.

 

That will work. Is that the right way? I never done so before, so i will wonder if it is a feature.

System Specs: AMD Ryzen 5 3600, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base  VR: HP Reverb G2

Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D  Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis  / F-16C / F-15E / F-4E (soon)  WWII: Spitfire / WWII Assets Pack

Tech.: Combined Arms / NS430 / Supercarrier   Maps:  Nevada / Persian Gulf / Normandie / Syria / South Atlantic  Waiting for:  BO-105 / OH 58D / CH-47 Chinook / G.91R / Tornado IDS / A-7E Corsair II

Link to comment
Share on other sites

OK. I have done it wrong before. :doh:

 

Open the throttle full, then close it to idle. Starting now the engine. Wenn then engine is running, open the throttle again. :smartass:

 

The new thing is, the HOT Start is causing flames at the exhaust.

System Specs: AMD Ryzen 5 3600, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base  VR: HP Reverb G2

Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D  Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis  / F-16C / F-15E / F-4E (soon)  WWII: Spitfire / WWII Assets Pack

Tech.: Combined Arms / NS430 / Supercarrier   Maps:  Nevada / Persian Gulf / Normandie / Syria / South Atlantic  Waiting for:  BO-105 / OH 58D / CH-47 Chinook / G.91R / Tornado IDS / A-7E Corsair II

Link to comment
Share on other sites

  • 1 month later...

first I had the same reaction as you. then I re read the manual.

 

Now I can start engine, without keep this "hot start" exhaust flame.

 

before engage starter for turbines, give just a bit rpm but not full, just enough to allow the needles to begin to move as it start, then low rpm until 40. Once Turbine is on and needle stabilize, engage slowy max rpm.

 

no more exhaust flame

 

 i7-10700KF CPU  3.80GHz - 32 GO Ram - - nVidia RTX 2070 -  SSD Samsung EVO with LG  TV screen 40"  in 3840x2150 -  cockpit scale 1:1

- MS FFB2 Joystick  - COUGAR F16 throttle  - Saitek Pro Flight Rudder Pedals

 

Link to comment
Share on other sites

Saw the same after a Huey manual start with 2.0 Nevada. Looked like an afterburner. No lights on the CAWS except for the usual yellow IFF.

Windows 10 64bit / Intel Core i7-5820K Haswell-E 6-Core 3.30 GHz / 32GB RAM / GeForce GTX 1080 8GB / Dell UltraSharp 27 QHD U2715H 2560x1440 / Saitek X52 Pro Flight System / TrackIR 5

Link to comment
Share on other sites

Open the throttle full, then close it to idle. Starting now the engine. When then engine is running, open the throttle again.

 

This is correct. Roll throttle all the way open, then roll back to idle. Press and hold the starter switch until the Gas Producer gauge shows 40 RPM, then release the starter switch. Gas Producer will increase to about 70-72 RPM. Once this occurs, roll throttle all the way back up. No hot start, no flames.

Link to comment
Share on other sites

You guys were correct. I can do it now and not get a hot start. They must have tweaked the settings for starting this bird up because before I was fine and then when I tried a the other day I got the hot start issue. I've fine tuned my throttle position a bit when starting and have no problems now.

 

Cheers gents.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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