UMAPINFO prevents PrBoom+ v 2.5.1.7 from starting?

[ViolentBeetle]

I'm trying to make episode selection work for the first time using UMAPINFO.

 

map MAP01 {
	episode = clear
	episode = "EPISODE1", "Occipital Onslaught", "1"
	levelname = "1. Skullgate Central"
	label = clear
	levelpic = "CWILV00"
}

// map MAP11 {
// 	levelname = "11. Cold Blood"
// 	label = clear
// 	levelpic = "CWILV10"
// }

map MAP12 {
	episode = "EPISODE2", "Everything is Ruined", "2"
	levelname = "12. Ruins"
	label = clear
	levelpic = "CWILV11"
}

// map MAP20 {
// 	levelname = "20. Cybertemple of Cyberdoom"
// 	label = clear
// 	levelpic = "CWILV19"
// }

map MAP21 {
	episode = "EPISODE3", "A Flesh Start", "3"
	levelname = "21. Fallen Dimension"
	label = clear
	levelpic = "CWILV20"
}

With this code, I'm unable to start the wad at all in 2.5

The problem seems to be "episode = clear" line. However if this line is not included, it messes up presentation of episodes in 2.6

But with this line, 2.5 the game simply refuses to move past difficulty selection. Is there any way to reconcile it without needlessly making it incompatible with older versions of PrBoom+?

 

It seems I can actually start it on Nightmare, which has an extra confirmation so I guess something screws with difficulty here?

 

UPD: Problem version is 2.5.1.7 - I found out it's important

Edited July 25, 2021 by ViolentBeetle

[JadingTsunami]

52 minutes ago, ViolentBeetle said:

I don't require it, it works fine if not supported.

I'm concerned that one version supports it in such a way that game breaks.

 

Optimizing for one buggy version that now exists in the middle of the version history of the port strikes me as odd. I would expect "upgrade to the latest" is a reasonable request given you would have updated your port as recently as mid-2019 to support UMAPINFO at all.

 

At any rate, unfortunately the answer to your question is no: what you want to achieve is not possible. You are encountering a known bug that was fixed in later revisions of the port.

 

Your choices would be to include a "2.5.1.7um compatibility" version of the WAD, drop your "episode" definitions, drop UMAPINFO support, tell users to supply a "-warp" command when launching with 2.5.1.7um, or only support 2.6um+.

[P41R47]

wich version of PrBoom+ 2.5 are you using?
Because only 2.5.1.7 and on are compatible with UMAPINFO
Previous versions are not compatible and not being mantained by now.

Try the code you have already, as it seems to be good mostly like the ones i made for myself, but delete the ''label = clear'' entry.
I don0t know what it does, and i don0t have it and they work fine for me.

[ViolentBeetle]

Just now, P41R47 said:

wich version of PrBoom+ 2.5 are you using?
Because only 2.5.1.7 and on are compatible with UMAPINFO
Previous versions are not compatible and not being mantained by now.

2.5.1.7

So guess it supports UMAPINFO (Makes sense, since it reads), just not correctly.

[P41R47]

Just now, ViolentBeetle said:

2.5.1.7

So guess it supports UMAPINFO (Makes sense, since it reads), just not correctly.

maybe there is an entry on that version that is not being parsed and make it crash?

Try on a 2.6 version without the ''label = clear'' entry.

I don't use it and they work fine for me.

[ViolentBeetle]

2 minutes ago, P41R47 said:

Try on a 2.6 version without the ''label = clear'' entry.

Behold, the horror!

 

How it is supposed to look (Made on DSDA version but 2.6 does the same with episode = clear):

[P41R47]

really strange, i use the following code and they work for me displaying like the second picture:

 

map map01  {
	levelname = "Gatehouse"
	levelpic = "CWILV00"
	next = "map02"
	skytexture = "SKY1"
    episode = clear
	episode = "M_EPI1", "2048 Units of /vr/", "1"
}

map map91  {
	levelname = "Vehement Onslaught"
	levelpic = "EWILV00"
	next = "map92"
	skytexture = "SKY1"
	music = "D_EXTRA1"
    
	episode = "M_EPI2", "Extra Units of /vr/", "2"

Try re-arranging the entries, maybe it order is making things go funky.

The label entry, i suppose, shows the image on the back, right?

 

Maybe thats not supported on 2.5.1.7

[ViolentBeetle]

2 minutes ago, P41R47 said:

really strange, i use the following code and they work for me displaying like the second picture:

 

map map01  {
	levelname = "Gatehouse"
	levelpic = "CWILV00"
	next = "map02"
	skytexture = "SKY1"
    episode = clear
	episode = "M_EPI1", "2048 Units of /vr/", "1"
}

map map91  {
	levelname = "Vehement Onslaught"
	levelpic = "EWILV00"
	next = "map92"
	skytexture = "SKY1"
	music = "D_EXTRA1"
    
	episode = "M_EPI2", "Extra Units of /vr/", "2"

Try re-arranging the entries, maybe it order is making things go funky.

Moving "episode" lines to where you have them didn't help.

[P41R47]

5 minutes ago, ViolentBeetle said:

Moving "episode" lines to where you have them didn't help.

I suspect that some entries are not supported on 2.5.1.7

Strange that they did not work on the  build of 2.6 for you
I downloaded a new build like 2 weeks ago and they work fine for me :/
 

[JadingTsunami]

Is there a particular reason you want to maintain compatibility with older versions?

 

The newest version is recommended as some fixes were made to the episode handling since the initial release (2.5.1.7).

[ViolentBeetle]

1 minute ago, JadingTsunami said:

Is there a particular reason you want to maintain compatibility with older versions?

 

The newest version is recommended as some fixes were made to the episode handling since the initial release (2.5.1.7).

Mostly because I'm not in a rush to update an almost 30 years old game so I don't feel like I should expect others to. I haven't downloaded 2.6 until today, actually.

I guess not supporting it would also be an option, but I'd like to explore possible solutions that aren't "Just don't support it".

[JadingTsunami]

8 minutes ago, ViolentBeetle said:

Mostly because I'm not in a rush to update an almost 30 years old game so I don't feel like I should expect others to. I haven't downloaded 2.6 until today, actually.

I guess not supporting it would also be an option, but I'd like to explore possible solutions that aren't "Just don't support it".

 

By requiring UMAPINFO, you are already doing that. PrBoom support for that is recent.

[ViolentBeetle]

Just now, JadingTsunami said:

 

By requiring UMAPINFO, you are already doing that. PrBoom support for that is recent.

I don't require it, it works fine if not supported.

I'm concerned that one version supports it in such a way that game breaks.