[1.0.3+] "Total Meltdown Remake" not loading maps

[NightFright]

Two of Aterbust's "Total Meltdown Remake" maps from 2017 refuse to load in Raze.

Errors during loading:
E5L1: Found lonely Sector Effector (lotag 0) at (-44800,54656)
E5L4: Found lonely Sector Effector (lotag 0) at (-2528,-6912)

Tested with:
Raze v1.0.0pre-127-gdca964444

Maps load fine in EDuke32. I have extracted the affected maps and attached to this post for testing purposes (without any needed .art, they just have to load).

[sinisterseed]

Well, since you mentioned it, does it rely on any EDuke32 specific extensions for these two maps by any chance?

For comparison, Rednukem/DukeGDX/WT would probably be more suitable, if they load fine in either of those.

[NightFright]

(Reference to another bug report, not meant for this one.)

[Graf Zahl]

Do you have a download link to the full Total Meltdown mod?
I only know that one full of EDuke32 features which surely does not work on Raze.

[NightFright]

It should be here. I am not aware of it being intended for EDuke32 only, and its con files load just fine in Raze. The old forum thread is here, btw.

[Graf Zahl]

I made the error non-fatal, it still looks like a map bug, though.

[Dynamo]

How many purely eduke32-related features are used in the TC by Fox, anyway? Surely nothing like TROR or particularly complex con code, considering it's meant to emulate a 1997 product...

[Graf Zahl]

If you mean the one referred to in the first post - I don't think there's anything. The only issue was these 2 bogus sector effectors that trigger a fatal error from the original Duke code that does not need to be fatal if the sprites are properly dealt with.

[NightFright]

I think he rather means the full conversion released by the EDuke32 team a while ago. This here is just an imitation attempt while the other is a 1:1 conversion using original data and imitating bugs. It's using a lot of EDuke32 code IIRC.

[Graf Zahl]

Yes, it heavily depends on EDuke32. It was already broken 0n 0.6 to such a degree that it was one of the deciding factors to go back to the roots with Duke's code.