tahno
Zealot
- Joined
- Mar 3, 2015
- Messages
- 657
- Reaction score
- 494
okay so
I went on S2 today and I roleplayed for the initial few hours, everything was going smoothly and such. I spawned in a dupe for the control panel room by the yellow gate, and I recently added a few new props to it.
The server crashed, I went afk for a bit after that and returned to the server and tried respawning the dupe from earlier. Then I got this message when I tried accessing the file on the advanced duplicator list.
I've tried going off and on gmod, I relogged from steam, disabling and enabling addons, and then I restarted my computer. None of those worked in stopping the error. The same outcome appeared when I attempted to open other files on my set.
Has anyone else stumbled upon this problem? And if they have, did they find a solution to it? I've checked the discussions on steam workshop and other gmod-based forums, and most of them didn't have promising outcomes (like the file for the dupe becoming corrupted), so I'm slightly concerned. Although someone mentioned that they experienced a similar glitch, yet it eventually halted.
I went on S2 today and I roleplayed for the initial few hours, everything was going smoothly and such. I spawned in a dupe for the control panel room by the yellow gate, and I recently added a few new props to it.
The server crashed, I went afk for a bit after that and returned to the server and tried respawning the dupe from earlier. Then I got this message when I tried accessing the file on the advanced duplicator list.

I've tried going off and on gmod, I relogged from steam, disabling and enabling addons, and then I restarted my computer. None of those worked in stopping the error. The same outcome appeared when I attempted to open other files on my set.
Has anyone else stumbled upon this problem? And if they have, did they find a solution to it? I've checked the discussions on steam workshop and other gmod-based forums, and most of them didn't have promising outcomes (like the file for the dupe becoming corrupted), so I'm slightly concerned. Although someone mentioned that they experienced a similar glitch, yet it eventually halted.