kelpie Posted March 21, 2018 Posted March 21, 2018 (edited) Ok, ignoring the not-so-great takeoff, After the second to last update to DCS 2.5 I can't keep the 109 flying for more than a minute or 2 before the engine suddenly stops. There's no warning, all the gauges seem to indicate that there's no problems. Suddenly the plane bounces, the engine goes dead, and then the coolant temp gauge suddenly jumps to just over the top arrow. It makes no sense to me and I've flown the 109 well for a month prior to the update and I am doing nothing different. Can someone take a look at the track and tell me what I'm doing wrong or if there's a bug that is causing this? I have no trouble at all with the 190 or the 51D. Just the 109. Update: I noticed that something similar happens when going down the runway and the right rudder is pressed even slightly. The plane suddenly dips right and the engine stops with no way to restart it and no damage to be repaired when the ground crew is called.bf109 engine failure.trk Edited March 21, 2018 by kelpie Modules: Owned: P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf Would Like to See: Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado __________________ Specifications: Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X
amazingme Posted March 21, 2018 Posted March 21, 2018 I didn't watch the track, but, did you make sure you set the prop pitch governor to ON and the radiators to Open or Auto? 1 Specs: Asus Z97 PRO Gamer, i7 4790K@4.6GHz, 4x8GB Kingston @2400MHz 11-13-14-32, Titan X, Creative X-Fi, 128+2x250GB SSDs, VPC T50 Throttle + G940, MFG Crosswinds, TrackIR 5 w/ pro clip, JetSeat, Win10 Pro 64-bit, Oculus Rift, 27"@1920x1080 Settings:2.1.x - Textures:High Terrain:High Civ.Traffic:Off Water:High VisRan:Low Heatblur:High Shadows:High Res:1920x1080 RoC:1024 MSAA:4x AF:16x HDR:OFF DefS: ON GCI: ON DoF:Off Lens: OFF C/G:390m Trees:1500m R:max Gamma: 1.5
kelpie Posted March 21, 2018 Author Posted March 21, 2018 I didn't watch the track, but, did you make sure you set the prop pitch governor to ON and the radiators to Open or Auto? The radiator was set to Auto but the pitch governor could very well be the problem. I'll need to test it out when I get back home. ;) Modules: Owned: P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf Would Like to See: Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado __________________ Specifications: Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X
kelpie Posted March 21, 2018 Author Posted March 21, 2018 The problem was definitely the governor switch. I had it set to manual instead of automatic. Well, case closed. :P Thanks, amazingme. I probably wouldn't have caught it if you didn't mention it. Modules: Owned: P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf Would Like to See: Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado __________________ Specifications: Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X
LeCuvier Posted March 21, 2018 Posted March 21, 2018 After engine start-up it's good practice to check that the engine governor is working. When you rev up the engine, you should see the needle on the prop pitch indicator move. That's the instrument at the right of the dashboard with a clock-like dial, marked "Luftschraube/Stellungsanzeige" LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
amazingme Posted March 21, 2018 Posted March 21, 2018 The problem was definitely the governor switch. I had it set to manual instead of automatic. Well, case closed. :P Thanks, amazingme. I probably wouldn't have caught it if you didn't mention it. Glad to hear! :thumbup: Specs: Asus Z97 PRO Gamer, i7 4790K@4.6GHz, 4x8GB Kingston @2400MHz 11-13-14-32, Titan X, Creative X-Fi, 128+2x250GB SSDs, VPC T50 Throttle + G940, MFG Crosswinds, TrackIR 5 w/ pro clip, JetSeat, Win10 Pro 64-bit, Oculus Rift, 27"@1920x1080 Settings:2.1.x - Textures:High Terrain:High Civ.Traffic:Off Water:High VisRan:Low Heatblur:High Shadows:High Res:1920x1080 RoC:1024 MSAA:4x AF:16x HDR:OFF DefS: ON GCI: ON DoF:Off Lens: OFF C/G:390m Trees:1500m R:max Gamma: 1.5
skywalker22 Posted May 17 Posted May 17 When I cold start the plane, engine is keep on shutting down. Why is that so? I put the engine governor into auto mode, but still. What am I missing? If I start hot, it works just fine. Attached is an my example of cold start. bf109-k4_engineStall.trk
razo+r Posted May 17 Posted May 17 6 minutes ago, skywalker22 said: When I cold start the plane, engine is keep on shutting down. Why is that so? I put the engine governor into auto mode, but still. What am I missing? If I start hot, it works just fine. Attached is an my example of cold start. bf109-k4_engineStall.trk 5.47 MB · 0 downloads Can't watch the track because I don't have CW Germany. If you could replicate it on another map, I could take a look.
skywalker22 Posted May 17 Posted May 17 Here you go, exactly the same thing (Causasus map). Really don't know what I'm doing wrong. bf109-k4_engineStall2.trk
razo+r Posted May 17 Posted May 17 6 minutes ago, skywalker22 said: Here you go, exactly the same thing (Causasus map). Really don't know what I'm doing wrong. bf109-k4_engineStall2.trk 4.56 MB · 0 downloads The engine doesn't stop, you are just completely feathering the prop manually, which puts the engine to almost 0 RPM and producing no power. In the track, after takeoff, you put the throttle to Idle, switch the governor to manual and reduce the RPM as far as possible. Not sure if intentional or not. Either keep the governor on and in auto mode, or check your bindings that you don't have the prop rpm setting bound to a switch so it keeps feathering the prop.
skywalker22 Posted May 17 Posted May 17 No, after take off I put the governor into Auto mode (aft position), and engine rpm were at they should be.
razo+r Posted May 17 Posted May 17 (edited) 3 minutes ago, skywalker22 said: No, after take off I put the governor into Auto mode (aft position), and engine rpm were at they should be. Yes and later on you put it again into manual mode and pressing the "reduce engine rpm" button. That's what I see in the track. Edited May 17 by razo+r
skywalker22 Posted May 17 Posted May 17 7 minutes ago, razo+r said: Yes and later on you put it again into manual mode and pressing the "reduce engine rpm" button. That's what I see in the track. Sorry, no. I did that after the engine died. I tried it ones again. Same thing. Governor on Auto and engine rpm @ cca 2500, ata @ 14. Try if for your self, take control from this track, 20seconds after taking off (after I put the governor into Auto mode). And then fly. Let me know if your engines stolls after 1-2 minutes into the flight. Mine does always.
razo+r Posted May 17 Posted May 17 (edited) 14 minutes ago, skywalker22 said: Sorry, no. I did that after the engine died. I tried it ones again. Same thing. Governor on Auto and engine rpm @ cca 2500, ata @ 14. Try if for your self, take control from this track, 20seconds after taking off (after I put the governor into Auto mode). And then fly. Let me know if your engines stolls after 1-2 minutes into the flight. Mine does always. In that case the track desynced. I will try that tomorrow. Did it say or report any fault in the debriefing? Or just general "engine failure"? How does the engine stall? Instant seizure? Slowly fading? Sputtering? Have you also tried properly warming up your engine prior to reving your engine? Edited May 17 by razo+r
grafspee Posted May 17 Posted May 17 @skywalker22 Hi, i watched that replay and only thing which was out of normal was that you did rev engine couple times up to high rpm other then that everything was as i do every time. You didn't over rev engine during take off which is quite often, ppl just forget to switch governor to auto and that kills engine quite fast. My advice is that you should try to move throttle with more finesse and don't rev it high until oil temp will be in proper range but probably that is not a reason why your engine quit. If you have any mods, remove them and run repair and clear in launcher if this not helps i have no more ideas. System specs: I7 14700KF, Gigabyte Z790 Aorus Elite, 64GB DDR4 3600MHz, Gigabyte RTX 4090,Win 11, 48" OLED LG TV + 42" LG LED monitor
skywalker22 Posted May 17 Posted May 17 thx for the review and advices @grafspee, I will try to be even more gentle before the oil temp doesn't get up into the range. I have no mods what so ever. @razo+r you can see from the track how engines dies all of a sudden. -- Indeed must have been the temps that do the difference in engine shutting down, but as far as I am aware why would engine even die or shut down it self when temps are still not high enough in the 1st place? I wouldn't say when the temps are too high, then its understandable that it dies because of seizure or some similar issue, but not when not hot enough. Strange indeed. Any explanation why? And what has the governor got to do with damaging the engine? Its is only meant for the angle (pitch) of the propellers. Don't get that connection either.
saburo_cz Posted May 17 Posted May 17 (edited) Except for your terrible engine handling immediately after the engine start, I think that you kill the engine in 1:25 minute after the mission start. You switched MW content in to fuel tank at that time. I took over control your mission without that and was able to flew the 109 for long time even with the Emergency power, 1,8ATA/2800RPM. Edited May 18 by saburo_cz F6F P-51D | P-47D | Mosquito FB Mk VI | Spitfire | Fw 190D | Fw 190A | Bf 109K | WWII Assets Pack Normandy 2 | The Channel | Sinai | Syria | PG | NTTR | South Atlantic F-4E | F-14A/B | F-15E | F/A-18 | F-86 | F-16C | A-10C | FC-3 | CA | SC |
skywalker22 Posted May 17 Posted May 17 (edited) 1 hour ago, saburo_cz said: You switched MW content in to fuel tank at that time. Should I not do that? Should I put that handle to fuel tank before engine start up? Learing the plane, that's why so many questions, and want to it do properly ps: I tried with selector handle on Fuel and governor on auto right from the start, warm up the water and oil, and engine shuted down in 30sec when off the ground. Edited May 17 by skywalker22
saburo_cz Posted May 17 Posted May 17 (edited) You can switch that lever, but only when you have correct liquid in the auxiliary tank. You can change it only in mission editor before the mission is run. Water/Methanol is used as a default choice in mission editor. If fuel is in the auxiliary tank, lever could by switched at any time. And the engine must not be operating above 1,45ATA. Edited May 18 by saburo_cz F6F P-51D | P-47D | Mosquito FB Mk VI | Spitfire | Fw 190D | Fw 190A | Bf 109K | WWII Assets Pack Normandy 2 | The Channel | Sinai | Syria | PG | NTTR | South Atlantic F-4E | F-14A/B | F-15E | F/A-18 | F-86 | F-16C | A-10C | FC-3 | CA | SC |
skywalker22 Posted May 17 Posted May 17 3 minutes ago, saburo_cz said: You can switch that lever, but only when you have correct liquid in the auxiliary tank. You can change it only in mission editor before the mission is run. Water/Methanol is used as a default choice in mission editor. If fuel is in the auxiliary tank, lever could by switched at any time. And the engine must not be operating above 1,45ATA. I have that MW-50 on board, its there by default, so I leave it as it is. Anyway... I tried with selector handle on Fuel (no MW-50) and governor on auto right from the start, warm up the water and oil, and engine shuted down in 30sec when off the ground. Can you make a track, how you do it? I just don't know what I'm doing wrong.
saburo_cz Posted May 17 Posted May 17 MW on board - lever on MW Stoff (UP) Fuel on board - lever on Kraftstoff (DOWN) F6F P-51D | P-47D | Mosquito FB Mk VI | Spitfire | Fw 190D | Fw 190A | Bf 109K | WWII Assets Pack Normandy 2 | The Channel | Sinai | Syria | PG | NTTR | South Atlantic F-4E | F-14A/B | F-15E | F/A-18 | F-86 | F-16C | A-10C | FC-3 | CA | SC |
Art-J Posted May 17 Posted May 17 1 hour ago, skywalker22 said: And what has the governor got to do with damaging the engine? Its is only meant for the angle@razo+r (pitch) of the propellers. Don't get that connection either. Novice DCS 109 players tend to forget to switch to auto and overrev their engines pretty quickly. That is the 1st cause for every "my engine dies" thread in this section of the forum. The 2nd usual cause is aforementioned fuel/MW switch. If you're configured with MW mixture but put switch in "fuel" position, you're pumping water into fuel tank causing engine to fail. It's better not to fumble with the switch at all. Depending on your aft tank configuration set in mission editor, the plane always spawns with switch set correctly, so don't touch it and make sure your HOTAS doesn't flip it when NOT needed. 1 i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
skywalker22 Posted May 17 Posted May 17 1 minute ago, Art-J said: The 2nd usual cause is aforementioned fuel/MW switch. If you're configured with MW mixture but put switch in "fuel" position, you're pumping water into fuel tank causing engine to fail. It's better not to fumble with the switch at all. Depending on your aft tank configuration set in mission editor, the plane always spawns with switch set correctly, so don't touch it and make sure your HOTAS doesn't flip it when NOT needed. This is it! If there is MW-50 mixture onboard, that switch has to be in up position (MW) at all times. And no engine problems. Thx a lot mate.
Recommended Posts