rmk80

The workaround is to remove the F-14s from your Liberation campaign. All freezes have disappeared for me this way. Unfortunately part of the enjoyment has disappeared as well,

Thanks for your reply! It is indeed not very practical to have to wait 30-40 min for the crash to happen. Really hope you guys find something that is triggering this.

@IronMike Is there any progress on this issue?

It is caused by the Tomcats. Others are experiencing the exact same issue. Heatblur is looking into it and hopefully they find a solution.

Do you already have a clue what is causing this? Is there anything we could try to solve this? Could this be caused by the sound error that is shown in the logs?

No, im not running any mods. This is happening with either F-14 player and AI units, on all maps, on different type of missions. So far excluding the F-14 is the only 100% fix for the freezing. I do believe there is an increased chance of happening on taxing missions with a lot of units involved. If I play some simple F-14 missions I can make it until the end, including landing on the carrier without freezing. Liberation missions do not involve scripting during the missions, except for monitoring losses. All scripting is done in between missions. There are however a lot of units involved in a single mission.

I would really appreciate a fix for this. DCS just isn't the same without the F-14 Thank you for your effort!

I am sure it is. Try replacing all F-14 flights by other modules (player and AI). I bet you it won’t crash then.

Can you confirm there are also F-14s present in the mission (AI) or not? Can you confirm if this is a Liberation mission or not?

Does anybody else experience freezes/lockups when the F-14 is part of the campaign? Especially when returning from a mission so after 30+ minutes or so. Does Liberation do aynthing special that is causing this behaviour?

Oh I'm definately there already. So far it has been the only way to really prevent the freezes. I can F2 with all settings on high like a mad man and it won't freeze if there is no F-14 present in the mission. If only we could find out wat is actually triggering this? At first I suspected late activation but this does not seem the case. I do notice that most freezes happen after 30+ minutes. Are you all playing Liberation or do some of you also experience this in other missions?

Ok, I haven't got any freezes anymore ever since I took the F-14 out of the equation. Reading through other topics it seems the F-14 has an issue with late activation since 2.70. Is this something ED is looking into? This kind of renders the module useless

Ok, just a small update. i'm starting to suspect the F-14 is causing this, considering the different posts mentioning this. So I started a new Liberation campaign, on the same map, including the supercarrier, but without any F-14's on either side. Well, I just finished a 1+ hour flight without any freezes During the missions I have been cycling through all units external views like crazy, but it still didn't crash. Of course this is just 1 mission, so I have to test this further, but my guess is that the feezes are somehow caused by the F-14, specifically by any communication/sound related issue related to the carrier

Thanks for your reply. I too play Liberation missions, Since it is all I play, I can't really comment if this is happening in other missions as well. I too have crashes when hosting in single player, as well as dedicated server. Also when dying and watching the missions as an observer through F2 I too get freezes. Especially when switch to a unit that is close to the carrier.

Well lowering the terrain and/or plane textures to low certainly does help in reducing the crashes/freezes. But I still get freezes on low texture settings, both in F-14 and FA-18, while I have a 3090 with 24Gb so memory really should not be an issue. The crashes happen consistently after carrying out the mission while returning to the carrier. At a certain moment at around 40-50 miles it appears a lot of data needs to be loaded and it is either a hicup or a complete freeze of the application. I see lots of posts on different forums describing the same behaviour. Would really appreciate it if DCS could look into this.

Ok, I finally found the solution! Thanks to this thread: Apparently when you like switching views a lot in VR (F2, F6), you need to set terrain textures to low (instead of high)! Just did 2 test flights and is no longer freezing despite me switching views a lot.

I have been testing the last couple of days, what is causing this freezing issue. At first I thought it to be related to the Oculus Rift, so i tried: - switching between normal and beta drivers - swiching usb and displayports - buying a powered usb hub This did not effect the freezing. Next I tried changing things things on my PC: - updating/changing display drivers - disabling led lighting mobo etc - removed all underclocks - removing and disabling software (AV, process lasso, MSI afterburner) Still no effect. I get consistent freezing about 50 nm form the carrier when returning from a mission. So i repaired DCS, renamed/rebuild saved games, changed supercarrier to Stennis and still no effect. The only things that seems to effect it, is when I don’t switch between external views during missions. As long as I don’t switch from aircraft to aircraft through F2, I can make It till the carrier without the game locking up. I have a habit of switching through all active aircraft to see what my side is doing. What does this mean? Is this a memory issue or leak? I run fairely high settings on my 3090, should I tune things down to not overload my PC? Any help is appreciated

Did you get to fix this? My game freezes every time, after about an hour when returning to the supercarrier.

Ok, I was too optimistic. It just crashed/freezed again. Every time it happens I am on my way back from my mission and approaching the supercarrier. There is another topic describing the same behaviour.

Ok nevermind, I finally found the culprit. It was the Rift S causing the freezes. I switched the USB port and all is fine again

Hi all, I started playing again after a while, and I can't seem to finish a missions before the game freezes and is no longer responding. This never happened to me before, with the same PC and hardware. I already repaired the game files, excluded the folder from AV software, but that didn't help. Note that I only play in VR (Rift S), I play latest Liberation through a dedicated server. Attached is the latest log file. Is there anything I could try? dcs.log

I have the same issue. When switching between external views, the game locks up after a while. It does not recover, I need to close DCS. dcs.log

Yes, this is such an annoying issue

Hi, I recently started playing Liberation on my own dedicated server, to gain a few fps while playing in VR. There are however a couple of issues I have come across that I do no experience when playing SP. 1. Wingmen will either not taxi at all, or only start taxiing when ATC notices I am on the runway 2. On the carrier, my wingmen does not get launched (deck crew not noticing him) 3. Radios are a in auto/easy mode only, although turned off in settings and missing settings Is there something I could change to have the same behaviour as in Single Player?

Ok, I updated all versions on the first post. Changes: Added Syrian Power Added A10-C II Updated Moose All versions use updated code You need to remove all save games to prevent issues. Note: I did not have time to really test it (specifically Syrian Power).