04-03-2013, 07:38 PM
Hey gents, first post, thanks for your hospitality.
I make tactically realistic no-respawn scenarios, mainly for DCSW A-10C but also for ArmA.
I've made a good, short, SpecOps POW rescue and extraction mission that plays very well in SP and hosted MP but as Variable and I discovered this morning, it does not appear to have full functionality in a deicated server environment.
As you can see from the download link here, I've used some great scripting tools. It appears that Kylania's process for bringing the hostage under the Group leader's command using "rescuePOWs.sqf" (attached) does work with a dedi. I think the little script I used to randomise certain unit start positions also works. We determined that the following aspects do not work:
- The trigger that summons the extraction helo did not work (it uses player's proximity to the POW):
- The POW's init loadout data did not work, as he appeared fully clothed even though I put him in his skivvies in the unit's init file by removing all uniforms and equipment
- The ability to get the AI to use their laser optics by putting them in combat mode did not work even though they have the correct load out and it works in SP. The command I used in the units' init files was:
I'd like to make more missions for you guys so it would be really helpful if someone could assist me in learning how to adjust mission design for dedicated servers. Could someone take a look at the attached files (I hope I am making this very easy) and advise? Thank you!
Here is a link to the mission with the scripting links I used:
http://www.armaholic.com/page.php?id=19967
Here is the discussion page on the BI forums:
http://forums.bistudio.com/showthread.ph...-Insertion
Finally, I have attached a .rar file with the mission's .sqm file and the one .sqf file used alongside it in the mission folder. All the other scripting and adjustments are in the units' init fields and trigger fields.
As soon as you guys can help me, I will re-publish the mission with changes made (as long as dedi adjustments do not mess with non-dedi MP functionality).
Thank you very much.
I make tactically realistic no-respawn scenarios, mainly for DCSW A-10C but also for ArmA.
I've made a good, short, SpecOps POW rescue and extraction mission that plays very well in SP and hosted MP but as Variable and I discovered this morning, it does not appear to have full functionality in a deicated server environment.
As you can see from the download link here, I've used some great scripting tools. It appears that Kylania's process for bringing the hostage under the Group leader's command using "rescuePOWs.sqf" (attached) does work with a dedi. I think the little script I used to randomise certain unit start positions also works. We determined that the following aspects do not work:
- The trigger that summons the extraction helo did not work (it uses player's proximity to the POW):
Code:
player knowsAbout p1 > 0 && player distance p1 < 5
- The POW's init loadout data did not work, as he appeared fully clothed even though I put him in his skivvies in the unit's init file by removing all uniforms and equipment
- The ability to get the AI to use their laser optics by putting them in combat mode did not work even though they have the correct load out and it works in SP. The command I used in the units' init files was:
Code:
(units group player) enableIRLasers true
I'd like to make more missions for you guys so it would be really helpful if someone could assist me in learning how to adjust mission design for dedicated servers. Could someone take a look at the attached files (I hope I am making this very easy) and advise? Thank you!
Here is a link to the mission with the scripting links I used:
http://www.armaholic.com/page.php?id=19967
Here is the discussion page on the BI forums:
http://forums.bistudio.com/showthread.ph...-Insertion
Finally, I have attached a .rar file with the mission's .sqm file and the one .sqf file used alongside it in the mission folder. All the other scripting and adjustments are in the units' init fields and trigger fields.
As soon as you guys can help me, I will re-publish the mission with changes made (as long as dedi adjustments do not mess with non-dedi MP functionality).
Thank you very much.