• Search
  • 🍪 Blender Basics Explore Library Podcast Educators: Blender Teaching Guide What's Coming Soon Upgrade your membership
  • Blog
  • Search
    • Full Library
    G

    Experimenting With Procedural Texture Generation — I’d Love Your Feedback!

    Dávid Gligor(GligDav)

    EDIT: originally, I forgot to add the short demo video that shows the basics of using the tool, so here it is:

    Hey There!

    I’ve been tinkering with a little side‑project lately, and I think some of you might find it interesting — especially if you enjoy procedural workflows, texture creation, or just exploring weird technical experiments.

    A couple of weeks ago I had one of those “wait… what if?” moments.

    The idea was simple: Could we approximate a raster texture automatically using a combination of procedural textures?

    I started experimenting, and after many tests (and many crashes), I now have a very early prototype that actually works well enough to share.

    It’s not magic, it’s not production‑ready, and it’s definitely not fast — but it’s a start.

    If you’re curious, you can check out the prototype on GitHub: GligDav/ProcTexLab. Clone the repo, follow the install instructions, and you’re good to go.

    This is very much a “baby’s first steps” situation, so here are some honest notes on what you should expect (and not expect):

    • Performance is rough. Even with GPU acceleration (CuPy), fitting a texture can take minutes or hours. If you plan to import results into Blender, keep the settings low.
    • The Blender addon is fragile. It breaks easily. I’m actively working on stabilizing it.
    • "Blurry" results are expected. This is an approximation tool — many raster textures simply can’t be recreated 1:1 with procedural building blocks.
    • Crashes and bugs will happen. It’s early research, not a polished tool.

    Since this community is full of artists and technical creators, I’d love to hear what you think:

    • Would you use a production‑ready version of this?
    • Do you see potential in the idea?
    • What would you change or improve?
    • Are there use cases I might be overlooking?

    Even a short comment would help me understand whether this project is worth pushing further.

    🙏 Thanks for taking the time to check this out!

    I’m excited to hear your thoughts — whether it’s “this is cool,” “this is weird,” or “here’s how you could make it better.”

    — Dávid

    1 love
    Reply
    • Martin Bergwerf replied

      Hi Dávid,

      Sorry, but that's way above my head.

      I tried reading the README and after the Installation part, you say; "It opens fullscreen by default; press Escape to leave fullscreen or F11 to toggle it." After that you lost me. That's full of technical terms and I don't even know where to place them. For instance atoms are mentioned, but are those chemical atoms or something else? 

      This seems to be one of the simpler explanations: "Maximum nonlinear optimizer iterations for each proposed atom." I understand every word, but still have no idea what it means.

      There's a Blender Addon, but I don't know what it does, how to use it and what for.


      2 loves
    • G
      Dávid Gligor(GligDav) replied

      Hey Martin,

      Thank you for the feedback, and I'm really sorry if the UI and the description of it feel overwhelming. My goal was to give a proper explanation of what the different things do and how they influence the final result. I've noted this, and I will pay attention when developing the production ready version to simplify the UI (and the documentation).

      BTW, there is a demo video showing a basic flow of the tool, which I forgot to include in the post (shame on me), I hope it helps a little bit!

      1 love
    • Martin Bergwerf replied

      Oh, the description didn't feel overwhelming, just incomprehensible. Let me be clear: I don't even know what a raster texture is.

      1 love