skippy0330 Posted October 27, 2017 Share Posted October 27, 2017 so i run two dedicated, both the exact same seed ect. one server updated to 16.4 flawlessly. the other, not so much. The second server refuses to start properly. I've even tried rolling back to an older save. I get this error in console: 2017-10-27T05:12:36 8.906 INF StartAsServer ArgumentException: An element with the same key already exists in the dictionary. at System.Collections.Generic.Dictionary`2[Vector3i,PowerItem].Add (Vector3i key, .PowerItem value) [0x00000] in <filename unknown>:0 at PowerManager.AddPowerNode (.PowerItem node, .PowerItem parent) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerConsumerToggle.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerConsumerToggle.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerConsumerToggle.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerConsumerToggle.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerTrigger.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerTimerRelay.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerSource.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerItem.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerSource.read (System.IO.BinaryReader _br, Byte _version) [0x00000] in <filename unknown>:0 at PowerManager.Read (System.IO.BinaryReader br) [0x00000] in <filename unknown>:0 at PowerManager.LoadPowerManager () [0x00000] in <filename unknown>:0 at GameManager+VI.MoveNext () [0x00000] in <filename unknown>:0 at UnityEngine.SetupCoroutine.InvokeMoveNext (IEnumerator enumerator, IntPtr returnValueAddress) [0x00000] in <filename unknown>:0 anyone ever encounter this before? Link to comment Share on other sites More sharing options...
Royal Deluxe Posted October 27, 2017 Share Posted October 27, 2017 Looks like you have a corrupted file. No idea if you can fix the files by steam at your provider Link to comment Share on other sites More sharing options...
skippy0330 Posted October 27, 2017 Author Share Posted October 27, 2017 it can't be corrupted. this is a backup of the file from two days ago, and just started happening on 16.4. it works on 16.3 Link to comment Share on other sites More sharing options...
Royal Deluxe Posted October 27, 2017 Share Posted October 27, 2017 Looks like the installation dont like the Electricity save file Not sure which file this was , power.dat maybe Maybe try to run it after you delete the file. (Should delete all wires) Link to comment Share on other sites More sharing options...
skippy0330 Posted October 27, 2017 Author Share Posted October 27, 2017 oh dude! i was just thinking that. going to give that a run Link to comment Share on other sites More sharing options...
skippy0330 Posted October 27, 2017 Author Share Posted October 27, 2017 update - that worked. didnt even lose wires either! Link to comment Share on other sites More sharing options...
Nyx Posted March 1, 2019 Share Posted March 1, 2019 I'm so used to things being complicated and looking for the impossible that I did not even think that the error could be as literal as an issue with the actual power.dat file that was probably just sitting there mocking me Thanks, you saved my bacon! P.S. This issue was in Alpha 17.2 Stable release. Link to comment Share on other sites More sharing options...
SylenThunder Posted March 1, 2019 Share Posted March 1, 2019 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.