Can Anyone Help Me Here?

[ForeskinJohn]

Long story short, im trying to use obsidian to generate a boom compatible megawad for use with prboom+, yet no matter what compatibility i build the wad for, whether its vanilla, limit removing, boom compat, or even prboom compat, i get this same error, or the same error with a different code behind it. what is going on here, when searching this error i get only one related result on google for some reason. is obsidian just not meant for use with prboom?

[Murdoch]

This should be in editing, not general.

 

Clearly sprite related shenanigans going on. Have you tried doing anything with custom sprites in your WAD?

[Obsidian]

10 minutes ago, Murdoch said:

This should be in editing, not general.

 

Indeed it should. And yeah, as far as I can tell this doesn't have to do with the map generation itself. If you post the wad in question we might be able to more easily discern the problem.

[Murdoch]

1 hour ago, Obsidian said:

 

Indeed it should. And yeah, as far as I can tell this doesn't have to do with the map generation itself. If you post the wad in question we might be able to more easily discern the problem.

 

Yes it's definitely not the map itself. Something else is going on with either the OP's WAD, or perhaps a resource pack he's using.

[dasho]

This is a case of Oblige's original design of Doom 1 being treated as an extension of Doom 2 biting us in the ass. We have substitution tables for Doom 1 to account for the Doom 2 materials and things that it doesn't have, but this doesn't work in all cases and results in the above error. If I had my druthers, Doom 1 support would just be dropped because it doesn't really bring anything special to the table as far as map generation goes.

Edited February 24, 2023 by dasho

[dasho]

I think I've stomped out the remaining material/thing issues as of this commit. You'll have to sync up with the repo or wait for the next update of the Stable download package, though. Either way, you'll want to do a CLEAN install, not overwriting the same directory, to ensure it's being tested properly.