Hello,

I am not able to look too deeply into this at the moment, but I would be interested to hear if this problem is occurring on any other courses.

One thing that comes to my mind is if the way the way the ships moving is triggered makes any difference, for example using On Course Loaded vs. On Hole Started.

- Kevin

I have been through several iterations of testing. I think I have tried both. The course in question actually has examples of one or the other or both in other holes, and these work in multiplayer for the joiners as well as the host or in solo play. Feel free to play it and check it out in the editor. Thanks.

Just now was able to test this. I was able to reproduce it, but unfortunately wasn't able to determine any reason why those specific groups aren't syncing properly.

Everything I could see from my debugging indicated that they should be syncing. It's not an issue of complexity, as the group with the dolphins was also not syncing, and that is a very simple group (I also deleted most things from the ships group with no luck).

The only thing I learned was that the problem lies with those existing groups specifically. I could add new objects with behaviors to the same hole and they were synced properly. I ungrouped the dolphins group and made a new group, and the re-made group synced properly.

So yeah, I'm unfortunately at a loss for this one. The only workaround I can give is to ungroup the problem groups, and then re-group them, and remake the behaviors.

- Kevin

I recall a few things now. I had in fact ungrouped and regroup this and another new hole in my later versions (the latest I have now made public) and this did not work for me. However the editor had crashed a few times; once when going into test mode and the other while saving / exiting the editor.

I think the file must be corrupt somehow, as the same issues still occur when I made blueprints of some holes and placed them into new holes of a new course. The course is now public and is called Transference.

I think there must be corruption in files associated with the holes. I think will try remaking these holes from scratch and see what happens.

More info: I had used Mysterious Island workshop files instead of Maker files (by deleting my Maker files after publishing to the workshop), meaning that I didn't just build directly onto one Maker file. Maybe going back & forth using Workshop files and resultant Maker files during the interims created a file corruption.

Thanks for trying to solve this puzzle. I seem to have a rare gift of finding impossible bugs in games.

OK, I made two replacement holes from scratch in a new test course. The problem persists. At that point I just removed the animations from the two original holes in Mysterious Island. The new file is Mysterious Island v. 2.0, which actually has several improvements otherwise. Thanks.

That is so odd. I'll try to take a look at this again soon and see if there is anything I missed.

- Kevin