Triggers at wrong place after exporting to MP

[Coyote @ rage]

I made a training mission where two players walk through some kind of obstacle course and have targets popping up randomly.
The popping up is executed, when one of the players walks into a trigger.
Now, in order to make sure that the player inside the executing trigger has a clear field of fire, I had to place triggers and targets very carefully, and it worked out quite well in the preview.
However, after I exported the mission to multiplayer and tested it, the triggers seemed to be either at different locations or the angle of the elipses is wrong.
I had the same problem in former missions but I could be more generous with trigger placement there.

Anyone encounter the same problem and/or knows a way to place triggers exactly?

Cheers, Coyote.

[Gummi]

never had that problem, and never seen it

[Chris Death]

I can confirm this;

This happened to me while testing a mission (V 1.46)
on Zwadar's Desert Everon 2.

I've made a few large area trigger's there, to simulate
a minefield - so that if anybody enter's it, there were
a lot of "LaserGuidedBombs" exploding.

When testing this map with one or two buddies, the
trigger areas became inaccurate.

People were flying thru the air, where they shouldn't have to
do that.


I'd suggest you to use the distance command in combination
with gamelogic's or markers, to check the approach of somebody in multiplayer. It works way more accurate in
mp.

~S~ CD

[Coyote @ rage]

Guess, thatÂ's the only way, but one more ray of light:
It coulde be happening only with triggers that have an angle differing from "0".
Two triggers shaped as rectangles, same size, one with an angle of "45", the other with an angle of "225" look the same on the map, but maybe they arenÂ't in game?

[Chris Death]

Sounds interresting Coyote,

because when i got these troubles, i've been using
rectangle triggers aswell.

I'll spend some time to investigate this again (once i've
some left).

~S~ CD

[Terox]

I had this problem very recently on a 1.91 version map creation

In this particular mission
1) It was heavily laden with objects
Which i thought might have added to the problem

2) It was uploaded and tested on a linux server
(I have no idea if this has a bearing on it but thought it best to include this info

3) The killtrigger was rectangular by the way

4) Having tested it, after creating the mp pbo on my machine, the problem was not evident

However it did become evident on the server




The position of the trigger, which happened to be a kill trigger for a spawn protection zone, moved to a centralised location on the map
To the exact same location as an ambient sound trigger and its angle changed also

I got rid of the problem by removing all the triggers and starting again

In hindsight, i thought i may have grouped the kill trigger to the ambient sound trigger by accident, or in some way it had grouped itself to it

I cant confirm this, as i didnt try to reproduce the fault


It would be very interesting to see if this is a bug, or simply caused by accidental grouping of triggers

[Coyote @ rage]

Progress:

1) many objects and triggers on my map, too, canÂ't see a reason here, though.

2) uploaded, tested and found the mischievous triggers on a LINUX server!

3) killtrigger as rectangular!

4) FOR THE FIRST time, I tested the MP pbo on MY MACHINE,  --> TRIGGERS ARE DEFINETLY CORRECT!!!


No grouping of the trigger with sth. else visible in editor and i am not sure how I should check for some miraculous grouping.

Thx, Terox.

Coyote @ rage

[Terox]

Just to confirm, i have managed to reproduce the same error

Its a rectangular trigger that has migrated when uploaded to the server (Not evident when testing the pbo on my machine)


My first attempt at fixing it will be to change the square trigger to an ellipse. Will report back at the weekend with my findings

[Coyote @ rage]

Excellent, Terox, will do the same.
How did you notice a "grouping".
My maps are in a very confined area, so probalby they are grouped, and it looks to me like they just changed angle, shape, etc.

[Terox]

A further investigation of this problem has brought me to the conclusion that it is only caused by the rectangular triggers

Changing the trigger to an ellipse without doing anything else, stopped the migrating trigger problem


Changing it back  to a rectangle created the problem again



bang goes the use of square triggers

[Coyote @ rage]

You da man, Terox!

DoesnÂ't really matter, if you canÂ't use rectangular ones. Play with em dimensions a little, get about the same effect.
Maybe we oughta report it? ShouldnÂ't be too hard to fix for BIS.

[Terox]

Just a thought

The missions this became apparent on, were ones using Sebnam Pack2 on the sebnam island

Chris also ebncountered his problem on a non BIS island

I dont s'pose you was creating a mission on a non BIS island too was you?

I cant see this causing the problem, but you never know, all these little snippets of info help

[Coyote @ rage]

IÂ'll add to the mystery:

I first encountered the problem on "Winter Nogojev", and made this thread after getting it again on BisÂ' Nogova.

Maybe weÂ're looking at a version bug? What version did Nogova, Resistance, that is, update OFP to?

Cheers, Coyote.

[Chris Death]

Coyote - i don't think, we're having a version bug.

The versions, where i encountered these problems were:

1.46 - 1.30

Nogova came with 1.75 btw

~S~ CD