Add Canvas Size option under Views Menu [Solved]

[Majora101]

Location: Views Menu
Option name: Canvas Size
Option type: Radio Box (options: 3x3 (default), 6x6, 9x9, 18x18, 36x36)

Option action when enabled/disabled/clicked:
These options would allow the user to adjust the size of the yellow bounding box, or "Canvas Size" within Cubik Studio to allow for the design and exportation of larger models without the need for workarounds such as increasing the model's scale in the Preview area or placing the model on an Armor Stand in-game. From viewing several forum posts, it seems these are the primary ways to create an artificial sense of scale; these are great workarounds for held Minecraft items, such as swords or tools, but not as much for large or tall models which are implemented as placeable blocks or decoration in-game, such as: trees, building models, giraffes, etc. I absolutely love the tool, but restricting designs to the 3x3 grid is a bit limiting (I understand the design choice behind restricting the user to a 3x3 space by default in the editor). I suggest allowing the user to change the size of the bounding box from 3x3 (default) to 6x6, 9x9, 18x18, or 36x36.

[JTK222]

Not possible, that's a Minecraft limit, nothing Cubik could do to allow this ingame.

[Majora101]

Is this a new limit as of a recent Minecraft vesion? Does it affect JSON and JAVA models? Which versions of Minecraft does this affect? In the past I was able to design large 50-60 block high JAVA models using Techne (each cube's height was set to a high value, no upscaling was used) and was able to implement them as blocks and have them render in-game in builds as recent as 1.8, if I'm remembering the version correctly. Minecraft to my knowledge can display large models, albeit in a buggy way, like this example:



You can see from the design of the 6x6 Techne editor grid that models exceeding a 3x3 grid can be implemented in Minecraft:



Models can also exceed its 6x6 bounding box:

[JTK222]

This are Java Models they work completely different then JSON Models.
Basically they don't have any limitations at all (expect not allowing floats in element size and good uv mapping...).
Beside the fact that Tile Entities are worse for performance then normal blocks (all the render issues seen on your boat are easy to fix but bad for performance)) there is nothing against Cubik not allowing bigger models for anything expect vanilla models. Even though I tough that this is already a thing in cubik.

[Sphax]

Block models are probably way more optimized than Entities model in Minecraft Java (and probably in Minecraft Bedrock).

The disappearing of model in your example is valid for entities (when a block model is displayed on an armorstand, it becomes an entity) and it's due to optimization with frustum culling.

To stick to the subject, Cubik Studio 2.9 has an option to set the grid to "Large" (which is nearly infinite).