McNasty_UK Posted March 21, 2022 Posted March 21, 2022 Here's my fix to a possible problem of start up on AH64 I found yesterday. Issue: Engine 1 starts to 66% no problem. Engine #2 APU gets it to 24% , flick idle switch ( Throttle now moves to idle) Engine spools to 49% then runs back down. Wont go to 66% stays in the red. My fix was to make sure the collective ( pitch) was to the floor. Then #2 would spool up to 66%. I guess I had pull a tad of pitch. Weird I know but it worked. I have my own 3D printed Collective but basically the collective is on an Axis. I cant figure out if this is a "Feature" of AH64 as in real life or a Bug. I cant see why any angle of pitch would effect #2 engine start up. Huey's engine starts at any collective setting. Ok, its common sense to floor the collective but hey. Hope this helps.
ED Team BIGNEWY Posted March 21, 2022 ED Team Posted March 21, 2022 Hi, welcome to the forum can you attach a short track replay example, you can save a track replay when you exit the mission. thank you 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, PIMAX Crystal
frostycab Posted March 21, 2022 Posted March 21, 2022 (edited) 3 hours ago, McNasty_UK said: My fix was to make sure the collective ( pitch) was to the floor. Then #2 would spool up to 66%. I guess I had pull a tad of pitch. This isn't necessarily connected to the issue at hand, but it's worth moving all your controls a little bit when first jumping into a mission. Wags mentioned this issue in his "Settling with Power" video, and showed that sometimes your axes may initially not match your physical controls. In his example he referred to cyclic and rudder, though I would guess that this could also happen with collective in some instances. Here is the link to the relevant part of the video: EDIT: I just tried to reproduce this, and although I did manage to get the start to fail it required more than just a slight input on the collective. I would estimate somewhere around 10% of the full range on my physical throttle. Definitely ensure your collective is fully zeroed at mission start and I doubt it will be an issue. Track file below. Engine start fail with collective applied.trk Edited March 21, 2022 by frostycab Supplied track file
McNasty_UK Posted March 21, 2022 Author Posted March 21, 2022 Thank you taking the time to recreate this. Ok So not so much a bug but pilot error. Although I still cant link too much pitch to no start engine 2 but 1 will. I've reset my axis in Windows too. Cheers. McNasty_UK
Recommended Posts