Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HQ Items do not get moved to new position #11

Closed
JohnnyDeeee opened this issue Jul 29, 2017 · 2 comments
Closed

HQ Items do not get moved to new position #11

JohnnyDeeee opened this issue Jul 29, 2017 · 2 comments

Comments

@JohnnyDeeee
Copy link

JohnnyDeeee commented Jul 29, 2017

My setup:

  • Latest arma 3 game/server version
  • Dedicated server (setup using TADST)
  • Client running on the same pc as the server
  • Antistasi (LordGolias edit, master branch) running on Altis
  • Default mission parameters

What happend:

During the creation of a new game, the following happend
HQ Items do not get moved to the new position (2) (Petros + campfire do get moved). If i tp back to the 'initial' starting position (1) the items are still there.

(1), (2): See screenshot for position locations
hn5drqhssfyw7kno3qmogg

If i run the 'maintenance options -> reset HQ' the items do get reset to the right position (i think because it just moves them near Petros..)

There are no errors inside the .rpt log that have something to do with this issue.

Steps to reproduce:

  1. Start a dedicated server
  2. Load the Antistasi mission (Altis)
  3. Choose 'new game'
  4. Choose a location
  5. Notice the HQ items did not get moved to your new location
@JohnnyDeeee JohnnyDeeee changed the title HQ Items do not get moved to new position [Dedicated server] HQ Items do not get moved to new position Jul 30, 2017
@JohnnyDeeee
Copy link
Author

Created a pull-request for a potential fix: #14

LordGolias added a commit that referenced this issue Aug 1, 2017
Thanks to @JohnnyDeeee for reporting, identifiying the error and proposing
a solution. This is just a simplification of that.
LordGolias added a commit that referenced this issue Aug 1, 2017
Thanks to @JohnnyDeeee for reporting, identifiying the error and proposing
a solution. This is just a simplification of that.
@JohnnyDeeee
Copy link
Author

Not able to reproduce with the current state of the master branch.
I guess it is fixed then?

LordGolias added a commit that referenced this issue Aug 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants