Creating a VoxelObject and drawing works,

After that I can't edit a VoxelObject see here:

https://user-images.githubusercontent.com/1045946/147395282-15d9951b-6b35-40dd-b04f-f92833a8f186.mp4

Using Godot 3.4.2

Begin migration to Godot 4.0. All gdscript has been (naively) translated to gdscript 2. Plugin currently crashes the editor with a stack overflow on startup, so this should probably be merged into a temporary branch.

Hello i have a rather annoying issue. After modifying things in the VoxelSet menu of an VoxelMesh such as adding/removing/modifying voxels, if i go to the VoxelObject and click on edit mode, voxel raycast or update button the voxel menu disapears. Here is a video showing the problem.

https://user-images.githubusercontent.com/56770939/121010013-233a2600-c795-11eb-82fd-2b5fba433aa3.mp4

When ever I click outside of that grey box, the window closes so I can't choose a color or add to voxel set.

I have a Mac so maybe the formatting is different.

In your examples you refer to Voxel.VoxelWorldSize. But this does not exist. (Invalid get index.)

Adding this to voxel.gd fixes it. Should be maybe variable.

const VoxelWorldSize = 0.5

Great project btw. 👍

A rewrite on the vox file importer, with minor additions, tweaks and fixes to the other importers, and voxel objects. Importer partially based on: https://github.com/jpaver/opengametools/blob/master/src/ogt_vox.h

The main new feature is the ability to fully import Magica Voxel files as scenes, while keeping all groups and objects separate. This allows for a faster workflow with Magica Voxel, skipping previously required import steps, when importing complex vox files.

This PR also fixes a missing sRGB flag on the default material, wrong forward orientation for imported voxel models, and incompatibility with newer vox files. It also introduces a new option for a per-model voxel size, and allows for more control over centering on import.

sRGB Color, and Vox compatibility example:

| Old | New | | ---------- | ---------- | | | | | | |

As seen in the pictures, the forward direction is also changed. Previously the vox importer kept Magica Voxels x axis direction, but as a result models faced backwards by default. The new importer flips the x-axis, keeping the forward direction from Magica Voxel aligned to Godots -z forward direction.

New import options, and importer:

| import options | new importer | imported vox file, with new importer | | ---------- | ---------- | ---------- | | | | |

The "Voxel Size" is now no longer global, and can be set per object. This works with voxel meshes, as well as voxel objects, and the voxel editor. A new editor option has been added, to re-scale the voxels while editing.

The new Magica Voxel Scene importer imports a vox file as seperate objects, keeping all included groups, shapes, and their respective transforms and names. Shapes are imported as Mesh Instances, and Groups as Spatials. This feature was the key reason for starting this PR, as it drastically speeds up the workflow in my current project.

Note: In it's current form this PR is a WIP. While all features I set out to add are present, it has not yet been tested thoroughly enough to be considered production ready. I would appreciate testing and feedback.

Hello,

When I build godot with this module https://github.com/Zylann/godot_voxel I get the error,

Unable to load addon script from path: 'res://addons/voxel-core/voxel-core.gd' There seems to be an error in the code, please check the syntax.

With the output being: - res://addons/voxel-core/classes/voxel_set.gd:52 - Parse Error: Non-static function "set_name" can only be called from an instance. - modules/gdscript/gdscript.cpp:583 - Method failed. Returning: ERR_PARSE_ERROR - res://addons/voxel-core/classes/voxel_object.gd:502 - Parse Error: The class "VoxelSet" couldn't be fully loaded (script error or cyclic dependency). - modules/gdscript/gdscript.cpp:583 - Method failed. Returning: ERR_PARSE_ERROR - res://addons/voxel-core/voxel-core.gd:17 - Parse Error: Couldn't fully preload the script, possible cyclic reference or compilation error. Use "load()" instead if a cyclic reference is intended. - modules/gdscript/gdscript.cpp:583 - Method failed. Returning: ERR_PARSE_ERROR

Is there any way I could fix this?

Add the ability for Voxels to define their own material attributes per face, such as metallic, roughness, emission among others

• [x] metallic
• [x] specular
• [x] roughness
• [x] emission
  • [x] energy
  • [x] color

As title says. im on a Mac on godot version 3.2.1 and voxelcore 2.0.0. I can confirm that updating a voxelcore's shader material won't save persistently however it applies it perfectly (?). And whenever I try to manually see mesh options the entire node deselects on the editor tree indicating a thread crash.

Just started learning godot (today) so maybe it'll be more obvious once I learn it, but maybe add some docs or a tutorial guide?

Doesn't need to be fancy, just a quick guide on how to do what you did in your intro video might be enough.

VoxelObject which is composed of n layers.

• Layers : Array
• Layer
  • name : String = 'layer_' + n
  • type : VoxleObject = VoxelMesh
  • data : Dictionary<Vector3, Dictionary> = {}

I would like to see support for custom meshes within voxel sets. Similar to chests/Grindstones or other special blooks in minecraft. If adding fully-custom meshes is a bit too much, I'd also find a "billboard-mode" for objects like flowers, grass, chains and so on pretty helpful.

(see demonstration below)

VoxelMesh accesses the scene tree and can cause errors while multithreading (if, for example, you want to use it for world generation).

This only happens when it's marked as static_body, and - from what I can tell - functions to make the generated StaticBody and CollisionShape save with the scene. Having a property to disable that would be nice and should be pretty simple.

I get a full crash whenever I try using VoxelObjects in my main scene. I can't seem to find any error output, so unfortunately I haven't the slightest idea why it's crashing as VoxelMesh seems to be working just fine. I will provide any logs or such on request!

First of all, love the tool, is amazing to work with.

I'm not sure if this is a bug or a technical limitation, but if you set your voxels color attribute into HDR space, when placed the color value seems to be clamped back into linear range (see screenshot below, left is voxel placed, right is the voxel placement preview rendering correctly). I haven't looked into the source code but am hoping to later this week to see if I can figure it out. Can use material emission to resolve this, but I think the raw color value workflow should also be valid, so that multiple emission levels can be used while keeping material count to a minimum, and just for convenience.

EDIT: I feel like I've made some progress, but am still bamboozled. It seems like both the placement preview cube and the voxelmesh are assembled using voxel_tool.gd using SurfaceTool, and are both setting the vertex colors correctly as far as I can tell from debugging, so I can't tell why only the preview mesh is displaying the colors properly. I was thinking it might have to do with how the material on the preview is displayed, but as far as I can tell it's setup in voxel_cursor.gd setup, and doesn't seem to do anything out of the ordinary. For now I feel like I'm at a bit of a dead end, but I'm gonna look at it some more again some other time

Voxel-Core has little to no error handling and what little there is isn't well defined. Corrections and improvements to the error handling throughout the code base are necessary.