![]() There was nothing on it or under it but it could only turn in circles and would not ascend or descend, only tilt slightly and would not move forward. And much to my confusion, the Cyclops got stuck on nothing. I want to finish the achievements so I will not spawn another cyclops or seamoth.I launched up my Subnautica file tonight to try to get some farming done a bit before bed. If that moved, did the seamoth moved too and caused it to disapear? Then I checked this forum and after reading that it was not a seamoth bug but a cyclops bug I remembered that there was another glitch that may be related, the top of the cyclops has some gear that now is floating to the side of it. That's when I noticed that the second seamoth was missing and was reluctant to build another one if they were going to keep disapearing with this bug. I went back to the first base to build another seamoth and discovered that the missing seamoth icon was still active, went back and the icon was inside the island, below where the seamoth had disapeared, so I figured it was a glitch and decided to use it as a marker or maybe wait to see if it kept sinking and recover it latter and continued exploring deeper sites with the cyclops. I finally built my cyclops and I went to test drive it and went to the floating island, I had the seamoth docked and took it to go to the island, low on food and water I made a mistake and the seamoth ended on the island, I went to the base to get the food and water and when I returned to figure out how to get the seamoth back to sea, it was gone. I don't know if all this is related, but it's what happened to me. If this seems written awkwardly, whenever I write a bug fix or workaround I try to use as many keywords as possible so anyone searching for my solution can find it easily later. I have renamed my old one to ghost cyclops and sunk it to the bottom in a trench with all the lights off. For now, I cannot get a Seamoth explosion or disappearance to occur in my new Cyclops. ![]() Still testing though, will determine later if this fully fixes it. Meanwhile, completely stripped of all construction, and all items removed, the old cyclops still blows up a seamoth. So far testing indicates the new cyclops will NOT cause a seamoth issue or bug, both virgin, and with all my old construction such as storage lockers and plant pots moved. Have not tested with a second constructed cyclops, only a console spawned one. With luck the new cyclops should be free of the glitch. Then hit f3 again, escape again, and ~ key. If you have an explode or disappearing seamoth in cyclops hit f3, escape, and click the disable console commands button in the upper left corner. Apparently the cyclops construction itself can bug out and make a cyclops that explodes a seamoth. Apparently the issue is in the construction of the Cyclops itself. The issue is NOT with the Seamoth like many assume. Here is my post talking about it on the steam bug forums:Īfter testing, a workaround / bug fix to seamoth exploding / disappears when in the cyclops bug in subnautica has been discovered by me. ![]() After testing today, it turns out the issue is the cyclops itself. The issue with creating a new Seamoth or a new console spawned one is that mine would just explode again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |