So, did Slade just mess up my .pk3?

[HeyItsDuke]

Was editing a wadsmooshed doom_complete.pk3 to add some extra maps and Slade 3 crashed. The .pk3 still works fine in GZDoom, but it crashes Slade whenever I try to open it now. Is my .pk3 messed up? Can I fix this? I would really appreciate any help at all so I don't risk losing my work. Thank you for taking the time to read this.

Edited July 6, 2020 by HeyItsDuke
Added a 3 because yes.

[JadingTsunami]

First, make backups of everything, no matter what state it is in. From this point forward, do not work on repairing or recovering anything unless it's on a copy. It's just good practice when trying to recover data.

 

Next, a pk3 is just a zipfile. If it is corrupted, you may be able to repair it.

 

First, make a copy and then rename the extension of the copy to .zip. See if you can unzip it safely. if you can, you can simply re-zip all the files to recover your .pk3 file. SLADE should (hopefully) open that one.

 

If it won't unzip, then you can try a zip file repair. You can search for "zip file repair" for some options.

 

Alternatively if you're good with the command line, you can try "zip -F" or "zip -FF" and see if either of those fixes the .zip file.

 

Good luck!

[HeyItsDuke]

2 hours ago, JadingTsunami said:

First, make backups of everything, no matter what state it is in. From this point forward, do not work on repairing or recovering anything unless it's on a copy. It's just good practice when trying to recover data.

 

Next, a pk3 is just a zipfile. If it is corrupted, you may be able to repair it.

 

First, make a copy and then rename the extension of the copy to .zip. See if you can unzip it safely. if you can, you can simply re-zip all the files to recover your .pk3 file. SLADE should (hopefully) open that one.

 

If it won't unzip, then you can try a zip file repair. You can search for "zip file repair" for some options.

 

Alternatively if you're good with the command line, you can try "zip -F" or "zip -FF" and see if either of those fixes the .zip file.

 

Good luck!

Thank you! I did have backups, but Slade borked those too. :/
For some reason, Slade is still crashing even after doing that. Hell, even after using a non modified backup and manually doing the entire modding process over again! I can't figure out what is wrong. I even completely reinstalled Slade.

 

EDIT: Here is the error that popped up right before the crash that started all of this.

Edited July 6, 2020 by HeyItsDuke
added screenshot

[Gez]

41 minutes ago, HeyItsDuke said:

What?

 

I have no idea what this means and did not even know SLADE could have such an error message. I am also surprised that "Slade Error" is not written as "SLADE Error" because "SLADE" is consistently in all-caps in the program.

[HeyItsDuke]

1 minute ago, Gez said:

What?

 

I have no idea what this means and did not even know SLADE could have such an error message. I am also surprised that "Slade Error" is not written as "SLADE Error" because "SLADE" is consistently in all-caps in the program.

Yeah, which is why I am extremely confused right now.
The even more baffling thing is that if I remod my backup .pk3 from scratch, I get the same issue. And the .pk3 still works fine in GZDoom, so it can't be corrupted. I was thinking something in Slade had to break I guess, right? So I completely wiped Slade from my PC and reinstalled it, and the problem didn't go away.

My head is literally hurting trying to figure out what is wrong.

[JadingTsunami]

9 hours ago, HeyItsDuke said:

Yeah, which is why I am extremely confused right now.
The even more baffling thing is that if I remod my backup .pk3 from scratch, I get the same issue. And the .pk3 still works fine in GZDoom, so it can't be corrupted. I was thinking something in Slade had to break I guess, right? So I completely wiped Slade from my PC and reinstalled it, and the problem didn't go away.

My head is literally hurting trying to figure out what is wrong.

 

This may sound obvious, but have you tried restarting your computer?

 

You're getting an interprocess communication error, which may mean that a copy of SLADE is still running (but crashed or in a bad state). Restarting usually clears things like that up.

 

EDIT: Btw, in this part, I just meant -- when recovering data, it's vital to only do recovery work on copies because any further corruption that might happen during the recovery effort won't hinder your ability to try again on a fresh copy of the (possibly corrupt) original data.

 

Quote

First, make backups of everything, no matter what state it is in. From this point forward, do not work on repairing or recovering anything unless it's on a copy. It's just good practice when trying to recover data.

 

Edited July 6, 2020 by JadingTsunami

[HeyItsDuke]

11 hours ago, JadingTsunami said:

 

This may sound obvious, but have you tried restarting your computer?

 

You're getting an interprocess communication error, which may mean that a copy of SLADE is still running (but crashed or in a bad state). Restarting usually clears things like that up.

 

EDIT: Btw, in this part, I just meant -- when recovering data, it's vital to only do recovery work on copies because any further corruption that might happen during the recovery effort won't hinder your ability to try again on a fresh copy of the (possibly corrupt) original data.

 

 

Yeah I did restart but the same issue stuck around. :/
I've pretty much given up and just separated my edits into a pwad. Thank you very much for trying to help me though, I really appreciate you taking the time to do that.

[Kappes Buur]

22 hours ago, HeyItsDuke said:

...

So I completely wiped Slade from my PC and reinstalled it, and the problem didn't go away.

My head is literally hurting trying to figure out what is wrong.

 

Which version of Slade3 did you reinstall?

Did you also delete or at least rename the config file before reinstalling?

You can find the cfg file in AppData\Roaming\Slade3.

 

Unfortunately some editors use a generic file name for the configuration of every revision instead of reflecting the program version in the file name. It is Slade3.cfg for all the version 3 revisions. Which means that the cfg file for an older version will be used for a newer revision, unless the file is deleted or the file name altered.

 

With a totally new installation Slade3 will automatically generate a new cfg file!

 

Give that a try, maybe it will help.

 

 

Edited July 7, 2020 by Kappes Buur

[Nevander]

That's the weirdest error message I've seen and some quick searching looks like its related to servers for some sort of reasons. Very strange and unfortunately I have no idea what could cause SLADE to give that.

[HeyItsDuke]

On 7/7/2020 at 1:58 AM, Kappes Buur said:

 

Which version of Slade3 did you reinstall?

Did you also delete or at least rename the config file before reinstalling?

You can find the cfg file in AppData\Roaming\Slade3.

 

Unfortunately some editors use a generic file name for the configuration of every revision instead of reflecting the program version in the file name. It is Slade3.cfg for all the version 3 revisions. Which means that the cfg file for an older version will be used for a newer revision, unless the file is deleted or the file name altered.

 

With a totally new installation Slade3 will automatically generate a new cfg file!

 

Give that a try, maybe it will help.

 

 

I installed the latest version (my previous one was slightly outdated) and deleted the old config file but sadly it didn't fix it.

 

On 7/7/2020 at 10:00 AM, Nevander said:

That's the weirdest error message I've seen and some quick searching looks like its related to servers for some sort of reasons. Very strange and unfortunately I have no idea what could cause SLADE to give that.

Wow, that's really strange. I have no idea what could've caused it.

[sirjuddington]

By latest version do you mean 3.1.12 or 3.2.0 beta?

 

I've seen things about that error before (something to do with how windows handles 'open with' for files) but it usually happens on startup from what I'm aware, so no idea how it would have happened during use.

 

As a last resort if you're ok with it you can send me the pk3 so I can see what exactly is causing the crash

[Nevander]

I'm thinking now something is going wrong with the PK3 specifically in SLADE and the error it's giving is bogus.

 

Try remaking the PK3 from scratch and only add one thing at a time (like sprites but nothing else), making backups along the way.