Jump to content

[FIXED INTERNALLY] Fuel Tank 4 stops feeding


Recommended Posts

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

Screen_190502_173807.thumb.png.5612225041fb1ba03878de5e77fe7f2d.png

Screen_190502_175009.thumb.png.22a13b999a8193d5d5144e278ffafff4.png

Link to comment
Share on other sites

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

Screen_190510_212940.thumb.png.d2c8c007f449efded13d0fdce6e40d56.png

Screen_190510_213015.thumb.png.fae4f3ea5444a979070e2cdd8d7e155b.png

Link to comment
Share on other sites

:-)

 

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

Screen_190515_001441_landingRollFlameout_7h20m-fails.thumb.jpg.884ec32ebf98d858717b0b64e696bf97.jpg


Edited 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

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 by discwalker

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

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 by discwalker

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

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"?

InkedScreen_190515_201846_LI.thumb.jpg.bcad20d5c4db2f72b607ff9878de614b.jpg

Link to comment
Share on other sites

  • ED Team
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 by NineLine

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

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-3

2,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

  • 1 month later...

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)

attachment.php?attachmentid=212572&stc=1&d=1561244449

edit> There is no "aw shoot" in the list of the 44 Hornet Failures, and how can a thing fail two times?? Mislabeled!

Screen_190623_005300_twoTimes!.thumb.jpg.d88f5c4f26c71490a9520a46f652112e.jpg

2,5,5,32533_Hornet-aw_shoot_two_times_failure-in_mission_fails_disabled!.trk


Edited by discwalker

GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...