That has something to do with how the computer stored 2-dimensional data (because the computer itself can only handle one-dimensional sequences). In MV, you need to use the full size tilesheet even if there are only a few dozen tiles on it and the rest transparent, because somewhere in the engine the calculations expect the tilesheet to be of normal size and they fail if trying to find the correct data on a smaller tilesheet.
In Ace, if you had extra slots on the tileset that you didn't need, you could simply place those snippets into the tilesheet slots and they usually worked. But usually most artists only make and distribute a few tiles each, resulting in a lot of tiny sheets of a dozen tiles or so. But the engine can get confused trying to display half tiles if your screen size is not a multiple of 32 or 48 (depending on what you set the plugin full tilesheet contains 16x16 tiles. Even if you don't need all tiles on a sheet, fill it up to full size with transparent or white placeholders.ģ) screensize should be multiple of tilesizeĭon't use a screen size that isn't a multiple of your tilesize - again a display calculation problem, although it usually works when the maps are larger. This one is new to MV, but if you are using incomplete smaller tilesheets in your tilesets, the display can go wrong. No Maker ever (that I know of) could handle maps that are smaller than the screen size without errors - it just wasn't as visible in older makers because they had a top screen size they couldn't pass.Ģ) use only full tilesheets for your tilesets If you change the screen size (especially when making it larger), you have to make your maps larger as well.
There are a few things you can try, because those have been shown to affect the display in different and strange ways:ġ) minimum map size is screen size in tiles.
0 kommentar(er)
