Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glitchy Super Shotgun and more #34

Open
aorin1 opened this issue Dec 8, 2024 · 5 comments
Open

Glitchy Super Shotgun and more #34

aorin1 opened this issue Dec 8, 2024 · 5 comments

Comments

@aorin1
Copy link

aorin1 commented Dec 8, 2024

These are the wads I added to Wadsmoosh Plus
1

Every time I shoot the Super Shotgun, there's this weird cycle of sprites at the top left

Screenshot_Doom_20241208_202135
Screenshot_Doom_20241208_202218
Screenshot_Doom_20241208_202218_01

I also noticed the machine gun is sped up for some reason. There might be other glitches, but I just can't play it as it is.

Also, for some reason, a few textures are replaced:

Screenshot_Doom_20241208_200150

Many sprites seem cropped/buried:
Screenshot_Doom_20241208_200912

Screenshot_Doom_20241208_200901

This swamp "animation" cycle displays a repeated fan/vent texture and comes back again to the first frame on and on:

Screenshot_Doom_20241208_201106
Screenshot_Doom_20241208_201110

Any idea why this happens?

@Owlet7
Copy link

Owlet7 commented Dec 9, 2024

This seems to me like the natural consequence of smooshing together so many different WADs with assets that conflict and replace each other. Making them all co-exist would require a lot of work.

@aorin1
Copy link
Author

aorin1 commented Dec 9, 2024

This seems to me like the natural consequence of smooshing together so many different WADs with assets that conflict and replace each other. Making them all co-exist would require a lot of work.

Honestly, I'm having a hard time trying to understand your thought process here, as merging all the supported wads is exactly what this tool is supposed to do and, thus, create a huge DOOM campaign.
Also, one expects that all supported wads, which are read and accepted by the application (while those that aren't, are just ignored and not added at all to the merging process), were all tested previously, prior to adding them as supported files.

With all that, it's clear that something undesired is happening with the tool, or possibly with some of the wads I added, but we'd need further testing/checking to clear it up.

@Owlet7
Copy link

Owlet7 commented Dec 9, 2024

Also, one expects that all supported wads, which are read and accepted by the application, were all tested previously, prior to adding them as supported files.

I am saying that it's not the case.

@Owlet7
Copy link

Owlet7 commented Dec 9, 2024

The fact that no new ZScript code was added tells me that almost no work on resolving conflicts was done.

Essentially, I would suggest to the author to reboot the development of the tool, and only add new supported WADs after proper QC.

@aorin1
Copy link
Author

aorin1 commented Dec 10, 2024

The fact that no new ZScript code was added tells me that almost no work on resolving conflicts was done.

Essentially, I would suggest to the author to reboot the development of the tool, and only add new supported WADs after proper QC.

I get it, a few of the supported wads also come with a .deh file, does this have any influence on what's going on?

I agree that the tool needs revision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants