zZzMan

I would like to add that this crash still happens. Updated to newest OB... Will continue testing when possible.

Hello, This bug is the failure of OSB L5 on the fuel page (Aux Gallons Ext) fails to appear when adding tanks to only stations 3/4. The OSB still works, but the text does not appear. Please refer the to attached track for an example of the issue. AH64 Tank issue.trk

To add this thread was originally made in relation to Qball and I thinking this was the same bug. Last week our tests showed that the assumption caused us to exclude data outside of the F-14 airframe. To make this clear this thread is for a crash that presents differently then the F-14 AI bug as we have seen F-18s crash singularly aswell. [Referencing above] Crash 1 affects other aiframes. Crash 2 [AI] only affects the 14 so far in testing. I could be wrong, I have minimal experience in programming and QA testing.

I am a squadron mate of Qball. You and I have been in another thread for a similar reason. I beleive there are 2 different bugs at play here. One that causes a crash consistently about 60 to 90 min in per client. Out of 12... one person would crash. The other bug is the F-14 AI issue. This bug presents more like yours. A crash later into a mission [iirc our last test I crashed at 42 min] where those who are close to each other crash together. This second condition [mission file with both active and inactive F-14 AI plus other items] has shown a 12/12 crash rate. Crash 1 seems to be an ED issue. Crash 2 seems to be a Heatblur issue. @IronMike just @ you for reference. [Sorry for formating, on mobile]

Hey all, I like all of you have been try to track down this bug. I would ask those who have experienced this watch the video linked in this thread. Is this the same issue? Does this present the same way as you have all experienced?

I have been trying to track down this issue for awhile and have been trying to get every factor in relation to the crash we can. It seems this thread and this bug report https://forum.dcs.world/topic/307327-dcs-freezesunresponsive-at-approximately-90-minutes-mission-elapsed-time/ are all the same or similar issues .... One thread thinks it is in relation to F-14 AI, this thread is kinda up in the air. Iron Mike if you read this what extra info can we help provide to track this down.

After testing the issue for over a month, F2 might be a factor, but the carrier doesn't. We have had crashes with a carrier in the mission and without. We have had crashing over 100 miles and within 2 miles. Overall even with a sample size of 12 we can not get it to happen consistently to the same person under the same conditions. Even timing is inconsistent... who knows. Have you changed your mods? Pagefile? Overall settings?

Coming back to this thread as the issue currently persists... We have been testing different items, and have yet to nail down a 100% trigger. Currently we are working with the F-14, on any map, without mods (By taking out the entire mods folder), and the issue persists. Log files and track files consistently do not generate. Our current working theory is to due with large amounts of Ram usage. The last test we have done is to decrease the amount of ram used via settings (Medium textures, Low/ off on almost everything else, and with the preload radius down to sub 14000). The crash has still occurred, but later into the mission around the 90 min from spawn. If anyone can confirm that the lowering of ram causes it to occur later in a mission then it may be a clue.

To add to this.... I am apart of an online group called VNAO, we have been experiencing the same issue, different hardware configurations, VR and flatscreen.... we have been testing, and have yet to come up with a cause that we can pin down. Come next month I will have enough of a sample group to get semi accurate results. The issue has persisted over 2 different servers with different host locations, different mission files, different airframes... I will come back when we get enough results to point to something that can help.