Quick MAPINFO question

[Reisal]

I am using the code below for MAPINFO for a new map in development but the automap remains the same, what needs to be altered?

map MAP14 "Occam's Cinema"
next MAP15
sky1 SKY2 0
par 600
music D_DDTBL2

[Kappes Buur]

You really should use the new MAPINFO format as the old format is deprecated.

map MAP14 "Occam's Cinema"
{
  levelnum = 14           //  levelnum = <levelnum>
  next     = "map15"      //  next = "<maplump>"
  sky1     = "name", 0.0  //  sky1 = "<texture>", [scrollspeed]
  sky2     = "name", 0.0  //  sky2 = "<texture>", [scrollspeed]
  doublesky
  par      = 600          //  par = <partime>
  music    = "D_DDTBL2"   //  music = "<musiclump>"
}

http://zdoom.org/wiki/MAPINFO/Map_definition

Mr. Chris said:

... but the automap remains the same, ...

Do you mean that the automap for map15 is the same as for map14 ?

[Gez]

Mr. Chris said:

I am using the code below for MAPINFO for a new map in development but the automap remains the same, what needs to be altered?

map MAP14 "Occam's Cinema"
next MAP15
sky1 SKY2 0
par 600
music D_DDTBL2

First, what port and what version?

For the rest of the post I'm going to assume ZDoom. I've copy-pasted that in a "mapinfo.txt" file, loaded it, and map14 had for automap name Occam's Cinema.

So the problem isn't in the MAPINFO lump; or at least not in this code.

Do you:
-have a dehacked lump which changes level name strings?
-have a zmapinfo lump?
-mix old and new syntax in the same mapinfo lump?
-have any warning message in the console?

[Reisal]

Gez said:

First, what port and what version?

For the rest of the post I'm going to assume ZDoom. I've copy-pasted that in a "mapinfo.txt" file, loaded it, and map14 had for automap name Occam's Cinema.

So the problem isn't in the MAPINFO lump; or at least not in this code.

Do you:
-have a dehacked lump which changes level name strings?
-have a zmapinfo lump?
-mix old and new syntax in the same mapinfo lump?
-have any warning message in the console?

I am using the latest Skulltag development version for my main ZDoom derivative port, there is no DEHACKED lump, no ZMAPINFO, don't know if I'm mixing new and old and no yellow or red errors while loading the map for testing.

ZDoom 2.5.0 doesn't change over the mapname in console either for some reason.

Here is the file for inspection to see what am I doing wrong with the lump.

[Gez]

I don't see any form of MAPINFO lump at all in the map.

Also, those VINTAGEx BMP images? Convert them to PNG or something.

All I can say is works for me.

[Reisal]

That was just weird, and the images were BMP for limit removing compatibility ports.

[Gez]

Mr. Chris said:

That was just weird, and the images were BMP for limit removing compatibility ports.

I don't know of any port that displays BMP. Some do display PNG, though -- including Skulltag, ZDoom, GZDoom, Vavoom, Doomsday, GLBoom+, and in the future Eternity.

I can guarantee you that neither ZDoom nor Skulltag will display BMP. The format is deliberately unsupported.

Finally, "limit-removing" refers to mapping limits, not to anything to do with supported image formats.

[Reisal]

Do paletted PNG files work normally for ZDoom's software mode?

[Gez]

Yeah, they do.

For any color in an image format with its own colors, it'll try the closest match. If the colors are inside the game palette, the closest match will be an exact match and everyone is happy.

The only issue with PNGs in the Doom (or whatever other game is modded) palette is that translations are not reliable. If you want to apply palette translations, you have to use the Doom picture format or flat format.