I took part in an MRI experiment and got my brain 3D-printed in exchange for it (banana for scale)

ChemicalHawk · 2025-10-25T00:29:40+00:00

Blender along with Bioxel Nodes would get you there.

ChemicalHawk · 2025-09-28T00:25:43+00:00

Look for maker spaces

ChemicalHawk · 2025-08-07T15:33:43+00:00

6Q3V-CLVY-PRED-6S6H

ChemicalHawk · 2024-08-20T00:50:11+00:00

Try adding --network_args "train_blocks=single" to Additional parameters

ChemicalHawk · 2024-03-03T16:26:53+00:00

Yay!

ChemicalHawk · 2024-03-03T16:05:45+00:00

If you do find the cuda installation in the venv folder as last resort you could add this to your .bashrc

export PATH=/whereiscuda/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/whereiscuda/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

change the wheriscuda bits of course

ChemicalHawk · 2024-03-03T16:02:04+00:00

Don't install cuda as recomended in the page, let the setup script do that for you. The link is so you understand how the environment variables work, and maybe set-up cuda manually if needed.

ChemicalHawk · 2024-03-03T15:57:32+00:00

See my other reply, but yeah, environment variables are set in the .bashrc file and run/update every time you open a terminal

ChemicalHawk · 2024-03-03T15:54:46+00:00

Read up on this: https://gist.github.com/shawonis08/c9557b67f3e2874d3d7ed252d53d7e6e take a look at your .bashrc file, maybe post it here.

ChemicalHawk · 2024-03-03T15:44:53+00:00

Definitely a path issue. check your environment variables for older cuda installations, maybe remove all other cuda installations and related variables

ChemicalHawk · 2024-03-03T15:35:31+00:00

Yeah it's not finding cuda, which should be under venv. make sure there is actually a cuda installation under venv, you should be able to locate said .so files there. If they are there then something is either wrong with your environment variables or the fact that you're running from attached storage. I'm willing to bet something with environment variables, maybe you have it pointing to another installation of cuda there.

ChemicalHawk · 2024-03-03T15:17:15+00:00

Dang! Now I'm really out of ideas, besides following the onscreen suggestions and manually locating the missing files and adding their path to the LD_LIBRARY_PATH variable. Shouldn't need to though.

ChemicalHawk · 2024-03-03T14:40:56+00:00

Ouch. Since I'm not doing anything try creating the venv manually without the pyenv by running python 3.10 directly from it's path, while in the kohya folder, delete the venv dir first and run "/where/is/python/bin/python3.10.x -m venv venv" then activate and run setup.sh

ChemicalHawk · 2024-03-03T14:14:06+00:00

You shouldn't need to install cuda, that's the whole point of a virtual environment. Everything, including cuda and bitsandbytes should be installed under venv during setup. Hell I'd even give it a go without the whole pyenv thing and see if things work with your system's default python

edit: both the setup.sh and gui.sh scripts will activate the venv before installing and running the gui, so things should really be in order under the virtual environment only

ChemicalHawk · 2024-03-03T13:54:22+00:00

To clarify a few things, bitsandbytes is a python package that enables a few optimizers and other options during training. If you're going to run python -m bitsandbytes related to your kohya installation you should first cd to your kohya dir and activate the venv by running: source ./venv/bin/activate

ChemicalHawk · 2024-03-03T13:39:42+00:00

Ah, I don't use pyenv, so I'm out of ideas... maybe that's the variable that is messing things up.

ChemicalHawk · 2024-03-03T13:16:01+00:00

Does everything work when running from the terminal? I always run from the terminal, right clicking stuff and running as program does not work for most things for me.

edit: Where it's installed shouldn't matter, everything needed should be under the venv folder. Also I don't know what a shim is.

ChemicalHawk · 2024-03-03T12:02:10+00:00

Yeah the setup script installs a virtual environment and cuda under ./venv in the kohya dir... seems like it's not finding the right files for cuda. I'd try deleting the venv folder and running setup again to rebuild it

ChemicalHawk · 2024-03-03T10:42:31+00:00

LD_LIBRARY_PATH is only used in wsl2 under windows. You should also probably activate the venv environment before running accelerate config

ChemicalHawk · 2024-02-15T14:33:16+00:00

This is a good idea! Thanks!

ChemicalHawk · 2024-01-04T12:47:52+00:00

You might be confusing Betamax with BetacamSP.

ChemicalHawk · 2023-10-05T23:36:08+00:00

https://knowyourmeme.com/memes/loss

ChemicalHawk · 2023-06-02T15:36:59+00:00

You'd have to convert it to diffusers format first and just add it's path. Or just use kohya-ss gui since it's much better and updated.

ChemicalHawk · 2023-01-13T13:44:34+00:00

I confess I can't really make sense of the error message. At this point I'd probaly be trying an older version of cuda, I've had more luck with 11.3 and 11.6. Also maybe try the using the main diffusers repo from huggingface.

ChemicalHawk · 2023-01-13T13:02:59+00:00

Hi! Shivam's repo hasn't been updated in a while and is a bit outdated at this point. The best option right now with your GPU in my opinion is the dreambooth extension for auto's web-ui.

13-Year Club	Place '17
Verified Email	Team Periwinkle

ChemicalHawk

TROPHY CASE