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
Training on Win10, RuntimeError: Could not find MSVC/GCC/CLANG #98
Comments
I didnt have the c++ development tools installed as part of Visual Studio, which I fixed now, however I keep having an error on the setting up of bias_act_plugin. Are there some further installation fixes I need to take please ? This error also happens when running the codes from Visual Studio PowerShell, with the same virtual environment.
|
Hey also having the same issue.
bias_act_plugin just fails to start up
Hope someone could help. Thanks! |
Now I have it working. Two things that help: |
I recently found that VS2019 community edition doesn't work with StyleGAN3 but VS2022 does. Alas, using VS2022 required some small changes. In case anyone above is struggling, this change might help: |
Hello,
I am trying to train Style GAN 3 on a windows 10 computer with TITAN RTX 24GB:
Driver Version: 496.76 CUDA Version: 11.5
Dependencies seem to be correctly installed (including Ninja), with Pytorch 1.9.0 with CUDA support using their wheel for past release, available for CUDA 11.1 (cf. https://pytorch.org/get-started/previous-versions/).
Regular Pytorch operations run without issues on GPU but there seem to be issues when setting up the custom CUDA operations.
Would anyone know how to fix this please ?
I am launching from terminal (Cmder emulator) inside a virtual environment using a command such as:
python D:\side_projects\microscopic_pix2pix\stylegan3-main\train.py --outdir=D:\side_projects\microscopic_pix2pix\stylegan3-main\training_runs\SGAN00_T_512px_bs32 --data=D:\side_projects\MM_Dataset\210106_Blue_Sample_Stitch_Data_SGAN512 --cfg=stylegan3-t --gpus=1 --batch=32 --gamma=8 --batch-gpu=8 --snap=10
Thanks !
The text was updated successfully, but these errors were encountered: