max polys?

[Doc]

Does anyone know if there is a fixed limit to polygons in a map?

[Mr]

5000 ones. then soldat crashes.

[iDante]

5000 ones. then soldat crashes.

Wasn't it 10k?

I just remember seeing in the mapmaker source a constant called MAXPOLYS2 or something that was set to 10k.

[jrgp]

5000 ones. then soldat crashes.

Wasn't it 10k?

I just remember seeing in the mapmaker source a constant called MAXPOLYS2 or something that was set to 10k.

For map stats, polyworks always shows the number of polygons as number/5000. So, I'd assume it's 5000.

[chrisgbk]

It's currently 5000 in the client, the map maker source is slightly incorrect.

[jrgp]

It's currently 5000 in the client, the map maker source is slightly incorrect.

In future verisons of Soldat, are you guys planning on increasing / decreasing this limit?

[EnEsCe]

Map format change.... Not anytime soon

[scarface09]

What's the map format going to be when it's changed?

[jrgp]

What's the map format going to be when it's changed?

No one knows yet...and even if the developers had a few plans, they probably wouldn't disclose them until it was really ready to be released.

[chrisgbk]

If it was changed, it most likely would be changed to a more flexible format so that changes could be added without breaking compatability; ie: floating sections:

Code: [Select]

[header: map format version]
[section header: size of section]
[section header: id]
[section data]
[section header: size of section]
[section header: id]
[section data]
...
[section header: size of section]
[section header: id]
[section data]

Where a section's data could be broken down, for example, as:

Code: [Select]

[polygon header]
[polygon data]

In this way, additions could be made without breaking compatability with parsers; sections that the parser doesn't understand can be skipped.

Note that this isn't currently planned, and if implemented wouldn't be seen until sometime around 2012 xP

[jrgp]

Note that this isn't currently planned, and if implemented wouldn't be seen until sometime around 2012 xP

Sorry, sort of offtopic but still relatively relevant: do you think Soldat will still be under active development in 2012? It'd reach it's ten year birthday then; I think Soldat's ten year anniversary would be awesome.

[chrisgbk]

Sorry, sort of offtopic but still relatively relevant: do you think Soldat will still be under active development in 2012? It'd reach it's ten year birthday then; I think Soldat's ten year anniversary would be awesome.

I'm not sure if "active" would be the best word to describe it by then, but would probably still be maintained. It definitely won't be abandoned.


As a small treat I whipped up the following code tidbit to show what maploading COULD be like in the future:

Code: [Select]

function testloadmap(filename: string);
var
  file: TFileStream;
  header: TFSM_Header;
  sectionHeader: TFSM_SectionHeader;
  polygonHeader: TFSM_PolygonHeader;
  polygonData: array of TFSM_Polygon;
begin
  // Open file for reading nicely
  file := TFileStream.Create(filename, fmOpenRead or fmShareDenyWrite);

  // Read header
  file.Read(header, sizeOf(TFSM_Header));

  // sanity check
  if header.magic <> FSM_Magic then
    raise EFSM_FileFormatException.Create;

  // Parse entire file
  while (file.position < file.size) do begin

    // Read section header
    file.Read(sectionHeader, sizeOf(TFSM_SectionHeader));

    // Check what section we're working with
    case sectionHeader.ID of
      FSM_Polygons: begin

        // Read section header
        file.Read(polygonHeader, sizeOf(TFSM_PolygonHeader));

        // Section sanity check
        if (sectionHeader.size - sizeOf(TFSM_PolygonHeader)) <> (polygonHeader.count * sizeOf(TFSM_Polygon)) then
          raise EFSM_FileSectionSizeException.Create;

        // Read section data
        setLength(polygonData, polygonHeader.count);
        file.Read(polygonData[0], polygonHeader.count * sizeOf(TFSM_Polygons));
      end;
    else
      // Skip this section
      file.Seek(sectionHeader.size, soFromCurrent);
    end;
  end;
end;

Those of you who have been here for a while might remember the Ouden project; this is the same format I suggested for the project back when it was alive. (circa 2005 or so)