GunSlingerAUS Posted April 10, 2010 Posted April 10, 2010 Hey guys I'm keen to start experimenting with the Russki aircraft, and have had a few successful flights in the lovely SU-25. I've hit a weird problem though -when I try the SU-25 campaign Cold War Warrior, Mission 1, my engines always catch fire just after start up? Here's my takeoff sequence: 1.) Shift + Home to start both engines 2.) Shift + L to start electronics 3.) Ctrl + c to close canopy 4.) Ctril + l to start nav lights 5.) I've tried leaving the throttle at 0% and around 30% - didn't make any difference. About a minute after start up, both engines catch fire. What am I doing wrong?:cry: Intel 11900K/NVIDIA RTX 3090/32GB DDR4 3666/Z590 Asus Maximus motherboard/2TB Samsung EVO Pro/55" LG C9 120Hz @ 4K/Windows 10/Jotunheim Schiit external headphone amp/Virpil HOTAS + MFG Crosswind pedals
mvsgas Posted April 10, 2010 Posted April 10, 2010 Try moving the throttle full forward and then back to idle before starting the engines. Make sure throttle at all the way back in the cockpit before starting the engines. To whom it may concern, I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that. Thank you for you patience. Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..
Sarge55 Posted April 10, 2010 Posted April 10, 2010 I turn on the electric power first then the engines with the throttle at 0%. That's the only difference I see. Haven't had a fire yet. [sIGPIC][/sIGPIC] i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog
Jg2001_Rasputin Posted April 10, 2010 Posted April 10, 2010 Had this problem once but noticed than that i had to throttle at ~75%. Moving it back to idle made the deal.
sonic Posted April 10, 2010 Posted April 10, 2010 Did you start the oher engine with right ALT + HOME ? [sIGPIC][/sIGPIC]
Distiler Posted April 10, 2010 Posted April 10, 2010 First is electronics, and let the instruments calibrate before starting engines. AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2
ArtMan_NL Posted April 10, 2010 Posted April 10, 2010 Never had that. Maybe you took the wrong fuel? :smilewink: Rshift L: start electronics Make sure throttle is at 0% wait a few seconds for calibrating Rshift Home: start both engines simultaneously Good luck. :joystick:
GunSlingerAUS Posted April 12, 2010 Author Posted April 12, 2010 Thanks guys - I think it was the fact I started engines before the electronics that caused the problem. Cheers! Intel 11900K/NVIDIA RTX 3090/32GB DDR4 3666/Z590 Asus Maximus motherboard/2TB Samsung EVO Pro/55" LG C9 120Hz @ 4K/Windows 10/Jotunheim Schiit external headphone amp/Virpil HOTAS + MFG Crosswind pedals
TAIPAN_ Posted April 12, 2010 Posted April 12, 2010 Also if you try to leave before they have powered up correctly. Wait until the RPM ticks past the 4 marker and backs up a bit, then you can raise throttle. Pimax Crystal VR & Simpit User | Ryzen CPU & Nvidia RTX GPU | Some of my mods
Recommended Posts