RCA3

HighLightS (High Dynamic Range and Lighting Suite) Description: HighLightS is a custom light for Arma 3. It uses class LightingNew to change light and colors and class Weather to bring one change to the lighting system. It also uses class HDRNewPars to help balance some dark areas and add some changes to NVG and eye adaption. Features: Softer light around sun during sunrise/sunset Longer transition between day/night Earlier transition to moon light More aperture at night (brighter) Clouds are white at night if lit by moon Purple skies before sunrise and after sunset Stars stay visible a bit longer Full light of sun/moon when not covered by clouds (i.e.flying above clouds or cloud openings in the sky) No predefined color/light scheme for each overcast setting. The cloud coverage sets the colors/light NVG has less aperture (darker) NVG transition is slower Eye adaption is slower Removed aperture change when looking to the ground Wind direction is fixed in direction N/S (direction can be changed in editor, duration only through scripting) Supported Maps: Altis, Stratis, Malden, Livonia, Tanoa CUP Terrains - Maps CUP Terrains - Maps 2.0 Download: Google Drive (Steam link may come later) Credits: arma3library.gitlab.io PMC Editing Wiki Foxhound International gaming group (wiki) IFA3 discord channel @Connor. (Color Picker) schemecolor.com Forums Bohemia.net Bohemia Interactive Media: Changelog: v1.0.1 Fixed: Moon object missing from Chernarus Summer/Winter

Oh, dang. I was hoping that was it. Let me ping @Tom_48_97 from Tools Development Branch Changelog and cross your fingers 🤞

Hey EO, You might be running the dev branch of A3 tools. My publisher version is 1.5.148.892 from 08/03/2002 which is accurate according to https://dev.arma3.com/techrep. You are running: Hope this helps 😉 Cheers.

I truly was convinced it was the other way around! I went and took a look on my old scripts, I use functions. Disregard, functions are better! Sorry, guys! Thanks for pointing it out, @_foley.

Just my 2 cents here: use the task commands instead of the functions. https://community.bistudio.com/wiki/setTaskState

I see. It doesn't belong there indeed. Fixed above.

One: 0 = [ this,"DELAY=",300,"PAUSE=",50,"EXIT=",myExitTrigger4,"INIT="," [_proxyThis,'1','SAFE','COLUMN','LIMITED','ONROAD'] execVM 'scripts\UPSMON.sqf'; " ]spawn jebus_fnc_main; Two: 0 =[ this,"Delay=",300,"PAUSE=",50,"EXIT=",myExitTrigger4,"INIT="," {_x disableAI 'Path'}forEach (units _ProxyThis); (group _ProxyThis) setVariable ['Vcm_Disable',true]; " ]spawn jebus_fnc_main; Combined (partially): 0 = [ this,"DELAY=",300,"PAUSE=",50,"EXIT=",myExitTrigger4,"INIT="," [_proxyThis,'1','SAFE','COLUMN','LIMITED','ONROAD'] execVM 'scripts\UPSMON.sqf'; (group _ProxyThis) setVariable ['Vcm_Disable',true]; " ]spawn jebus_fnc_main; Don't use bold for scripts as it makes it harder to read certain characters and use the code (<>) from the tools to post inside a code window. Format it to C Languages. Apparently you had errors on the initial lines (one or both, don't remember already).

Oh, thanks. I should've have gone with case 0, case 1. That would've worked too.

