diwako

Hah, damn yeah I see I forgot to correct one setDamage. I will fix this real quick and push a hotfix on github. Script updated to v1.5.1 Changelog: -Fixed Electra damage without ACE medical enabled Download: https://github.com/diwako/stalker_anomalies

Are you running the latest version? The only anomaly that has lights to it is the electra one.

That error is really weird. have you tried restarting the game? The init.sqf and description.ext look fine. you sure you have put them into the right mission folder?

Do you also execute this "[] call anomaly_fnc_init" ? If that does not help then check if you also added these parts to your description.ext. class CfgFunctions { createShortcuts = 1; #include "scripts\funcs.hpp" }; class CfgSounds { sounds[] = {}; #include "sounds\sounds.hpp" }; If you did not, add this to your description.ext and reload the mission into the editor.

No worries, got you covered. Let's say you want to spawn some anomalies, in my case I put them near a freedom base. Place down some hidden markers, let's call them "freedom_anomaly_electra_1", "freedom_anomaly_electra_2", "freedom_anomaly_electra_3" etc Place down a trigger, size is of your choosing. Type: None Activation: Any Player Activation Type: Present Tick Repeatable Tick Server only Put this in the activation field (set the higher number to the number of your markers) freedomAnomaly = []; for "_i" from 1 to 5 do { freedomAnomaly pushBack ([getMarkerPos ("freedom_anomaly_electra_" + str(_i))] call anomaly_fnc_createElectra); }; Put this in the deactivation field [freedomAnomaly] call anomaly_fnc_deleteAnomalies;

Bolt throwing is now in. If you have ACE mounted it is in self interact -> equipment. If you are not using ACE it is a scroll wheel action Changes for 1.5: -Bolt throwing has been added -fixed actions disappearing upon respawn when not using ACE Download: https://github.com/diwako/stalker_anomalies

I cannot give you a code example right now, but here is the general run down Place invisible markers around an area you want to fill with anomalies. Name them what ever you want,. but they have to have the same start and a different number at the end, example: "loc_anomaly_1", "loc_anomaly_2", "loc_anomaly_3" and so on Place a trigger which is repeating and server only and activates if any player is present. Up on activation create a an empty global array. Create a for loop and iterate over a number beginning with 1 and ends with the last number of your placed down markers. Create anomalies based on the markerposition (see getMarkerPos) and add them to a global array (see pushBack). Up on deactivation of that trigger just call the delete anomaly function with the global array as parameter This should be relatively easy to do.

A system like this is not implemented or planned so far. In my own mission I am currently using a system which spawns in and out anomalies on a fixed location marked with a marker. I might implement something like this for future use, but this won't happen for at least 2 months. Right now my focus is in adding bolt throwing and fixing existing code before adding some new feature.

Just pushed an update before I have to leave for 2 weeks and cannot work on anything. So please let me know if you find something that is not working correctly. Changes for 1.4: -Added Zeus Ares/Achilles support -Added feature to delete anomalies -General nil exception fixes -fixed players not taking damage without ACE medical present -reduced cool down time for all anomalies -added feature to check if an item is present in a units loadout (used for anomaly detector) -anomaly detector feature can now be set up to require an item present in a units loadout. Can be set in init.sqf. empty string means no item needed. Download: https://github.com/diwako/stalker_anomalies And a sneak peek for an upcoming feature. Right now it is too buggy to be included. https://i.imgur.com/eGhYFql.gifv https://i.imgur.com/u8bYVpD.gifv

Thank you, Normally there should be support for damage without ACE enabled. I also have taken a look into the code on why that might happen. Turns out it is a rookie mistake, really. I will be doing an update some time later with more then just this fix. For now you can look into scripts\anomalies\ and open up the sqf files starting with "fn_activate". In there just search for (!isNil "ace_medical_fnc_addDamageToUnit") And edit the else case from e.g. _x setDamage _dam + 0.5; to _x setDamage (_dam + 0.5); Right now the error seems it is applying the units current damage to itself again and does not add to it. Putting brackets around that should apply it. If not feel free to tell me, as I currently have a a lot to do in real life I have little time right now to work on this project. On a side node. I also have started to work on a stalker mission in my little free time and could gather some interesting ideas and use cases out of it. Next update will contain some bug fixes and new features like Zeus (with Ares/Achilles) support, being able to delete Anomalies, and some tweaks to cool down times to anomalies.

Just pushed an update: Added a small showcase in mission file Added vehicle support! Fixed missing script file to spawning springboards Vehicle support is now in! It is based on what kind of vehicle and how heavy it is. Examples: A tracked vehicle driving into a burner will not lose its tracks, but a wheeled vehicle will. Both vehicles will take some engine damage because of the heat. A vehicle weighing more then 10 Tons will not be thrown away by a springboad, but a lighter vehicle will. Teleporters will only teleport vehicles weighing less then 10 Tons. Electras will disable a vehicles engine temporary and damage the engine in the process. Lighter vehicles will be sucked into a Meatgrinder and receive hull damage. Heavier vehicles will not be affected by the Meatgrinder. Meatgrinder sucking in an M-ATV: https://i.imgur.com/cIIhZ9O.gifv

Not really fond of uploading scripts to the workshop as it is not a mod. In order to upload a script to the workshop you'd need to put in a mission and then upload the PBO to it. Imo it is annoying to get the pbo and then extract it, just to get the script. Sure it will help with exposure, but this script really isn't beginner friendly as it uses compiled scripts rather then scripts being called via execVM or precompile at mission start. Of course you can correct me on this, but for now I do not really want to use the workshop because of what I just said and my plans on refactoring scripts for next update.

Ease of use and teleport anomalies are using CBA's hashmap internally. Right now, with all the anomalies added I wanted in the first place, I will be revising and refactoring some code now. And I will be using CBAs "currentUnit" functionality to add zeus support and remote controlled units. Normally I would do all that with the "ace_player" object, but I want to remove ace form the requirement list. So, I need to recreate the flame particle effects at some point. Besides, CBA really became something that is run along side Arma when playing multiplayer or with mods. Well, at least for me.

Pushed an update: Added Teleport anomaly Create methods now return just created trigger Next step will be code revisions and refactoring, Maybe bolt throwing and respawn support after that. Some Media: https://i.imgur.com/C84EIBI.gifv https://i.imgur.com/eEBL8Zb.gifv

Just pushed an update Added burner anomaly Sprinboards now have idle sounds Anomaly particles are now rendered according to your camera position and not your player position (for zeus and spectator support) (respawn support is still not in ¯\_(ツ)_/¯) Some small bugfixes here and there

I get the memory leak pretty consistently when playing with a group. Here's the dump and dxDiag file. No rpt since I forgot to re-enable logs. http://www.diwako.net/zeug/Arma3performanceLeak-19-02-17.7z

I did a lot of digging around, in the end I started over and tested it on my server after even just placing one unit. Turns out I kind of found the problem. RHS units are completely fine and will not make your server crash or even trigger the CfgWeapon.Burst error. However if you place nearly anything from the CUP_Weapons mod, you will get the CfgWeapon.Burst and forcing the server back to the mission selection screen. The CfgWeapon.Burst error originates from RHS, they even went ahead and said in their support ticket that it will be fixed and it seems that RHS is not affected by crashes because of it and it's the another mods fault. Thing is, CUP alone on the server does not do this, only if RHS is included. Right now the fixes are, do not use CUP_Weapons (this includes static weapons) or spawn it in via script during mission time or do not use RHS. It is possible that even any other weapon mod that uses that class will trigger it. So far my mission is still not running even after removing everything from CUP_Weapons, seems NIArms is also affected by this. I will have to wait for RHS to get their shit together and release a hotfix. Knowing their update speed, it might take a month.

Hey, First I do want to apologies if this is the wrong section for this and I should have posted it in the Mission & Editing forums. I've recently gotten an issue that I cannot start my mission on my groups dedicated server on Linux anymore. It just kicks me back into the mission select screen. Then upon restarting the mission again the server crashes with a SEGV Fault. I've been searching the internet left and right for the issue, went through the whole RPT file, read up on the feedback trackers on certain mods that we use. Nothing, this is kinda the last turn I can do before either deleting the whole mission or start over from scratch. And since it is an ongoing campaign mission, I'd rather not do that. So here some information: Mods used are: CBA ACE CUP Terrains CUP Weapons and Units RHS, every mod NIArms (Formerly known as HLC Weapons), Core and AK pack Task force Radio My group is using the Profiling Branch Server. In the RPT there is a lot of spam from "No entry 'bin\config.bin/CfgWeapons.Burst'.". This is from the RHS Mod, according to their bugtracker it does not cause this weird behavior. Another thing I noticed in the bugtracker is "Ref to nonnetwork object *some id*: dummyweapon.p3d", but according to the BI Wiki it can be ignored. I went ahead and just started deleting bases and outposts, then at some point it all worked again, but no indication really what the issue was. So from this I know it is a map object causing all this. The main problem is, I have placed quite a lot of objects so no idea which are the offending ones. I am testing these things now on my local dedicated windows server which resulted in a very similar behavior and uploaded the RPT until it kicks me back to selection screen. Link to RPT I also uploaded the non-binarized mission.sqm. Link to Mission.sqm I am at a loss here, can someone help?

Might found a bug with setFriend. Wanted to make a mission in which the allegiance with the independent side will turn sour during the mission, noticed that units running the AI who already saw the Players while they were still friends will not attack the Players once setFriend is used. EG: West and Independence are friendly, player moves up to the AI. Set friend is used right in front of the AI like this: independent setFriend [WEST, 0];WEST setFriend [independent, 0] AI will react like it has seen an enemy, take cover, flank and all that. But they will not shoot. Otherwise really digging this AI, great work.

Sent you the mission files. Also one note, I am adding ItemRadio to loadouts as a test, since it didn't work before.

Yes, I take a guess that the loadout did get applied after the player received a radio. The weird thing is, I am not removing any items other than uniform, weapons, backpack and vests when applying the loadout.

Hi there, Just registered here since I could not find a solution to my problem anywhere. I am customizing the loadouts of players in my missions and noticed when ever I apply the loadout on spawn or respawn the default A3 ItemRadio does not get replaced or rather only on some loadouts with its counter part from TFAR. Is there a way to add the radios manually? So far I've only found the longrange radio item names, but never really from the personal radios.