rmk80

Hey, I really appreciate some of you are still enjoying and playing this mission and the fact that is still running on current versions. I like your idea of adding static targets and I do think it is possible. First thing to check is if all required Moose functions are available for static objects as well (not sure). Apart from adding the statics in the mission editor, it requires adding a new category to the script. This will take some edits. Maybe I can have a look when I’m back from vacation

Wow great find! Im gonna have to dive into Helios to see if I can replicate your solution

Well, after some intense flying since the OB with the fix I haven’t had any freezes anymore! Very happy that this issue that had been bugging me since April has been fixed. A true Christmas present

Ah great, thx for confirming! I will check and see if I can reproduce the freezing

So did the fix make it into the OB today?

Or you could use Voiceattack, works perfectly for VR

Hi, if I hide the cockpit with Alt + F1 the buttons on my UFC no longer function and it is also no longer synchronized. If I unhide the cockpit everything is back to normal. Is this intended/normal behaviour? Is there a work around? The DDI’s do keep working without the cockpit visible.

Are u sure?! That would be awesome news

I received the tracking link just today. Now let’s see what I have to pay to customs! Probably another 21%

Same for me. Has not been shipped yet

Yes, I can fly any other module without freezes as long as there are no F-14s in the missions. if they are present, the game freezes no matter the module I’m flying. Disabling the F14 module did not change this behaviour.

Is there already any progress/news on this issue?

This might be caused because a FARP is considered as a group, but with "dead" units/objects in it (just guessing). Somehow the original counting of total units (when saving) has a different result then when you request a status report. You could try to add two lines. First: (see line that has THENAMEOFYOURFARP) --SAVE TOTAL UNIT COUNT totalRedUnitCount = 0 totalBlueUnitCount = 0 local AllGroups = SET_GROUP:New():FilterCategories("ground"):FilterActive(true):FilterOnce() AllGroups:RemoveGroupsByName("THENAMEOFYOURFARP") SCHEDULER:New( nil, function() AllGroups:ForEachGroupAlive(function (GROUP) if GROUP:GetCoalition() == 1 then totalRedUnitCount = totalRedUnitCount + getAliveUnitsGrp(GROUP) end if GROUP:GetCoalition() == 2 then totalBlueUnitCount = totalBlueUnitCount + getAliveUnitsGrp(GROUP) end end) Second: (see line that has THENAMEOFYOURFARP) BLUE_TARGET_SET = SET_GROUP:New() BLUE_TARGET_SET = RemoveGroupsByName("THENAMEOFYOURFARP") Not sure if this will work though

I got the same error just now. Never seen it before

Ok, that didn't take too long. Just had a freeze when switching views.

Have you tried a slow repair? Did you clear out the FXO and Metashader2 folders after the patch?

Funny thing is I have not had a single freeze since 2.8. And I have been flying 8 Liberation missions so far with lots of F-14s and view changes (F2). Of course this doesn’t mean a thing until you get one, but I do find it odd and it has been months since I could actually return to the carrier in these missions. I will of course report back if I break my lucky chain

Fingers crossed

I tried this workaround, but I still got a mission freeze. So far the only real workaround for me that has proven to work is not having any Tomcats in the mission.

I also tried IronMike's fix, but unfortunately it did'nt fix it for me. Just had another freeze

Just posting the solution in case anybody else has the same issue: You need to add all units of the carrier group to this script part (so they are not considered airbases): Note that these are unit names! do -- FIND BLUE AIRBASES BLUE_AIRBASE_SET = SET_AIRBASE:New() :FilterCoalitions("blue") :FilterOnce() BLUE_AIRBASE_SET:RemoveAirbasesByName({"CVN-71","Blue Escort #001","Blue Escort #002","Blue Escort #003","Blue Escort #004"}) MESSAGE:New( BLUE_AIRBASE_SET:Count().. " BLUE AIRBASES FOUND", messageTime, nil ):ToAllIf(DEBUG) end You should also add your carrier (group name) like this: do -- INIT CARRIER & TANKER MESSAGE:New( "INIT CARRIER & TANKER", messageTime, nil ):ToAllIf(DEBUG) local BLUE_CARRIER = GROUP:FindByName( "BLUE CARRIER" ) BLUE_CARRIER:PatrolRoute() local BLUE_CARRIER_2 = GROUP:FindByName( "THENAMEOFYOURCARRIER" ) BLUE_CARRIER_2:PatrolRoute() -- CARRIER TANKER local BLUE_TANKER_TEXACO= RECOVERYTANKER:New(UNIT:FindByName("CVN-71"), "BLUE TANKER TEXACO") BLUE_TANKER_TEXACO:SetTakeoffAir() BLUE_TANKER_TEXACO:SetTACAN(81, "TEX") BLUE_TANKER_TEXACO:SetRadio(261,"AM") BLUE_TANKER_TEXACO:SetCallsign(1) BLUE_TANKER_TEXACO:Start() end Also set local DEBUG = true at the beginning of the script to see what is happening in case of errors or stalling of the mission.

I noticed a lot of us are having this error in our logs: 2022-09-24 01:46:26.469 ERROR SOUND: can't load wave: "speech\eng\common\navy_player\effects\aircrafts\cockpits\radioclickbefore.wav" 2022-09-24 01:46:26.472 ERROR SOUND: can't load wave: "speech\eng\common\navy_player\effects\aircrafts\cockpits\radioclickafter.wav" Could this have anything to do with the freezes?

@IronMike Are you still looking into possible fixes for this issue, since the last OB unfortunately didn't fix it? As for the event causing this. I strongly feel this is somehow related to (AI) flights returning from their sorties. Whether it has to do with communication between AI and carrier, available landing/parking spots on the carrier, or despawning events, I really don't know. I still do have AI F-14s returning and landing on the carrier just fine, so maybe it has something to do with the amount of AI units involved around the carrier. I did notice that when I started my own flights in Liberation at the start of mission time, the freezes always happen in the 30-50 min timeframe. Which is when the first flights are getting back. In the latest Liberation you have the option to speed up/skip mission time, so I'm actually starting later. This immediately has its effect on the freezes which can happen within the first 10 minutes, when the actual mission is already 30 min on its way. This leads me to believe it is somehow tied to returning flights.

I was kind of excited to see the latest patch has a possible fix for the F14 freezing issue. Unfortunately I just had another freeze, exactly the same as before. Anybody else seeing this as well after latest beta patch?

I does look like it is related to high memory usage. So complex missions, high textures and lots of changing views seems to increase or speed up the chance of the freeze happening. On the other hand I highly suspect it happens when the AI F14's return to the carrier. Does anyone also get these feezes in complex mission which include AI F14s but lack the carrier?