vosen / ZLUDA

CUDA on AMD GPUs
Apache License 2.0
8.45k stars 494 forks source link

Issue with recent V-Ray engine runing on Sketchup 2021 #173

Open batero2000 opened 4 months ago

batero2000 commented 4 months ago

Hi! I'm having the following error messages while trying to render with ZLUDA on V-Ray 6.

14/3/2024 19:58:28 | Error | [V-Ray] Failed to initialize OptiX (check your driver version. OptiX requires NVidia driver 466.11 or later)! Error Code : 7804
-- | -- | --
14/3/2024 19:58:28 | Error | [V-Ray] [VUtils::VOptix::ContextImpl::init] 7804: OptiX failed to initialize. Error code : 7804

batero2000 commented 4 months ago

More info:

lshqqytiger commented 4 months ago

nvoptix is excluded by default. You have to build ZLUDA with zluda_rt enabled.

batero2000 commented 4 months ago

nvoptix is excluded by default. You have to build ZLUDA with zluda_rt enabled.

Can you help me with that pleaase? I don't know anything about code, I just want to use my AMD GPU to make renders.

lshqqytiger commented 4 months ago
  1. Make sure that you have satisfied the prerequisites.
  2. Clone the repository
    git clone --recurse-submodules https://github.com/vosen/zluda.git
  3. Enable zluda_rt by modifying this line:
    broken = false
  4. Build ZLUDA.
    cargo xtask --release

This will build nvoptix.dll, but I'm not sure V-Ray is available by doing this. #165

batero2000 commented 4 months ago
  1. Make sure that you have satisfied the prerequisites.
  2. Clone the repository
git clone --recurse-submodules https://github.com/vosen/zluda.git
  1. Enable zluda_rt by modifying this line:
broken = false
  1. Build ZLUDA.
cargo xtask --release

This will build nvoptix.dll, but I'm not sure V-Ray is available by doing this. #165

Thanks for your response, I'm having an issue when running the last command, I get this:

error: failed to run custom build command for `llvm-sys v150.1.2 (C:\Users\---\Escritorio\ZLUDA-master\ext\llvm-sys.rs)`

Caused by:
  process didn't exit successfully: `C:\Users\---\Escritorio\ZLUDA-master\target\release\build\llvm-sys-8ce5b24440cec93a\build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs
  cargo:rerun-if-changed=C:\Users\---\Escritorio\ZLUDA-master\ext\llvm-project\llvm
  cargo:rerun-if-changed=C:\Users\---\Escritorio\ZLUDA-master\ext\llvm-sys.rs\build.cmake
  CMAKE_TOOLCHAIN_FILE_x86_64-pc-windows-msvc = None
  CMAKE_TOOLCHAIN_FILE_x86_64_pc_windows_msvc = None
  HOST_CMAKE_TOOLCHAIN_FILE = None
  CMAKE_TOOLCHAIN_FILE = None
  CMAKE_GENERATOR_x86_64-pc-windows-msvc = None
  CMAKE_GENERATOR_x86_64_pc_windows_msvc = None
  HOST_CMAKE_GENERATOR = None
  CMAKE_GENERATOR = None
  CMAKE_PREFIX_PATH_x86_64-pc-windows-msvc = None
  CMAKE_PREFIX_PATH_x86_64_pc_windows_msvc = None
  HOST_CMAKE_PREFIX_PATH = None
  CMAKE_PREFIX_PATH = None
  CMAKE_x86_64-pc-windows-msvc = None
  CMAKE_x86_64_pc_windows_msvc = None
  HOST_CMAKE = None
  CMAKE = None
  running: "cmake" "C:\\Users\\---\\Escritorio\\ZLUDA-master\\ext\\llvm-project\\llvm" "-G" "Visual Studio 17 2022" "-Thost=x64" "-Ax64" "-DLLVM_ENABLE_TERMINFO=OFF" "-DLLVM_BUILD_TOOLS=OFF" "-DLLVM_TARGETS_TO_BUILD=" "-DLLVM_ENABLE_PROJECTS=" "-DCMAKE_PROJECT_INCLUDE_BEFORE=C:\\Users\\----\\Escritorio\\ZLUDA-master\\ext\\llvm-sys.rs\\build.cmake" "-DCMAKE_INSTALL_PREFIX=C:\\Users\\----\\Escritorio\\ZLUDA-master\\target\\release\\build\\llvm-sys-65e36a2f59a296a6\\out" "-DCMAKE_C_FLAGS= -nologo -MD -Brepro" "-DCMAKE_C_FLAGS_RELEASE= -nologo -MD -Brepro" "-DCMAKE_CXX_FLAGS= -nologo -MD -Brepro" "-DCMAKE_CXX_FLAGS_RELEASE= -nologo -MD -Brepro" "-DCMAKE_ASM_FLAGS= -nologo -MD -Brepro" "-DCMAKE_ASM_FLAGS_RELEASE= -nologo -MD -Brepro" "-DCMAKE_BUILD_TYPE=Release"

  --- stderr
  CMake Error: The source directory "C:/Users/---/Escritorio/ZLUDA-master/ext/llvm-project/llvm" does not exist.
  Specify --help for usage, or press the help button on the CMake GUI.
  thread 'main' panicked at C:\Users\---\.cargo\registry\src\index.crates.io-6f17d22bba15001f\cmake-0.1.50\src\lib.rs:1098:5:

  command did not execute successfully, got: exit code: 1

  build script failed, must exit now
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: process didn't exit successfully: `target\debug\xtask.exe --release` (exit code: 101)
lshqqytiger commented 4 months ago

