Mahid Sheikh

Here's some demos I uploaded on Mastodon a long time back (not much has changed though): - [Basic demo](https://cdn.masto.host/mastodonart/media_attachments/files/111/233/777/869/555/782/original/b05bad2270ab792d.mp4) - [PBR Demo](https://cdn.masto.host/mastodonart/media_attachments/files/111/327/393/633/923/100/original/c6cdcb7e375388a3.mp4)

> We can either treat this as a feature branch, or try to merge parts of it at a time until the UI side is fully ready. I think the...

> What is your thought on finding a way to mark a material to work for specific blocks/materials, vs working as the template for all of them? I could imagine...

Also, the code is ready for review, not sure if I mentioned that earlier

Alright, since it seems like Vivy builds for the most part without errors, I'll move Vivy from a build-time option to an experimental feature (which I believe would make Vivy...

To avoid conflicts, I propose we merge this initially, and then make features such as the simplified UI and ability for user-defined paths separate PRs. That way, this doesn't become...

So a slight change in UI philosophy: although it was proposed to make the Vivy UI act closer to sync materials, I feel that it would be redundant (why have...

Basic concept of the Vivy config editor. This is without refinements, and I haven't yet implemented the ability to apply changes, but I think this basic idea should work for...

Alright basic config editing. This is in the same location as the Vivy node tools https://github.com/user-attachments/assets/7a7896fb-2bee-465f-a199-c70f42bdd920

I've now implemented basic custom path support. For now, this will only be one file, since multiple files would require some more in-depth work with regards to importing materials