Jump to content

Recommended Posts

Posted

Okay, I know this is going to sound strange, so don't start off thinking I'm nuts... Here's the deal... If I create a mission in the mission editor that has triggers like "If Group in Zone" then "Activate another group", the triggers work fine when I run the mission from the computer that built the mission. However.... If I send this mission to another user or to a different system to run as a server, the triggers don't work. They will work IF I change the trigger from "If Group in Zone" to "If UNIT in zone" but not if I use Group.

 

It is like this in 2.0, 1.5, and I believe in 1.2...

 

I have tested this by sending the mission to 2 users in our community and had them run the mission. I am told by the guy who runs our server that he has had this problem since the beginning and that everytime he builds a map that he must use UNIT conditions if he expects it to work in the server system (where the mission was not built).

 

What the heck? :crash:

HawgDawg4life of MSFlights.net

 

[sIGPIC][/sIGPIC]

Posted
Okay, I know this is going to sound strange, so don't start off thinking I'm nuts... Here's the deal... If I create a mission in the mission editor that has triggers like "If Group in Zone" then "Activate another group", the triggers work fine when I run the mission from the computer that built the mission. However.... If I send this mission to another user or to a different system to run as a server, the triggers don't work. They will work IF I change the trigger from "If Group in Zone" to "If UNIT in zone" but not if I use Group.

 

It is like this in 2.0, 1.5, and I believe in 1.2...

 

I have tested this by sending the mission to 2 users in our community and had them run the mission. I am told by the guy who runs our server that he has had this problem since the beginning and that everytime he builds a map that he must use UNIT conditions if he expects it to work in the server system (where the mission was not built).

 

What the heck? :crash:

 

Yep had this issues years ago, was told along the lines in MP there is no such things as groups as far as trigger system goes, you must use UNITS, crazy I know, so it sounds like it hasn't changed.

Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV).

 

DCS Tech Support.

Posted

Is this confirmed, does anyone of you had this issue ? Could be really poblematic for the camapign i am trying to release....i always used part of group, never used unit, even because unit inside zone sometimes doesn't work for me....:shocking:

Posted

Confirmed, PART OF GROUP IN ZONE not working for client aircraft in multiplayer in 1.5 at the moment (at least not for me either.)

 

I feel your pain re: conversion; I used to use GROUP IN ZONE as well and had to shuffle a LOT of triggers around in a few of my missions.

 

As far as I know it is a server side/client side issue and not related to the computer the .miz was built on.

Posted

SP or MP

 

So it is related to server slots, i guess in SP with only 1 plane assigned to player it won't happen...i hope...

Even because i say this again in my mission editor UNIT INSIDE ZONE doesn't work, i must use GROUP...:huh:

Posted

Works fine in MP on the machine I created with

 

So it is related to server slots, i guess in SP with only 1 plane assigned to player it won't happen...i hope...

Even because i say this again in my mission editor UNIT INSIDE ZONE doesn't work, i must use GROUP...:huh:

 

No No, this works fine on the system that I created the mission on. EVEN in multiplayer. I can run multiplayer and everything is fine, but only on the system the mission was created on. If I transfer it to another system, its screwed.

HawgDawg4life of MSFlights.net

 

[sIGPIC][/sIGPIC]

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...