Help with mapinfo bug(?)

You seem to mix the old format and the new format. In the new format it's just "cluster" (without the "def"). And I think the number shouldn't be written in quotation marks.

I couldn't say without taking some time to hunt through the source (which port are you using, by the way?) and it would help to have the whole mapinfo lump that you're testing with. But that sounds suspiciously like you could be hitting up against a hard-coded limit to the maximum number of clusters. 

43 minutes ago, meapineapple said:

I couldn't say without taking some time to hunt through the source (which port are you using, by the way?) and it would help to have the whole mapinfo lump that you're testing with. But that sounds suspiciously like you could be hitting up against a hard-coded limit to the maximum number of clusters. 

GZDoom 3.4.0

57 minutes ago, boris said:

You seem to mix the old format and the new format. In the new format it's just "cluster" (without the "def"). And I think the number shouldn't be written in quotation marks.

Tried changing it to cluster and removing quotes. Didn't work :\

On 11/5/2018 at 3:53 PM, meapineapple said:

I couldn't say without taking some time to hunt through the source (which port are you using, by the way?) and it would help to have the whole mapinfo lump that you're testing with. But that sounds suspiciously like you could be hitting up against a hard-coded limit to the maximum number of clusters. 

"26" suggested "A" to "Z" to me, as if the number was converted to a letter at some point, but it's just a guess.

If you did exactly as boris said ("cluster" not "clusterdef", and remove quotes from numbers), the issue is most likely in the relevent map definitions. We'll have to see that.

Also, GZDoom 3 6.0 is out, you should update.