charliereddog

I'm having some issues with a trigger I have set up on a task which works perfectly on my local machine when hosting a mission, but does not work on a dedicated server. The task is to take 4 water tanks to a village, and the trigger simply detects whether they are within 30m of the point required. I have checked that the count command is correctly picking up the objects on the dedicated server via server debug and it is. I am tearing my hair out with this. As I said, this works flawlessly on my machine when I host and test, but on the dedicated server it does not work. Please point out my obvious mistake.

This doesn't appear to work for me on a dedi server. Changed the allegiances fine, but the waypoints were not copied.

I usually use server only for task synced triggers but in fairness they are usually simple !alive tank type stuff and they seem to work without needing to be on individual clients. AFAIK tasks are not local. True. Because it is synced to the task status being completed. As I noted originally, this set up works when I host the mission myself. True. I will add some code to the trigger to check it is not triggering silently. I'm not sure about the locality issue. If I add water tanks to the required area via Zeus when using the dedicated server and use the expanded debug for the server, I can see the result of the count is the same for the server, the HC and my client machine.

As I'm sure they'll be looking forward to an apology for suggesting they have done anything without the requisite permission...

Ok. Update. I'm a clown. DAC works fine in my mission without a HC, (albeit fps is around 5 but who needs frames right). Turns out I was spawning DAC on the server despite thinking I wasn't , and the HC migration was changing the locality and therefore units were stopping moving later on as the locality changed. Once I'd sorted my code out to do what I thought it was doing in the first place, DAC ran successfully on a 24hr soak test last night. Of course all the AI vehicles and helicopters ran out of fuel but baby steps. I think I can sort that via config_events, but having seen a couple of references to the same problem in DAC3 for ARMA2 I don't see a posted solution. I'm still getting an odd marker error thrown at the end of the DAC initialisation, I say odd because I've got markers set to off...

Lol. The documentation is more a user guide. It's not documentation of the code. Sadly :( We've just set the same mission running without a HC and will check to see if DAC has stalled when I get home. If so then it points to a problem with the way our HC works. If not, well I guess we are back to square one.

Do you mean on an engine level? I've not changed any of the scripts except to add a couple of corrections and to spawn my own compositions for camps. Nothing which touches the scheduled environment.

We are using a HC because we are using a lot of units. (200+ east groups and 100+independent groups.) The code for migrating to HC is our own clan specific so I can't comment on other set ups etc. It's entirely possible that the issue is down to what you say, however I'm not convinced it is because DAC functions perfectly for a while before falling over. However there is nothing in the rpts to indicate any errors (except a DAC marker error which seems meaningless) nor any obvious link. Sad to say but I suspect I'm going to have to write my own basic DAC. I can't wade through 160 odd uncommented and undocumented sqf to try to work out what the problems could be. I'm just not that competent.

And it's just happened again. Mission was running for about an hour and then boom. Everything stopped moving. I deleted most of the units and some respawned at camps, but it crapped out again shortly thereafter and even deleting those didn't respawn again. Looks like DAC is no longer stable enough to do what I want it to do which is a massive shame as I used to love it back in the day and I'm desperate to move away from ALiVE.

Any chance of adding the roads to the sat image so they don't fade out in Zeus and from the air?

Lots. But the units themselves were RHS.

Code changes still need a bit of tweaking. Some of the original code is not great and camps are being generated on top of each other... However, I ran a large scale test yesterday with 30 odd players and while everything started fine, after about an hour of playing the AI stopped moving and building back up when players got in range. Anyone else encountered this before?

Hi guys. Sure. I'm just trying to finish up my code changes. Sadly DAC camps tend to spawn in what personally I consider unsuitable places at the moment so I'm likely going to have to tamper with that routine too. Will hope to get it finished up this weekend.

After a bit of messing about, I've managed to get DAC to spawn a composition as a camp, along with a mortar and consider that unit as part of DAC for the purposes of calling in Arty support. This means being able to do away with the god awful camp config entirely and just use normal compositions which for me is a hugely useful change.

Oh pants. That's a shame. I was hoping to mod it to use compositions instead of the god awful camp config... :( Guess I'll have to do more drastic modifications to the code than I'd anticipated.

If a camp is just a logic ie an empty camp, can it still fire arty support?

Thanks @delta99, I've got it working OK. There's a few things I'd like to change, for example the camps are just urgh to set up, would be much better to use a composition like ALiVE or something similar. Shame it's not being updated and continued to be developed. With the license as it is no one else can touch it either, except for personal tweaks.

So what's the current status of this? Still supported? Do I need to trawl through the thread to find errors/bugs which need manually changing? Is headless client now sorted ?

Just checking this out as a possible alternative to ALiVE for some missions. Has anyone tried updating it to spawn the editor groups, rather than individually created groups from configs? Seems a rather tedious and roundabout way of doing it.

Having spent some time creating a mission that featured lots of preplaced units and waypoints with waypoint activation syncing to triggers and other waypoints, I was less than thrilled when putting it on my unit's dedicated server with HC's to discover that it didn't work as expected thanks to the way that HC's are implemented. Now I imagine I can overcome the initial "go" with a public variable and condition in the first waypoint, but how do I deal with the more intricate methodology needed for get out/transport unload etc? Our unit heavily uses zeus for our operations and I'm trying to premake the missions so that all the zeus needs do is trigger an action, not have to plonk down units, set waypoints and what have you all in real time. For example one of the triggers had 3 chopper crews, 6 squads mounting up, flying in formation and landing and disembarking with the choppers flying off. That's quite a lot of stress for a zeus, especially as they may be trying to deal with other things as well at the same time. Ideas gratefully received.

I'm getting really frustrated with this game. I thought the whole point of the 3d editor was to make it easier to do stuff IN THE EDITOR, and not have to fart around with scripts etc. However, I've resigned myself to having to do so, but there are few accurate and up to date tutorials around any more, and while the BIKI might be fine for developers and those who know this stuff, it's nigh on useless to me. Can someone please help with what I'd have assumed would be a simple requirement. All I want to do is the following: 1) Create a starting task for all players. 2) Complete that task when all enemy in an area are dead. 3) Create a new task and assign to all players to go to a radio tower and blow it up 4) Complete that task when the tower is dead. 5) Create a new task and assign to all players to go to an airfield and destroy two aircraft. 6) Complete that task when the two planes are dead. I don't want the tasks created in 3 and 5 to be visible until the prior tasks are completed, I don't want the players to have any indication of what is coming next. (this is one of my current problems with in-editor setup) Of course I want this to be MP safe, JIP compatible and if you could explain in words of one syllable that would be marvellous... :) Thanks.

And thank you. With that example I can finally see what I did wrong. (which was not syncing the task create modules to the previous task completion trigger).

Thanks for this. I've used a bit of your script to make a bunch of AI wounded that my team have to deal with and then evac. Appreciate that this isn't the direction you were going, but do you by any chance know how to create patients that you can't wholly revive, but that you just have to stabilise? I don't want to have to deal with a bunch of AI suddenly running about, I just want my players to have to stabilise and move the living into a Medivac.

Dude. I didn't say the triggers didn't work. I said the usage of them didn't fit my need which was to not have all tasks visible from the outset. You didn't provide a working example either.

I'm not going to argue with you. I found a solution I'm happy with. It wasn't yours. It is all good.