#reassign and #restart commands

[MessiahUA]

Have any of you notice, that if you are using #reassign or #restart, server become very unstable, JIP bugs appear (when two persons control one soldier) and finally it may just crash.

This was an issue in all versions of server. I'm just curious, when this commands will be fixed?

[raedor]

Which version are you using? I did not see these bugs yet (in 1.02 and 1.05).

[MessiahUA]

Currently I'm using 1.05, but I just automatically write #missions, because in 1.01 and 1.02 I had this weird problems with restarting or reassigning mission.

[Sickboy]

Currently I'm using 1.05, but I just automatically write #missions, because in 1.01 and 1.02 I had this weird problems with restarting or reassigning mission.

We had the same problems for 1.01 and 1.02. I havent tried it in 1.05 yet, used to using #missions now everytime too :P

[MessiahUA]

I havent tried it in 1.05 yet

I tried reassign in 1.05, but when I saw same symptom of this problem (when you have same people in different role slots), I came up with the conclusion, that this problem is still there. That's why I've created this topic.

[Suma]

I can confirm #reassign causes problems - we just recently tracked the "shared control" down to this (cf. http://bugs.armed-assault.net/view.php?id=1781). I am not sure about #restart yet.

[MessiahUA]

Thank you, Suma, for you reply. It's really great to see BIS team answering here on our questions .

I hope, that everything will work in 1.06.

[fasad]

I have noticed that when playing CTI in the demo (5116), voting for restart would cause a lot major desyncs a short time after the mission restarted, especially if the initial mission had been running for a long time. Voting for the missions and selected the same mission prevents this problem.

[Foxhound]

Have any of you notice, that if you are using #reassign or #restart, server become very unstable, JIP bugs appear (when two persons control one soldier) and finally it may just crash.

This was an issue in all versions of server. I'm just curious, when this commands will be fixed?

#restart has caused more troubles for us than #reassign did (after a #restart we would just keep hangin in the briefing, and if the admin decided to go back the players were kicked including the admin ).

Anyway, great to see you are already working on how to fix this.
I hope it can be resolved in the next patch, often server visitors are annoyed by these probs and leave

[CouchMonkey]

I can confirm, those two commands cause issues that result in server instability. It has been that way since 1.02 (for us anyways) and is till an issue now. We just use the #missions command to get around that.