-
Notifications
You must be signed in to change notification settings - Fork 4
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
Properly sync materials in realtime across MALT and BEER. #6
Comments
The dropped variables only happen when used with other layers. If I try to use it by itself as a single BEER layer, most of the options will show up but it will ignore the settings of the original Malt material. This screenshot shows the same material, the left viewed in the BEER UI, the right when viewed in Blender's Materials Property panel. |
I re-read the Readme file and the screenshot above will show partial correct settings after I click on Update BEER Material. Everything seems to break down after I add a Basic Gradient Mesh material. Steps to recreate: Add a Basic Line Mesh to a new BEER Material, set it up and click on Update BEER Material. The object will be updated with the new styles but some settings will be ignored (Receive Shadow / Self Shadow): Add a new layer and create a new material based on the Basic Gradient Mesh, set it up and click on Update BEER Material, this is when a bunch of variables from the first layer will be dropped and all settings from both layers are ignored. |
Some properties are improperly loaded (such as gradient maps), and the materials inconsistently synch - next revision should address both points. The malt material editor doesn't feed back to the layers as you've noticed. The next revision will allow you to edit the material properties in realtime from the BEER menu and optionally hide the MALT menu properties for BEER specific materials. The beergen# prefix is used for variables to prevent any issues parsing, with the # corresponding to the layer. Being able to rename the layer directly and using that as the prefix makes sense - it currently names itself using the attached material. Thank you very much for raising these issues! It's super helpful to reference. Hopefully these should all be addressed within the week. |
I noticed that when I try to use a Malt material that uses global variables that aren't referenced in some type of get method, these variables are dropped in new BEER materials.
All of these global variables show up as settings to be edited in a Malt material:
But are dropped in BEER Materials when used in a layer:
Unrelated, it would be cool if we had some way to rename the prefix used for the material settings (beergen1, beergen2, beergen#) don't offer much context as to what layer the settings belong to.
Edit:
I just noticed that all of these variables show up in alphabetical order in both Malt and BEER so maybe that's why it's prefixed the way it currently is?? if that is the case could a different label be used like beerlayer# or blayer# or even better blayer#__layername, (can layers be given names?) (edit: i think i should be able to edit the name via the UI layer panel but double clicking to rename does nothing)
The text was updated successfully, but these errors were encountered: