Limits and "d:" in the data

[fizzyade]

Hi, I've just discovered this utility and I'm trying to import data into it from my existing data, this means generating the necessary JSON and so on.

The first issue I seem to have hit is there being an X limit of 4096 pixels, changing it in the GUI always clips it to 4096., is there really a limit of 4096?

The second image is the "d" field that states it's an internal only field, but, I have to add this field into the data on import because otherwise LDtk won't accept the file, as this seems to be nothing more than (tile y/tile height) * (tiles in x) + (tile x/tile width) why doesn't LDtk generate this field on import if it's missing?

Thanks

[fizzyade]

To answer my own question....

The limit seems only to be when creating data inside the application, if I edit the JSON and change the width & height to values over this, everything works fine.

For background, I'm hitting this problem because I'm using data that is ending up in a mega drive game and as such, I have a tile size of 8x8, but the actual structure in formatted so that the hardware can directly render the data from ROM.

The second part with "d:", it would be nice if this field was generated if missing rather than LVtk failing to load the JSON.