dont_have_name

Do your voice files have an associating .lip file? I had the same issue with my most recent mission and was only able to fix it by removing the .lip files.

HOLY MOLY I LOVE YOU KYLANIA AND I LOVE YOU LARROW! I implemented Larrow's version and stepped away for FOURTEEN MINUTES and when I came back it was still running at a smooth 60 FPS! I'll have to use my current method if it's running in single player, but Larrow's version runs perfectly on a hosted server which is where this mission will be played 99% of the time! Thank you Kylania for linking me to that script and thank you Larrow for making it! :D

The total size of the 10 scripts that run the movement is 608 KB. My mission.sqm is 262 KB. All of the scripts combined (minus sounds & images) is 1.13 MB. And I forgot to mention that the FPS decreases both in single player and when hosted on a server. It's not exclusive to multiplayer. The actual total time they will be running is dependent on how fast the players can shoot them, but before the players can there is a minimum time of just under 90 seconds. I realize that on an average run I'll probably lose about 5 frames overall, which will be annoying since the mission will continue on for longer after this ends, but I'd still really like to know if the issue is with me or with the function so I can at least attempt to fix it or use a different method.

Amateur mission maker here. I'm about to tear my hair out over this, so I'd greatly appreciate it if anyone more knowledgeable than myself could help me figure out if there's an error in my scripts or if the function BIS_fnc_unitPlay has a memory leak of some sort. So I'm trying to make a silly mission for my buddies that involves units flying around in circles, sort of like superman. I figured the best/easiest way to do this was using BIS_fnc_unitCapture to record units walking through the sky on multiple large floating boxes I had set up in a circle, then deleting the boxes and using unitPlay on the units. The unit flies their circle, and upon completion begins another go with another unitPlay. This method works wonderfully. The transitions are smooth, I can use disableAI "ANIM" as well as switchMove "HaloFreeFall_non" to make them even look like superman flying. The only problem I've faced is that over time the server host's FPS slowly declines. With 10 units on a loop for 8 minutes I lose 20 FPS! Once I terminate the functions, delete the units, and clean up everything related to the scripts, the server stays at the lower FPS unit a restart. I don't know too much about memory leaks, but this sounds like one to me. Here's the code I use to get a unit to fly the loop until they die: flyingUnit1Movement.sqf _unitPlayback = (/*too much data to paste here. It is the data copied from BIS_fnc_unitCapture*/); flyingUnit1 switchMove "HaloFreeFall_non"; _handle = [flyingUnit1, _unitPlayback] spawn BIS_fnc_UnitPlay; while {alive flyingUnit1} do { if (scriptDone _handle) then { terminate _handle; _handle = [flyingUnit1, _unitPlayback] spawn BIS_fnc_UnitPlay; }; sleep 0.1; }; terminate _handle; _handle = nil; The units themselves are all created in a separate script, here one unit's creation: unitCreation.sqf flyingUnitSpawnPoint = [22132,20857,0]; //Position close to where I want unit to fly flyingUnitGroup1 = createGroup west; "B_Soldier_F" createUnit [flyingUnitSpawnPoint, flyingUnitGroup1, "flyingUnit1 = this;"]; flyingUnit1 disableAI "ANIM"; flyingUnit1MovementHandle = execVM "flyingUnit1Movement.sqf"; I've searched the forums as well as google for anyone who had a similar issue, but I could find nothing. I've tried pretty much everything I can think of to fix it, such as using call instead of spawn and checking if the function is done based off time rather than scriptDone. Nothing I can think of works. If it turns out that unitPlay has a memory leak, I'll likely try using BIS_fnc_unitCaptureSimple and BIS_fnc_unitPlaySimple to see if those have the same issue, but due to how long it took me to get these 10 paths right and set up, I'd rather get an experts opinion first. Finally, for what it's worth, I did the math and the unitPlay function is called just under 36 times every minute. If anyone can see were this frame loss issue is coming from in my code, please help me out! I hate to jump to claiming BIS_fnc_unitPlay has a memory leak, but I've run out of ideas!

Throwing a createDiaryRecord command into the init.sqf and using the <img/> tag should work. player createDiaryRecord ["Diary", ["Title", "Description. <img image='imageName.jpg'/>"]];

CSAT used the east wind device to artificially create natural disasters, so they could then come in and help "stabilize the country". The exact quote from the final mission intro was "Grooming a network of Pro-CSAT governments". Pretty much, they mess everything up by arming criminals and creating tsunamis with the East wind device, then they can come in and "save the day" by killing/disarming the criminals and distributing aid for the tsunami damage. And as of right now there are no plans for a dedicated solo campaign.

I'll keep this spoiler free since I don't actually know what the spoiler tag is. I'd rate 4/7 of the missions as good, with Keystone and End Game being bland and Extraction being flat out awful. Me and my two buddies I played it with were pretty disappointing by length, we kind of all agreed APEX would have been much more reasonable at $25. We also were pretty disappointed at how little NATO was used. We got to see some NATO guys standing around a V44 and that was about it... Even on the last mission's video intro the NATO guy says "You'll have full NATO support at your disposal" but there's not a single friendly NATO in the whole thing, it's still just Raider 2 VS the world... It was a pretty disappointing finale. And finally, single player. There was no reason to not have bots. I read that they were left out because BI thought they were too hard for the average user to control, but that's an awful excuse. An excuse that punishes players like me who DO know how bots work, and would love to be able to set up coordinated attacks with them in this campaign. Seriously, I think every player who has NO clue how bots work would still rather have bots than not, even if all they're capable of making the bots do is follow them around. Overall, the campaign just kind of feels half baked. There were just some things missing, especially on that last mission which was hyping itself up so much.