nusiq / mcblend Goto Github PK

Fix inaccurate typing.

Hey, I downloaded the latest zip file (3.2.0) and installed it in blender. When I wanna enable the addon, I get this error:

Add support for mirror option for bones.

Currently there is no option to set the visible bounds of the model.

The exporter currently takes the minimal and maximal UV coordinates of the 4 loops (vertices) of the face. Minecraft saves the uv for a face as two vectors (position and size) but it's possible in blender to move any vertex in any place. The user should be warned that such UV can't be accurately exported to Minecraft format.

Add the option of grouping some of the cubes together so they get the same UV map.

Add option to pretty print the output json file.

Bones that use mc_mirror have bad uv-mapping for top and bottom.

mc_is_bone isn't used anymore. This is a bug.

Even though the schema for Minecraft model says that the width and height must be an integer, Minecraft still accepts float values (they are probably rounded using floor function). Some of the models from default resource pack have integers written in float format - armor stand uses:

"texture_width" : 64.0,
"texture_height" : 64.0,

Mcblend doesn't allow importing models like that. This should be changed to fit the behavior of Minecraft.

Last version of mcblend that has working UV-mapping is v2.0.0.

Currently every bone from minecraft model creates an empty with cubes which represent the cubes. It's hard to work with model like that. There will be an option to import model with armature in the future.

• - framerate
• - world unit scale
• - creating material
• - object names
• - multiple animations

• rotation
• pivot
• origin
• size
• uv

All of these properties are optional.

Defult values:

• rotation: [0, 0, 0]
• pivot: [0, 0, 0]
• origin: [0, 0, 0]
• size: [0, 0, 0] // Makes it invisible
• uv: [0, 0]

Empty object {} is also a valid cube definition. Mcblend shouldn't break on importing and also it should insert the default values in place of the missing ones.

This one:

The mc_is_bone property is just a tag that says that the object is a mcbone. Bool values in custom properties are not supported so currently it uses the int value. Changing it to something not editable (empty dictionary, empty list or a pointer) will look better in the GUI. The mc_is_bone will be changed to just an empty dictionary.

There are no use cases for using custom parenting which is currently implemented.

"visible_bounds_offset" "visible_bounds_width" "visible_bounds_height" are optional and the lack of them should not break the importer.

Related issue #47

Currently the editor overwrites the content of the file.

It breaks when there is no:

• pivot
• rotation
• cubes

All of this properties are optional.

Default values:

• pivot: [0, 0, 0]
• rotation: [0, 0, 0]
• cubes: no value (empty list)

https://pypi.org/project/fake-bpy-module-2.82/

Title...

Add support for multiple animations.

Add keyframe data only if necessary.

Just change it to something uneditable (like a dict) and test for it's existance.

title....

The syntax for the feature is described in the schema file for models for bedrock. It's still experimental but it would be really cool to add support for that.

• export
• import

Add mirror option for UV mapping.

Add loop option to animations.

Model file size can be reduced by excluding properties with default values.

• mirror
• uv groups

It turns out that bedrock supports per-face UV-mapping. Support for that should be added.

IK bones shouldn't be exported.

Toggle mc_mirror returns the oposite message to what it should return. It shows the "Cleared mc_mirror" when the mc_mirror is set to 1 and "Set mc_mirror to 1" when its cleared.

Add an option to use object parenting of exported model into custom parenting which is already implemented in this extension.

Recent rework of UV mapping added option to use per face UV-mapping (and closed #32). Custom property mc_uv isn't used anymore which means that the importing function must be rewritten to use blender uvs instead.

Its not a bug that completly breaks the plugin because the differences are really small but it gives false alarms durign testing with github actions. Ubuntu returns slightly different results than windows even though they run the same version of blender.

Add support for minecraft model option "inflate".

It's possible to create a list property so there is no reason to keep mc_uv_u and mc_uv_v as separate values.

Add feature to generate UV mapping for the model to make creating textures for minecraft possible in blender.

If imported model doesn't define texture_width and texture_height load it with default values (like Minecraft does):

• texture_width: 64
• texture_height: 64

Solving this issue requires solving Issue #46 first. Currently Mcblend doesn't support the concept of visible bounds at all. When this will be implemented the importer should also be able to import models without defined visible bounds. Here are the default values:

• visible_bounds_width: 1,
• visible_bounds_height: 1,
• visible_bounds_offset: [0, 0, 0]

The addon internally works with quaternions but Minecraft models store rotation as Euler models. Euler angles can represent the same rotation in multiple ways which can cause problems during the interpolation between two frames of animation. The solution to this problem is in src/operator_func/common.py:pick_closest_rotation function. It looks through equivalent Euler angles and tries to pick the one which is represented by a vector as close as possible to the previous rotation.

The function tries to find the equivalent rotations in two ways:

1. Adding/removing 360 to one of the axes (which works fine).
2. Applying transformation f(v) = [x, y, z] --> [x + 180, -(y + 180), z + 180]
   and the combinations of these two.

The second way of getting the equivalent rotation sometimes return unexpected results. It's hard to illustrate that because these unexpected results are usually replaced by a better (closer) rotation created by method 1 but after some testing I created an example. It looks like additional correction is necessary for the converter to work properly.

The problem is caused by original rotation (before animation) of the bone. Only the Y-axis affects the results. It's especially conspicuous when original rotation why gets close to (90+(n*180). Adding 2 * original_Y to the Y value of the rotation after f(v) transformation fixes the problem (for cases tested so far).

Problem ilustraded in Blockbench:

1. The model - original Y-rotation is -45
   
2. Some random rotation in the 1st keyframe
   
3. Rotation after transformation and a correction Y-90
   
4. Rotation after the transformation but without the correction.
   

Add if possible...

Automate testing. You can run scripts in blender in background with ./blender.exe -b -P "path/to/your/file.py"

The plugin lacks an ability to add locators to bones.

Related issue: #51

Currently the editor writes over the content of the file.

It will work similar to normal object scaling from blender.

Recent rework of UV mapping added option to use per face UV-mapping (and closed #32). The Positions of the textures are still placed as in the default minecraft cube UV but the exporter always uses the sytax for mapping each face separately.

The 'mc_uv' custom property is not used anymore. The exporter uses the UV coordinates from UV-map in blender. The exporter should be able to tell if the UV coordinates matches the shape used by default UV.