Did you clone the repository with --recurse-submodules? If not, run

git submodule init
git submodule update
batero2000 commented 4 months ago

Did you clone the repository with --recurse-submodules? If not, run

git submodule init
git submodule update

I just downloaded the repository with my browser and open terminal from there. Git command doesn't work in my PC (Windows 11).

Edit: Sorry I'm such a noob, I already installed it, now I'm compiling, update soon. Thanks for your reply.

Edit 2: Nice! Now I'm getting this error message:

error: failed to run custom build command for `llvm-sys v150.1.2 (C:\Users\feder\zluda\ext\llvm-sys.rs)`

Caused by:
  process didn't exit successfully: `C:\Users\feder\zluda\target\release\build\llvm-sys-8ce5b24440cec93a\build-script-build` (exit code: 101)
  --- stderr
  CMake Deprecation Warning at CMakeLists.txt:8 (cmake_policy):
    The OLD behavior for policy CMP0114 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Deprecation Warning at CMakeLists.txt:13 (cmake_policy):
    The OLD behavior for policy CMP0116 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Warning at C:/Users/feder/zluda/ext/llvm-project/third-party/benchmark/CMakeLists.txt:308 (message):
    Using std::regex with exceptions disabled is not fully supported

  CMake Deprecation Warning at CMakeLists.txt:8 (cmake_policy):
    The OLD behavior for policy CMP0114 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Deprecation Warning at CMakeLists.txt:13 (cmake_policy):
    The OLD behavior for policy CMP0116 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Warning at C:/Users/feder/zluda/ext/llvm-project/third-party/benchmark/CMakeLists.txt:308 (message):
    Using std::regex with exceptions disabled is not fully supported

  CMake Deprecation Warning at CMakeLists.txt:8 (cmake_policy):
    The OLD behavior for policy CMP0114 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Deprecation Warning at CMakeLists.txt:13 (cmake_policy):
    The OLD behavior for policy CMP0116 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Warning at C:/Users/feder/zluda/ext/llvm-project/third-party/benchmark/CMakeLists.txt:308 (message):
    Using std::regex with exceptions disabled is not fully supported

  CMake Deprecation Warning at CMakeLists.txt:8 (cmake_policy):
    The OLD behavior for policy CMP0114 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Deprecation Warning at CMakeLists.txt:13 (cmake_policy):
    The OLD behavior for policy CMP0116 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Warning at C:/Users/feder/zluda/ext/llvm-project/third-party/benchmark/CMakeLists.txt:308 (message):
    Using std::regex with exceptions disabled is not fully supported

  CMake Deprecation Warning at CMakeLists.txt:8 (cmake_policy):
    The OLD behavior for policy CMP0114 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Deprecation Warning at CMakeLists.txt:13 (cmake_policy):
    The OLD behavior for policy CMP0116 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Warning at C:/Users/feder/zluda/ext/llvm-project/third-party/benchmark/CMakeLists.txt:308 (message):
    Using std::regex with exceptions disabled is not fully supported

  CMake Deprecation Warning at CMakeLists.txt:8 (cmake_policy):
    The OLD behavior for policy CMP0114 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Deprecation Warning at CMakeLists.txt:13 (cmake_policy):
    The OLD behavior for policy CMP0116 will be removed from a future version
    of CMake.

    The cmake-policies(7) manual explains that the OLD behaviors of all
    policies are deprecated and that a policy should be set to OLD only under
    specific short-term circumstances.  Projects should be ported to the NEW
    behavior and not rely on setting a policy to OLD.

  CMake Warning at C:/Users/feder/zluda/ext/llvm-project/third-party/benchmark/CMakeLists.txt:308 (message):
    Using std::regex with exceptions disabled is not fully supported

  thread 'main' panicked at ext\llvm-sys.rs\build.rs:103:10:
  called `Result::unwrap()` on an `Err` value: Os { code: 3, kind: NotFound, message: "El sistema no puede encontrar la ruta especificada." }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\xtask.exe --release` (exit code: 101)
batero2000 commented 3 months ago

@lshqqytiger Any ideas of how I can fix the issue above? I still can get it to compile with nvoptix.

batero2000 commented 3 months ago

Finally, the issue was I wasn't building zluda with ninja. I got OptiX.

Nevertheless, V-Ray is still angry with me, same error is shown, but now it complains about Nvidia driver version:

1/4/2024 16:10:46 | Error | [V-Ray Asset Editor] No active scene Promise {  'No active scene' }
-- | -- | --
1/4/2024 16:11:05 | Error | [V-Ray] Failed to initialize OptiX (check your driver version. OptiX requires NVidia driver 466.11 or later)! Error Code : 7804
1/4/2024 16:11:05 | Error | [V-Ray] [VUtils::VOptix::ContextImpl::init] 7804: OptiX failed to initialize. Error code : 7804

Hope there is a fix anytime soon

DanoCH-boop commented 2 months ago

Hello, did you resolve this issue?