stanhope

Which flares? The ones from the starter pistol, the ones fired from under-barrel 40mm grenade launchers, modded ones, ...?

Could you share how you fixed it?

Put in onactivation: private _hintText = "Players weight:"; { _hintText = parseText format ["%1<br/>%2: %3", _hintText, name _x, load _x]; } forEach thisList; hint _hintText; Untested, let me know if it works

Read the license from the add-ons you're repacking, if they allow it you're good, if not you need to get explicit (preferably written) permission from the author. If you don't have that you're not allowed to repack. Do read the steam workshop agreement carefully. Permissions given to someone that's not you don't apply to you.

Could you verify the integrity of your game files? (steam library, right click on arma, properties, local files, verify local files) What are your computer's specs? I can tell you have 8GB of RAM but not what CPU & GPU you have

"name player" in MP returns the actual username of the player, use setvariable or something to give people a custom name or rename their group or something

There's plenty of other ways doing this, but without knowing the use case I can't suggest any.

Name your boxes box, box_1, box_2, ... and then put one of the following in trigger condition: box in thisList && box_1 in thisList && box_2 in thisList if you want your script to fire if all 3 boxes are in the trigger. box in thisList || box_1 in thisList || box_2 in thisList if you want your script to fire if one of your boxes is in the trigger.

If it's vanilla there's (to my knowledge) no way to change the ballistic behaviour of any round.

Which mods are you using?

Have you verified the integrity of your game files? (steam, right click on arma, properties, local files, verify integrity) Which mission is this happening on? Is there anything unusual in your RPT?

This seems strange to me: == "D:\Steam\steamapps\common\Arma 3\Arma3_x64.exe" -malloc=system -mod= -beservice specifically the malloc What I find even more strange is a few lines down from there it says: Allocator: Windows [] [] While all my RPTs say Allocator: C:\Program Files\SteamLibrary\steamapps\common\Arma 3\Dll\tbb4malloc_bi_x64.dll [2017.0.0.0] [2017.0.0.0] Have you tried without the custom malloc param? If that doesn't work, verify the integrity of your game files (I mean, best to do it anyway, it doesn't hurt anything)

You probably need to remote exec the switch move where the target is local, see: https://community.bistudio.com/wiki/switchMove https://community.bistudio.com/wiki/remoteExec

To call it globally put it in the init.sqf file (see https://community.bistudio.com/wiki/Event_Scripts#init.sqf). And put this above the switchmove in the code block: "params ["_target", "_player", "_params"];" See the advanced example here: https://ace3mod.com/wiki/framework/interactionMenu-framework.html

In the difficulty settings turn the option off to see units on the map iirc

Copy and paste, alternatively, go over all the vehicles in cfgvehicles using https://community.bistudio.com/wiki/configFile and filter on starting with O_ and B_.

You mean this list? https://community.bistudio.com/wiki/Arma_3:_CfgVehicles_WEST

Presumably because he wants a flying aircraft carrier. And to answer the question: because objects that are attached to other objects (the carrier that's attached to the heli) don't act as they normally would.

Have you tried using a custom memory allocator? https://community.bistudio.com/wiki/Arma_3:_Custom_Memory_Allocator

Does this also happen on vanilla vehicles?

What have you already tried to fix this issue?

What's your UI size currently set to? Small, medium or large?

Have you verified the integrity of your game files? (that's probably not going to be it, but it's such an easy step that you might as well do it, right click on arma in steam > properties > local files > verify integrity) Do you have an IPv4? Are you behind an unusually strict firewall?

Could you put the following in the windows explorer window navigation bar: "%localappdata%\Arma 3 Launcher\Logs" and have a look through the logs to see if there's anything there that's out of the ordinary?