Peally Posted May 7, 2013 Posted May 7, 2013 Noticed while playing in BS2 that this mission is (seemingly to me) impossible to complete during the beginning. I've played it plenty of times in BS1 without issue. While starting up your helo tends to take a massive amount of small arms fire from the insurgents. Looking at the debrief it looks like some of it isn't even aimed (just stray rounds). Every time I've tried the mission my right engine catches fire from the constant hits. I've tried doing the startup shortcut cheat (as the mission recommends), and also tried manually (very quickly! :)) starting up just the extremely bare basics for flight. In both cases the engines have no time to spool up before fire and/or destruction. I don't recall much more than a stray round or two hitting the helo in BS1. If this is in the wrong section my apologies. Thanks! Semper Gumby, Always Flexible
sigzegv Posted May 8, 2013 Posted May 8, 2013 Same issue here, unable to start right engine because it is always under constant fire ( starting it and as quickly as possible doesn't change the issue )...
Peally Posted May 9, 2013 Author Posted May 9, 2013 I dont have any problems, just make sure you start up in this order: Batteries->Fuel Tanks->APU->disable Rotor-Brake -> Engines startup -> everything else. If anyone wants to see the track (sorry just the startup flown with the keyboard and no joystick/rudders), Ive attached it to this post. [ATTACH]81087[/ATTACH] When I played your track you very quickly had an engine fire, and your takeoff looked like mine, flopping off of the FARP and into the grass :D There's just a ridiculous amount of rifle fire hitting the bird during the entire process. Semper Gumby, Always Flexible
Ich666 Posted May 9, 2013 Posted May 9, 2013 Oups, didnt want to delete my post, just the attachment, since obviously the track is corrupted. Is this problem with the new patch?
Erforce Posted May 9, 2013 Posted May 9, 2013 Hello BS lovers. I've just fixed the mission for you. Please replace it in your campaign folder. Yes, some things changed causing infantry to hit your right side before your can start the engine. My modifications are : - INS infantry relocalized, higher skill. It will take care of RUs infantry, then RUS armors, then you. At this time, mortar should land too. - Modified mortar hit target zone (more precise). The old advanced waypoint (from BS1/2) were not recognised in 1.2.4 It's all about random, so INS-infantry may kill you whenever possible. Enjoy, this was one of my favorite mission. Auto Start procedure may not kill you. Manual emergency start (1mn15) WILL not kill you. :)Deployment04_eng.miz 1 TASK / ROLES acronyms guide Black Shark A.I. datalink guide illustrated (v1.2.4 Available on Wiki) DCS World Codex 1.1 : full units list (Speed/Weapons/Armor thickness/Threat zone/Weapon damage...) (Oct 2013) BlackShark 2 1.2.x Bug and glitches thread (v1.2.7)
Peally Posted May 9, 2013 Author Posted May 9, 2013 Cheers :thumbup: It's a somewhat minor issue, but hopefully ED sorts it out at some point. Breaks the campaign for people that don't frequent forums. 1 Semper Gumby, Always Flexible
pocococo Posted May 10, 2013 Posted May 10, 2013 Yay! I just came here for the same reason (no time to take off before right engine fire) and there's a fix already! : ) : ) I agree that Eagle should fix this and push a patch ASAP.
pocococo Posted May 10, 2013 Posted May 10, 2013 I was starting to wonder if I was supposed to drive my heli to the next FARP on the wheels... that or get out and start shooting with a pistol ; )
Erforce Posted May 10, 2013 Posted May 10, 2013 first time i tryed it, my right engine was burning. But as soldiers had no access to left side, i could took-off. Oh by the way, without EEG and full safe start procedure. I know veterans hate this, but... it works (ok, let's say 20% success /80% to killl your second engine ;) ) Anyway, for the 4rd mission (still kinda tutorial), it may be too hard. hehe TASK / ROLES acronyms guide Black Shark A.I. datalink guide illustrated (v1.2.4 Available on Wiki) DCS World Codex 1.1 : full units list (Speed/Weapons/Armor thickness/Threat zone/Weapon damage...) (Oct 2013) BlackShark 2 1.2.x Bug and glitches thread (v1.2.7)
Goltred Posted May 11, 2013 Posted May 11, 2013 Uh, i had no problem at all with this mission... i received enemy fire but none of my engines got badly damaged by it and i was doing the manual startup procedure (maybe i did some things shorter but that was just improvisation :P)
Boris Posted May 24, 2013 Posted May 24, 2013 Uh, i had no problem at all with this mission... i received enemy fire but none of my engines got badly damaged by it and i was doing the manual startup procedure (maybe i did some things shorter but that was just improvisation :P) Maybe you're still running an older version? PC Specs / Hardware: MSI z370 Gaming Plus Mainboard, Intel 8700k @ 5GHz, MSI Sea Hawk 2080 Ti @ 2100MHz, 32GB 3200 MHz DDR4 RAM Displays: Philips BDM4065UC 60Hz 4K UHD Screen, Pimax 8KX Controllers / Peripherals: VPC MongoosT-50, Thrustmaster Warthog HOTAS, modded MS FFB2/CH Combatstick, MFG Crosswind Pedals, Gametrix JetSeat OS: Windows 10 Home Creator's Update
fedaykin Posted November 21, 2013 Posted November 21, 2013 (edited) OMG, I am currently having the same problem. Engine 2 gets damaged immediately and won't start. I'm amazed at how careless these developers are, they constantly break things and then fail to patch them. I can't believe they still haven't fixed this. EDIT: Tried Erforce's edited mission file, thanks for that. It appears the chopper isn't supposed to have any weapons loaded, but for some reason I remember it having some cannon rounds in the first version of BS. Hmm... Edited November 21, 2013 by fedaykin
bmbpdk Posted January 5, 2014 Posted January 5, 2014 Hello BS lovers. I've just fixed the mission for you. Please replace it in your campaign folder. Yes, some things changed causing infantry to hit your right side before your can start the engine. My modifications are : - INS infantry relocalized, higher skill. It will take care of RUs infantry, then RUS armors, then you. At this time, mortar should land too. - Modified mortar hit target zone (more precise). The old advanced waypoint (from BS1/2) were not recognised in 1.2.4 It's all about random, so INS-infantry may kill you whenever possible. Enjoy, this was one of my favorite mission. Auto Start procedure may not kill you. Manual emergency start (1mn15) WILL not kill you. :) Thank you sooo much, i have been fighting this mission for weeks! Dont ask me why on earth i did´n google this problem before, perhaps because im stubborn as the mountains. Inno3d RTX 2070 Twin X2, ASUS STRIX Z270E Gaming, Intel i7 7700K, 32GB Corsair vengeance, Kingston Hyper X FPS Alloy Cherry MX Red, Logitech G102 Prodigy, Track Ir 5, Thrustmaster Warthog HOTAS, Saitek Combat Rudder pedals, Beyer Dynamic DT770, Acer CB280HK 4K monitor, Win 10 Pro 64bit
HammerUK9 Posted February 13, 2014 Posted February 13, 2014 I took ages on a full manual start and didn't get hit by anything - the enemy were suppressed quickly. HOWEVER... Upon landing I was sporting holes in everything - so was my wingman and he was also missing the top half of his vertical stab. I swear we weren't shot at by ground forces. Reviewing the log showed that, as I flew the section being illuminated by the Su-25, I actually flew through a barrage of BM-21 rockets! >_< Maybe I was just at an unlucky altitude at an unlucky time, but how I didn't get blown to bits I don't know! Tim
Nage Posted February 14, 2014 Posted February 14, 2014 I could not take off until patch 1.2.7. My right engine would be destroyed by AKs no matter what i tried. After 1.2.7. patch success on first try. So i guess they fixed it in 1.2.7. patch. :)
kampf Posted February 27, 2014 Posted February 27, 2014 I managed to complete this mission in 1.2.6, simply telling the ground crew to repair my Shark. :music_whistling: Waited some minutes while being fired by infantry and mortars. :megalol: Then manual startup and get the hell away!!! :thumbup:
Recommended Posts