You have a syntax error on else ( instead of { (and double [ ])but if I understand what you're trying to achieve this might be simpler (on Trigger Activation): []spawn{ switch (round (random 1)) do{ case 1:{["Bravo_1"] call BIS_fnc_advHint; sleep 1; [z_b1] call DAC_Activate}; case 2:{["Bravo_2"] call BIS_fnc_advHint; sleep 1; [z_b2] call DAC_Activate}; default{}; }; };

Just a guess, but try (re)installing Microsoft Visual C++ x64: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Related to PiR (Project Injury Reaction) by @0Y0. Ask there: Or try reinstall PiR. Unsubscribe, subscribe.

Hello, Unfortunately your syntax is wrong, check wiki: https://community.bistudio.com/wiki/forEach https://community.bistudio.com/wiki/Arma_3:_Event_Handlers#Killed It's better to use the params given in the examples on the wiki. Keeps things simple and clear for everyone. In order to use the variable _killer you need to pass it down first through params. Variable a is too vague as well as it can be easily overwritten and you should make it more explicit. { _x addEventHandler ["Killed", { params ["_unit", "_killer", "_instigator", "_useEffects"]; if (isPlayer _killer) then{a = 1}; }]; }foreach allunits;

It works here. Maybe you didn't paste outside of scope. This is my init.sqf:

He was referencing Garbage Collector and/or other commands/stuff. You can test it, kill the guy and check for group, won't delete.

He's talking about deleteGroup, not deleteGroupWhenEmpty Or better, both, but referencing deleteGroupWhenEmpty false. One is saying deleteGroupWhenEmpty false won't prevent deleteGroup from deleting it. Other is saying group will be deleted regardless what deleteGroupWhenEmpty is set. Hardly the same 😋

Not if you set this flag to false. I kinda used this before. And tested it again now. Dedmen was discussing this with Lou this week actually. (Oh My God the hour is 1337 🤣) Ye, this is false.

That's actually already too advanced for me 😁. I go alot by trial and error. I can tell you I have come across having to manually add some parameters overwritten inside some deep classes. Maybe this will explain it to you: https://community.bistudio.com/wiki/Class_Inheritance

It might just not work. But add it anywhere on init.sqf. Excluded from your code (outside scope { }).

You need the AI's names (from the editor) and then on Trigger Activation use one of these functions or the command playMove: https://community.bistudio.com/wiki/BIS_fnc_ambientAnim https://community.bistudio.com/wiki/BIS_fnc_ambientAnimCombat https://community.bistudio.com/wiki/playMove https://community.bistudio.com/wiki/Arma_3:_Moves

Try adding this outside the scope of your other script. On init.sqf addMissionEventHandler ["GroupCreated", { params ["_group"]; _group deleteGroupWhenEmpty false; }];

I don't have Old Man so I can't help you, but have you read this? https://community.bistudio.com/wiki/Arma_3:_Old_Man_Systems These could be classes inside Description.ext.

Uuh, I might have screwed that up, try deleting those previous classes. class CfgPatches { class RHSplaneFIX { units[] = {}; weapons[] = {}; requiredVersion = 0.1; requiredAddons[] = {"rhs_main", "rhs_main_loadorder"}; }; }; // RHS_A10: Plane_CAS_01_base_F and RHS_Su25SM_vvs: RHS_Su25_VVS_Base class CfgVehicles { class Plane_CAS_01_base_F; class RHS_A10: Plane_CAS_01_base_F { incomingMissileDetectionSystem = "16"; // AA sensor }; class RHS_Su25_VVS_Base; class RHS_Su25SM_vvs: RHS_Su25_VVS_Base { incomingMissileDetectionSystem = 16; // AA sensor }; };

The requiredAddons[] needs the name of the addon/pbo that has your objects, in your case would be whichever pbo it has "Christmas_Small_Box_Static", "Christmas_Small_Box_Short_Static", "Christmas_Medium_Box_Short_Static". I honestly can't tell which but looking at your Christmas Pack addons folder it is one of the Christmas_nnn.pbo files. You'll know better than me. Below I have an example where I built a composition with 3 snowman, and 1 Christmas tree. I needed the Christmas_Trees.pbo and Christmas_Snowmans.pbo to be loaded, so I added those two. The .sqe files are inside Christmas_Compositions\Christmas_Comp1 of my Kalo_Comps addon. class CfgPatches { class GE_ChristmasPack_Compositions { weapons[] = {}; requiredVersion = 1; requiredAddons[] = {"A3_Data_F_AoW_Loadorder","Christmas_Trees","Christmas_Snowmans"}; // Required addons, used for setting load order. units[] = {"Christmas_Clothed_Snowman_Hat","Christmas_Whole_Tree","Christmas_Happy_Snowman","Christmas_Happy_Snowman_Bucket"}; // List of objects (CfgVehicles classes) contained in the addon. Important also for Zeus content unlocking. }; }; class CfgEditorCategories { class GE_Christmas_Compositions // CfgGroups NATO { displayName = "Christmas Compositions"; }; }; class CfgEditorSubcategories { class GE_Christmas_SnowCastles // CfgGroups Armored { displayName = "Snow Castles"; }; }; class Cfg3DEN { class Compositions { class GE_Christmas_Composition_Castle_01 // one class per composition { scope=2; path = "Christmas_Compositions\Christmas_Comp1"; // pbo path to a folder containing header.sqe/composition.sqe files side = 8; // 0 opfor, 1 blufor, 2 indfor, 3 civ, 8 Empty/Props editorCategory = "GE_Christmas_Compositions"; // link to CfgEditorCategories editorSubcategory = "GE_Christmas_SnowCastles"; // link to CfgEditorSubcategories displayName = "Snow Castle Part 01"; icon = "\A3\ui_f\data\map\markers\nato\b_inf.paa"; // left side icon in groups list useSideColorOnIcon = 0; // 1 == icon is always colored in faction color }; }; }; PS. The sleigh with a driving wheel is hilarious! 🤣 Merry Christmas! 🎄

Open Arma without your mod, but with RHS. Go to Config Viewer cfgVehicles, find RHS_A10 and find out what it inherits from. Move RHS_A10 class inside cfgVehicles and define the class the plane inherits from, and inherit RHS_A10 from it. class CfgVehicles { class somePlane; //edit here class RHS_A10; class RHS_A10: somePlane{ //edit here incomingMissileDetectionSystem = "16"; }; };

And your own mod (cfgPatches) name?