Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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
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 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.
- Kevin