Jump to content
Bohemia Interactive Forums

whiztler

Member
 View Profile  See their activity

  • Content Count

    547

  • Joined

  • Last visited

  • Medals

Everything posted by whiztler

  1. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    New mega links added.
  2. whiztler

    [MP CO37 Campaign] Two Sierra

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    @Aplion Thanks for the heads up. New link is up in the op.
  3. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Vehicle crew. But have implemented it for all framework spawns
  4. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Still have no idea. Added a forced "allowDamage true" after each spawn which solves it.
  5. whiztler

    [MP CO37 Campaign] Two Sierra

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Updated to version 1.11. See OP for download information. Version 1.11 Fixed: Invulnerable vehicle gunners. Updated: Performance improvements. Updated: 2sierra_readme.pdf ReadMe document. Updated: Applied ADF 2.22 framework.
  6. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Updated to version 1.73. See OP for more information and download links Changelog version 1.73: Fixed: Invulnerable vehicle gunners. Updated: Performance improvements. Updated: Applied ADF 2.22 framework.
  7. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 2

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Updated to version 1.73. See OP for more information and download links Changelog version 1.73: Fixed: Invulnerable vehicle gunners. Updated: Performance improvements. Updated: Applied ADF 2.22 framework.
  8. whiztler

    Function call after Respawn

    whiztler replied to MFiveASP's topic in ARMA 3 - MISSION EDITING & SCRIPTING

    I recon the unit is still a null object. Add: private _timeOut = time + 5; waitUntil {!isNull _unit || time > _timeOut}; Before your loadout call.
  9. whiztler

    Marker on top of other marker

    whiztler replied to Taylor1984's topic in ARMA 3 - MISSION EDITING & SCRIPTING

    I use a re-marker script to recreate a marker (always is on top of other markers): ADF_fnc_remarker = { ////// ["myMarker"] call ADF_fnc_remarker; params [ ["_oldMarker", "", [""]] ]; // Check marker if !(_oldMarker in allMapMarkers) exitWith { diag_log format ["Marker: '%1' is not a valid marker or does not exist", _oldMarker]; }; // Store marker data private _name = _oldMarker; private _position = getMarkerPos _oldMarker; private _type = getMarkerType _oldMarker; private _colour = getMarkerColor _oldMarker; private _shape = markerShape _oldMarker; private _dir = markerDir _oldMarker; private _size = getMarkerSize _oldMarker; private _text = markerText _oldMarker; private _alpha = markerAlpha _oldMarker; private _brush = markerBrush _oldMarker; // Hack due to bug in ARMA3 if !(_type isKindOf "CfgMarkers") then {_type = "";}; if !(_shape in ["ICON", "RECTANGLE", "ELLIPSE", "POLYLINE"]) then { _shape = "ICON"; _type = "hd_dot"; _colour = "ColorUNKNOWN"; _text = "Marker Error"; }; // Delete the marker deleteMarker _oldMarker; // re-create the marker on top of the object markers private _newMarker = createMarker [_name, _position]; _newMarker setMarkerType _type; _newMarker setMarkerColor _colour; _newMarker setMarkerShape _shape; _newMarker setMarkerDir _dir; _newMarker setMarkerSize _size; _newMarker setMarkerText _text; _newMarker setMarkerAlpha _alpha; _newMarker setMarkerBrush _brush; // Return the new marker _newMarker };
  10. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Which mission is giving you issues? Can you share the RPT log? I see no reason why #restart shouldn't work. Seems more like a server issue to me. But you can always try #missions and select the mission from there.
  11. whiztler
    Did you name the soldier? If not than name the soldier, e.g. unit_01. In your script you can then delete the waypoint: deleteWaypoint [group unit_01, index];
  12. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    All patrol functions call upon "core/fn_addWaypoint.sqf" (ADF_fnc_addWaypoint) to create the actual waypoint(s). Tbh I never had the need for waypoint timeouts in my missions hence why I haven't added the option. I might add it to the next ADF release.
  13. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Quite a few of the ADF functions have been updated. Had some issues with the AI skill application so deactivated it. Besides that it is mostly optimization.
  14. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 1

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Updated to version 1.72. See OP for more information and download links Changelog version 1.72: Updated: Reverted all AI skill to default skill. Updated: Most mission scripts for further performance improvement. Updated: Applied ADF 2.20 framework.
  15. whiztler

    [MP CO15 Campaign] Wolfpack Vol. 2

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Updated to version 1.72. See OP for more information and download links Changelog version 1.72: Updated: Reverted all AI skill to default skill. Updated: Most mission scripts for further performance improvement. Updated: Applied ADF 2.20 framework.
  16. whiztler

    [MP CO37 Campaign] Two Sierra

    whiztler replied to whiztler's topic in ARMA 3 - USER MISSIONS

    Updated to version 1.10. See OP for download information. Version 1.10 Fixed: Attempt to fix the occasional invincibility of OpFor. Updated: 2sierra_readme.pdf ReadMe document. Updated: Applied ADF 2.19 framework. Note I received several reports that OpFor is very difficult to kill and sometimes require 10+ hits for them to go down. From a mission maker point of view this seems due to a change in config of body armor etc. Since my missions do not alter any unit config, the only other possible explication was the skill set changes. Although it does not seems logical, it is the only setting that is applied in both Two Sierra and Wolfpack missions that alter behaviour of OpFor. I have removed any skill set/behaviour changes and kept everything as Vanilla as possible. Please let me know if this clears-up the invincibility issue of OpFor units.
  17. whiztler
    From the wiki waitUntil:
  18. whiztler
    I prefer the ZBE_Cache script over the BIS engine solution. The fact that it does not cache the leader of a group make real-time simulation much more realistic. See you in a few years 😁
  19. whiztler

    Client Owner and remoteExec

    whiztler replied to ZaellixA's topic in ARMA 3 - MISSION EDITING & SCRIPTING

    Perhaps posting the code regarding your query will give us some insight in your issue. Also when testing in MP my advise is to actually start an MP session. TADST is a great tool for this, a tool I use as well. https://forums.bohemia.net/forums/topic/101123-tophes-arma-dedicated-server-tool-tadst/
  20. whiztler

    Attacth TO nearEntities

    whiztler replied to Barba-negra's topic in ARMA 3 - MISSION EDITING & SCRIPTING

    Have a look at the forEach command. It lets you execute a command on items in an array (which your list of objects is)
  21. whiztler
    Perhaps explain a bit what how the issue starts. You hide objects using the module and place another object in its place in Eden? It should work. Perhaps you can test an alternative route by hiding the object and then spawn another object in its place using a script (https://community.bistudio.com/wiki/createVehicle).
  22. whiztler
    You can (temp) 'freeze' a unit by disabling the simulation. In case of Eden, put the following in the init box of a unit: this enableSimulation false;
  23. whiztler
    On the addWaypoint wiki page you can se two icons on the top: AG global -- A stands for Argument - Arguments of these scripting commands (AG) don't have to be local to the client the command is executed on. EG global -- E stands for Effect - Effects of these scripting commands (EG) are broadcasted over the network and happen on every computer in the network. So when you have a command with EG Global, the effect is seen by everyone, no matter who executes the command. In most cases it is best to execute these commands on the server or a headless clients.
  24. whiztler
    You can terminate code by checking the alive state of a unit: if (!alive MyUnit) exitWith {};
  25. whiztler
    Do not execute Global commands (such as hideObjectGlobal) on all clients. The init.sqf is execute by all players, (dedicated) server, headless client(s0, etc. When you use the global version of an engine command the information is communicated over the network to each connected entity by each connected entity. Causing a lot of network traffic. In case of hideObjectGlobal it can only be executed by the server. So you need to move the code from your init.sqf to the iniServer.sqf file in you mission root. If you do not have a initServer.sqf in your mission root then simply create one. Alternatively you can let the server execute the code in your init.sqf: if isServer then { }; Your code would then look something like: if isServer then { { _x hideObjectGlobal true; } count [bag_1, bag_2, bag_3, bag_4, bag_5, bag_6, bag_7, bag_8, bag_9, bag_10, bag_11, bag_12, bag_13, bag_14, bag_15, bag_16, bag_17, bag_18, bag_19, bag_20, bag_21, bag_22, bag_23, bag_24, zu3_3, zu3_8, zu3_7, zu3_6, zu3_5, zu3_4]; };
×