-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No material support #3
Comments
About the material support, we could add a new "Matter" class to parse MATT chunk properties according to
Just to debug informations to Console:
Starting from this code snippet, I am testing how to setup the material nodes for:
The following script changes the shader for selected objects (it is just an example). You can test it in Blender 2.80 changing the second parameter of
|
Okay, my thoughts on this are thus: I am happy to incorporate changes to handle the I want to ensure you're aware that the I really do want to update this repo to handle newer .vox files (preferible in a catch-all style), but progress on that hasn't gotten off of note paper for several reasons. In this rewrite, I envisage a cleaner Object Oriented style, and proper separation of tasks, to allow a proper test suit. I would be keen on hearing your intentions with this MATTER class object. |
The idea is to parse materials properties (whether as new Nothing more that is beyond the importer purpose IMHO. After a quick read, the most important differences in latest VOX file format:
In concrete terms, the new "Principled BSDF" shader should be enough; for the class instead, I would say that we should follow the same philosophy of the new VOX specs using a list of material properties i.e. (key, value) pairs. ps. about Principled BSDF |
Btw, I read you already parsed MATT chunk in "Materials" branch... |
Heh, I completely forgot I had started on a new branch for it. When you lay things out like that, yeah, seems fairly easy to get implemented. Thanks for the Principled BSDF breakdown, very helpful to have everything listed out like that 👍 I am still unsure what "make them available using a Matter class to advanced users" implies. If users want to tweak away from the imported materials, they would do so in Blender, and given the materials are shared, this'd work just fine. |
I found it yesterday: I was looking for Forks/Branches. We could just start from MATT/MATL parsers, the "simplest" part, and implement more chunks then. This is not the right thread to talk about newest chunks (except for materials), but I found undocumented rOBJ new chunk in MagicaVoxel 0.99 Sorry but I forgot to add the reference for the useful screenshots: |
Debugging latest MATL chunk to Console (unsure about ascii or utf-8 encoding anyhow):
To read:
|
Materials saved in the .vox format are not processed.
The text was updated successfully, but these errors were encountered: