Dangermouseb51 Posted March 25, 2019 Share Posted March 25, 2019 (edited) Got a weird pita ,y right engine to spool up it initiates and at the 20% mark moved throttle out of detent and I see the small needle spin up to 9 o’clock position but engine not spinning up ... Seems to happen randomly any suggestions ... Jim Edited April 13, 2019 by IronMike Dangermouse [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Kultteri Posted March 25, 2019 Share Posted March 25, 2019 Have had this happen once before. For me it went away by restarting the game. Haven’t had that problem since Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
SpeedyE420 Posted March 25, 2019 Share Posted March 25, 2019 also had this happen to me a couple times in multi after getting into a new jet. Restart was the only fix I found for it. Owned Modules: F-18, F-16, F-14, AV-8B, A-10c, Huey, Hip, KA-50, Gazelle, Mig 15, Mig 19, Mig 21, FC3, P-51, BF-109, C-101, L-39, F-5, YAK-52 PC Specs- 8700k at 5.1GHz on Asrock z370 Fata1ity k6, EVGA 1080ti SSC2, 32 GB G.Skill TridentZ, 1TB NVMe m.2 Drive for DCS with a 500gb NVMe M.2 boot drive, Oculus Rift S Link to comment Share on other sites More sharing options...
IronMike Posted April 13, 2019 Share Posted April 13, 2019 Does this still happen to you? I could not reproduce it on my end. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
Oceandar Posted April 13, 2019 Share Posted April 13, 2019 (edited) After newest OB update it seems fine and working as it should. Edit : sadly to inform you, I still got this problem in MP. Got shot down, respawn then right engine didnt start. Edited April 13, 2019 by Oceandar Mastering others is strength. Mastering yourself is true power. - Lao Tze Link to comment Share on other sites More sharing options...
DUSTY Posted April 13, 2019 Share Posted April 13, 2019 I just had this problem for the first time tonight. Multiplayer in the Blue Flag PG server, got shot down by a Hazard Perry (sigh) then couldn't get the right engine started. Left and rejoined the server to no avail. F-15E | AH-64 | F/A-18C | F-14B | A-10C | UH-1H | Mi-8MTV2 | Ka-50 | SA342 | Super Carrier | Nevada | Persian Gulf | Syria | Intel Core i7 11700K - 32GB 3200MHz CL16 DDR4 - MSI GeForce RTX 3060 Gaming X 12GB - Samsung 970 EVO Plus NVMe SSD 1TB Link to comment Share on other sites More sharing options...
Valk Posted April 13, 2019 Share Posted April 13, 2019 It happened to me aswell today. Couldn't get the right engine to start either. Was also on Blue Flag PG server. Link to comment Share on other sites More sharing options...
IronMike Posted April 14, 2019 Share Posted April 14, 2019 Thank you guys, this is a separate issue, that happens after taking damage to the engine. The only fix atm is to restart DCS. We hope we can provide a fix for this soon. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
pacastro Posted April 25, 2019 Share Posted April 25, 2019 Still present in last update 2.5.4.30038. Link to comment Share on other sites More sharing options...
mattag08 Posted April 26, 2019 Share Posted April 26, 2019 I get this bug randomly. I even got it on the Case I tutorial. It seems to be a random chance that the right engine is just not functioning upon spawning in. In the case of the Case I tutorial the engine just instantly began to spool down when I hit fly. It's about one out of 20 spawns that does it and it is fixed by simply selecting a new slot (if MP) or restarting the mission (if SP). Flying the DCS: F-14B from Heatblur Simulations with Carrier Strike Group 2 and the VF-154 Black Knights! I also own: Ka-50 2, A-10C, P-51D, UH-1H, Mi-8MTV2, FC3, F-86F, CA, Mig-15bis, Mig-21bis, F/A-18C, L-39, F-5E, AV-8B, AJS-37, F-16C, Mig-19P, JF-17, C-101, and CEII Link to comment Share on other sites More sharing options...
Wavehopper Posted April 29, 2019 Share Posted April 29, 2019 Got this bug yesterday in MP. Switched from Huey to the F14 and the right engine wouldn’t light on start up. https://www.youtube.com/channel/UCC9G7AVfi68SovXCTCH-7fA Link to comment Share on other sites More sharing options...
Biggus Posted April 30, 2019 Share Posted April 30, 2019 The patch prior to this one seemed to fix it but it is now back every now and then. I can't reproduce it but it happens periodically. Link to comment Share on other sites More sharing options...
Snapage Posted June 8, 2019 Share Posted June 8, 2019 I experienced this bug for the first time today. This is after patch 2.5.5.31917. :\ Link to comment Share on other sites More sharing options...
mattag08 Posted June 8, 2019 Share Posted June 8, 2019 I still get this bug. Recently I cannot fix it simply by restarting the mission anymore. I have to restart DCS completely to fix it. Flying the DCS: F-14B from Heatblur Simulations with Carrier Strike Group 2 and the VF-154 Black Knights! I also own: Ka-50 2, A-10C, P-51D, UH-1H, Mi-8MTV2, FC3, F-86F, CA, Mig-15bis, Mig-21bis, F/A-18C, L-39, F-5E, AV-8B, AJS-37, F-16C, Mig-19P, JF-17, C-101, and CEII Link to comment Share on other sites More sharing options...
Rewis.C Posted June 12, 2019 Share Posted June 12, 2019 I'm getting this bug. It happens to me when I get shot down and go to briefing again. It does it pretty consistantly for me. It started in a multi-player server and carried over to any mission I loaded. I had to restart DCS World to resolve it. Link to comment Share on other sites More sharing options...
OxideMako Posted June 15, 2019 Share Posted June 15, 2019 Yeah, I got this today on the current OB, in MP. Link to comment Share on other sites More sharing options...
Solidsnakekillsu Posted June 16, 2019 Share Posted June 16, 2019 It’s a bug where your taken a hit to the engines and gone down then when you respawn and try to start it again it still thinks the engine is running been there since Tomcat release. Only fix right now is to completely exit dcs and restart the game Link to comment Share on other sites More sharing options...
-Painter- Posted July 9, 2019 Share Posted July 9, 2019 Got it right now again after I got hit and lost both engines on the BF:PG server. Re-slotted into a new plane after that event - right engine not spooling (left engine starts fine, cross bleed air doesn't help for the right). Regards REAPER 31 | Painter [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
IronMike Posted July 9, 2019 Share Posted July 9, 2019 Got it right now again after I got hit and lost both engines on the BF:PG server. Re-slotted into a new plane after that event - right engine not spooling (left engine starts fine, cross bleed air doesn't help for the right). That is very unfortunate, we were hoping that it got fixed with the latest patch. Thank you for the report. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
Biggus Posted July 10, 2019 Share Posted July 10, 2019 Yup, I had it tonight too. Current open beta. It is certainly rarer than it used to be. Link to comment Share on other sites More sharing options...
Solidsnakekillsu Posted July 10, 2019 Share Posted July 10, 2019 Yea I’ve had it happen a couple of times since the last OB patch also Link to comment Share on other sites More sharing options...
Mikkall Posted November 19, 2019 Share Posted November 19, 2019 Happening to me right now. Link to comment Share on other sites More sharing options...
raelias Posted November 19, 2019 Share Posted November 19, 2019 Just happened to me as well during a multiplayer session on my 3rd aircraft (DDCS) Worked as normal when I restarted DCS Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf Link to comment Share on other sites More sharing options...
IronMike Posted November 20, 2019 Share Posted November 20, 2019 The right engine is haunted. Definitley haunted, if you ask me. :D In all seriousness though, I'd wish we'd find something to be able to reproduce and fix it, but we don't. It is one of the weirdest bugs that keeps haunting us.. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
QuiGon Posted November 21, 2019 Share Posted November 21, 2019 The right engine is haunted. Definitley haunted, if you ask me. :D In all seriousness though, I'd wish we'd find something to be able to reproduce and fix it, but we don't. It is one of the weirdest bugs that keeps haunting us.. Given the randomness and rarity of this bug I can totally relate to this, being a software developer myself :) Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing! Link to comment Share on other sites More sharing options...
Recommended Posts