[BUG] Cyclops Hull Upgrades just stopped working (Build 19974)
gordon432
Scotland Join Date: 2015-06-25 Member: 205761Members
Scotland Join Date: 2015-06-25 Member: 205761Members
Hello Devs,
Freedom Mode
Build 19974
Windows 10 Pro Insider Preview
Problem:
Fitted energy upgrade + 3 hull upgrades to Cyclops but still get depth warnings at 125m and crush depth warnings at 250m (should be 800m).
Tried removing / refitting upgrades. No change.
Tried closing game and verifying game files in Steam. No change.
Tried running Ccleaner to flush memory (6 gig) etc. No change.
Tried ignoring the problem for a bit hoping it would go away. No change.
Finally tried consol spawning a new Cyclops and porting over my upgrades from the defective original. This worked. Test dives in the same area of water where the original Cyclops was failing at 125m and 250m went well. Problem solved then? No.
Inspired by my successful 'fix' I began the monotonous task of transferring 5 lockers of stuff, plus the fabricator, workbench, fragment analyser and docked Seamoth, from the defective Cyclops to my newly spawed and fully working Cyclops. Then I headed back to my Seabase docking platform (close to the pod) for a bit of locker organising prior to heading out in search of much deeper waters to explore.
I arrive at a suitable looking diving location and begin to descend. Utterly gobsmacked to get the same crap depth warnings at 125m and 250m as before!
At that point my patience was already exceeding terminal crush depth - so I logged off.
This is a game killer for me.
I have built all the other bits of kit. Have built a great wee sub docking base. Have visited the big floating island away out to the south / west end of the game. Deep water exploration is now the main motivation for playing and, due to this infuriating bug, I am unable to do that.
Can anyone save my underwater ass by telling me how to fix this? Or do I have to park the game now until the July update and hope the problem is gone by then?
Great game guys. Keep on making it better.
Onwards and upwards!
Freedom Mode
Build 19974
Windows 10 Pro Insider Preview
Problem:
Fitted energy upgrade + 3 hull upgrades to Cyclops but still get depth warnings at 125m and crush depth warnings at 250m (should be 800m).
Tried removing / refitting upgrades. No change.
Tried closing game and verifying game files in Steam. No change.
Tried running Ccleaner to flush memory (6 gig) etc. No change.
Tried ignoring the problem for a bit hoping it would go away. No change.
Finally tried consol spawning a new Cyclops and porting over my upgrades from the defective original. This worked. Test dives in the same area of water where the original Cyclops was failing at 125m and 250m went well. Problem solved then? No.
Inspired by my successful 'fix' I began the monotonous task of transferring 5 lockers of stuff, plus the fabricator, workbench, fragment analyser and docked Seamoth, from the defective Cyclops to my newly spawed and fully working Cyclops. Then I headed back to my Seabase docking platform (close to the pod) for a bit of locker organising prior to heading out in search of much deeper waters to explore.
I arrive at a suitable looking diving location and begin to descend. Utterly gobsmacked to get the same crap depth warnings at 125m and 250m as before!
At that point my patience was already exceeding terminal crush depth - so I logged off.
This is a game killer for me.
I have built all the other bits of kit. Have built a great wee sub docking base. Have visited the big floating island away out to the south / west end of the game. Deep water exploration is now the main motivation for playing and, due to this infuriating bug, I am unable to do that.
Can anyone save my underwater ass by telling me how to fix this? Or do I have to park the game now until the July update and hope the problem is gone by then?
Great game guys. Keep on making it better.
Onwards and upwards!
Comments
Try it after taking out the Seamoth. Also try diving only with the Seamoth, should emit the same warnings...
Took Seamoth out of the Cyclops and it was then able to dive to the full extent of its upgrades. Hate not having it in there though, lol. So hope they fix that bug soon.
Thank you very much for your help - much appreciated