Skimmer8824 Posted May 2, 2019 Share Posted May 2, 2019 I have been experiencing a failure where fuel tank 4 stops feeding gas. This results in EXT XFER, FUEL LO, and R GEN warnings/failures followed by engines turning off with plenty of gas left. I have been having this issue on every F-18 flight for the past two or three months occurring on different terrains and weather. Attached is a track file and screen shots of the fuel page and warnings from two different flights.tank 4 failure.trk Link to comment Share on other sites More sharing options...
ED Team NineLine Posted May 2, 2019 ED Team Share Posted May 2, 2019 Thanks, I'll check it out. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Skimmer8824 Posted May 4, 2019 Author Share Posted May 4, 2019 I am attaching another TRK file where I took off from hot start on ramp, climbed to 23K and flew level flight. This time tank 4 fed fuel until 580 pounds. Once the tank stopped feeding several failures occured, i.e. OBOGS DEGD, FCS, RGEN, etc.tank failure at 580 pounds.trk Link to comment Share on other sites More sharing options...
ED Team NineLine Posted May 5, 2019 ED Team Share Posted May 5, 2019 So I watched your newest track, and I was not seeing the same thing, so its possible its fixed internally, watch for the issue in the next patch and let me know if you still see it. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Skimmer8824 Posted May 11, 2019 Author Share Posted May 11, 2019 I have updated to 2.5.4.30386 open beta, and I am still experiencing these issues. I have replayed the tracks I have submitted with the same results. I am also attaching a new track where the fuel tank number 4 stopped feeding at 2030 pounds. After 41 min ET, I experienced an FCS failure, then at 48 min ET an OBOGS DEGD warning. Please advise, thanks.tank failure at 2030 pounds.trk Link to comment Share on other sites More sharing options...
discwalker Posted May 14, 2019 Share Posted May 14, 2019 (edited) :-) Perhaps nothing was broken or fixed. Please thanks the FA18C failures to the mission designer. replay of your first track: See the 2 coming failures in client AC when random system failures is off (ME forced), preprogrammed failures not available due client slot. 7h20m 7h28m (+tank4 feed, right generator) +in the global settings random system failures was off during replay ++but we know the track settings is over the global settings, they are permanent until DCS restart Edited May 15, 2019 by discwalker names of failures GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
discwalker Posted May 14, 2019 Share Posted May 14, 2019 (edited) debriefing log shows the correct exact failures occured by something (indirect scripts?): [16] = { ["failure"] = "Failure_Hyd_HYD1B_Leak", ["failureDisplayName"] = "", ["initiator"] = "Pilot #038", ["initiatorMissionID"] = "114", ["initiatorPilotName"] = "Skimmer", ["t"] = 26432, ["type"] = "failure", }, [17] = { ["failure"] = "Failure_Fuel_Tank4Transfer", ["failureDisplayName"] = "", ["initiator"] = "Pilot #038", ["initiatorMissionID"] = "114", ["initiatorPilotName"] = "Skimmer", ["t"] = 26904, ["type"] = "failure", in the first mission random system failures forced to off, maybe overridden setting Edited May 14, 2019 by discwalker GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
discwalker Posted May 15, 2019 Share Posted May 15, 2019 (edited) 2.5.4.30386 without any script, only 1 AC a client FA18C and unwanted failures came. 28min runtime; caucasus; ME rnd failures forced OFF [4] = { ["failure"] = "Failure_Fuel_Tank4Transfer", ["failureDisplayName"] = "", ["initiator"] = "Pilot #001", ["initiatorMissionID"] = "269", ["initiatorPilotName"] = "discwalker", ["t"] = 26934, ["type"] = "failure", }, [5] = { ["failure"] = "Failure_ECS_Valve", ["failureDisplayName"] = "", ["initiator"] = "Pilot #001", ["initiatorMissionID"] = "269", ["initiatorPilotName"] = "discwalker", ["t"] = 27319, ["type"] = "failure", }, [6] = { ["failure"] = "Failure_PP_RightAMAD_OilLeak", ["failureDisplayName"] = "", ["initiator"] = "Pilot #001", ["initiatorMissionID"] = "269", ["initiatorPilotName"] = "discwalker", ["t"] = 28005, ["type"] = "failure", }, 2,5,4,30386_WITHOUT_takeoff_failures-RNDfailuresForcedOff3.trk Edited May 15, 2019 by discwalker GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
discwalker Posted May 15, 2019 Share Posted May 15, 2019 - Fresh DCS start - set in game oftions misc random system failures to ON, - in this mission Forced to OFF, DCS dont care about it, after approx 28 min runtime failures came (dont takeoff, just use 60x time compression)OverrideOverriddenTest.miz GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
Skimmer8824 Posted May 16, 2019 Author Share Posted May 16, 2019 I can confirm the same. After ~28 minutes of any mission, tank 4 fails(along with others), consistently. This is occurring regardless whether or not random system failures are enabled/disabled in the mission or DCS settings. Is it still the case that this is "Fixed Internally"? Link to comment Share on other sites More sharing options...
ED Team NineLine Posted May 16, 2019 ED Team Share Posted May 16, 2019 (edited) I'll check again guys, see what I see after that time period. Edited May 16, 2019 by NineLine Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
ED Team NineLine Posted May 16, 2019 ED Team Share Posted May 16, 2019 (edited) I have updated to 2.5.4.30386 open beta, and I am still experiencing these issues. I have replayed the tracks I have submitted with the same results. I am also attaching a new track where the fuel tank number 4 stopped feeding at 2030 pounds. After 41 min ET, I experienced an FCS failure, then at 48 min ET an OBOGS DEGD warning. Please advise, thanks. Can you send me the mission this is from? I see random failures set up in the mission. So that probably explains it. If this is about Random failures, it might be less about the Hornet and more about the ME or core game. Edited May 16, 2019 by NineLine Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
discwalker Posted May 17, 2019 Share Posted May 17, 2019 reproduced with F-5E-3 To get the mission option1: just open in the ME with filter set to *.trk To get the mission option2: rename it to *.zip edit with your favourite archive manager and delete the 2 track folders in it (track, track_data) rename it to *.miz open with ME in the usual way ------------------ "tank failure at 2030 pounds.trk" RANDOM system failures **NOT** forced to anything. ------------------ with this track after 48 min runtime total tacan failure came in F-5E-32,5,4,30386_f5e_failure_48min_MErndFailsSetToOFF!!!.trk GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
ED Team NineLine Posted May 17, 2019 ED Team Share Posted May 17, 2019 I already opened the track, but I wanted the original mission to be sure. As I said, sounds like a core game issue, and not a Hornet one. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
discwalker Posted May 17, 2019 Share Posted May 17, 2019 With fresh DCS start I can only trigger failures when forced to off with Hornet only, not with F5, F-15, Su-27. GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
Gruw Posted May 20, 2019 Share Posted May 20, 2019 ...sounds like a core game issue, and not a Hornet one. A core game issue sounds terrible. Any news about this? Link to comment Share on other sites More sharing options...
discwalker Posted June 22, 2019 Share Posted June 22, 2019 (edited) update Nothing is fixed, Spitfire do the same: https://forums.eagle.ru/showpost.php?p=3954365&postcount=36 steps: 1. DCS fresh start 2. Options: random system failures ON 3. load this mission, in this failures forced to OFF (but DCS will override the override) 4. jump in the single plane: Hornet /Or edit to Spitfire and jump in that./ 5. apply wheelchocks 6. open debriefing during SP mission ( " ' " key) 7. accelerate time 15x-60x 8. Wait to failure (in track: 28min28s failure / 31min14s failure as in Spitfire) edit> There is no "aw shoot" in the list of the 44 Hornet Failures, and how can a thing fail two times?? Mislabeled!2,5,5,32533_Hornet-aw_shoot_two_times_failure-in_mission_fails_disabled!.trk Edited June 22, 2019 by discwalker GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
Recommended Posts