Blender: Difference between revisions

(3 intermediate revisions by the same user not shown)

Line 143:

environment.systemPackages = with pkgs; [

(blender.override {config.cudaSupport=true;})

# (~~pkgsRocm.~~blender.override {config.cudaSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support

/* (blender.override {

config.cudaSupport=true;

config.rocmSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support */

];

</syntaxhighlight>

~~NixOS Foundation does not cache CUDA versions of packages because of the unfree license. This means if~~ you ~~do not have~~ the [[CUDA#Setting up CUDA Binary Cache|CUDA Binary Cache]] set up, your machine will be compiling Blender from source. Compiling Blender is very resource-intensive, so if you are unable to use the CUDA Cache, ~~it is recommended to limit~~ the ~~number of cores or jobs that the process will take with the <code>--max-jobs</code> / <code>-j</code>~~ and ~~<code>--cores</code> flags whenever calling a command that will be building Blender, see:~~ [~~https://github.com/NixOS/nix/blob/master/doc/manual/source/advanced-topics/cores-vs-jobs.md Tuning Cores & Jobs~~] ~~for more information~~.

If installing Blender with <code>cudaSupport</code>, it is highly recommended you set up the [[CUDA#Setting up CUDA Binary Cache|CUDA Binary Cache]]. If you do not have it set up, and install Blender with <code>cudaSupport</code>, your machine will be compiling Blender from source.

Compiling Blender is very resource-intensive, so if you are unable to use the CUDA Cache, please see the associated warning and information in [[CUDA#Enabling CUDA In Packages]].

==== Community Flakes ====

Line 159:

Line 164:

environment.systemPackages = with pkgs; [

pkgsRocm.blender

# (blender.override {config.rocmSupport=true;}) # (equivalent to `pkgsRocm.blender`)

# (~~pkgsRocm.~~blender.override {config.cudaSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support

/* (blender.override {

config.rocmSupport=true;

config.cudaSupport=false;}) # (equivalent to `pkgsRocm.blender`) */

/* (blender.override {

config.cudaSupport=true;

config.rocmSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support */

];

</syntaxhighlight>

Line 175:

Line 187:

=== UI is dim on Vulkan backend and KDE Plasma ===

This is a cross-distro issue on current KDE Plasma (~~Wayland Session,~~ KDE Version 6.6.~~3) and~~ NVIDIA drivers (Versions 595.XX). A workaround option that doesn't require downgrading is to force XWayland by running Blender with the following command. See more information at the related {{issue|link=https://projects.blender.org/blender/blender/issues/155467||issue}} on Blender's repo.

This is a cross-distro issue on current KDE Plasma with NVIDIA, (confirmed issue on KDE Version 6.6.2-6.6.4 Wayland Session with NVIDIA drivers Versions 595.XX, though may affect others too). A workaround option that doesn't require downgrading is to force XWayland by running Blender with the following command. See more information at the related {{issue|link=https://projects.blender.org/blender/blender/issues/155467||issue}} on Blender's repo.

WAYLAND_DISPLAY=0 blender

</syntaxhighlight>

== References ==

@@ Line 143: / Line 143: @@
 environment.systemPackages = with pkgs; [
    (blender.override {config.cudaSupport=true;})
-# (pkgsRocm.blender.override {config.cudaSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support
+/* (blender.override {
+    config.cudaSupport=true;
+    config.rocmSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support */
 ];
 </syntaxhighlight>
-NixOS Foundation does not cache CUDA versions of packages because of the unfree license. This means if you do not have the [[CUDA#Setting up CUDA Binary Cache|CUDA Binary Cache]] set up, your machine will be compiling Blender from source. Compiling Blender is very resource-intensive, so if you are unable to use the CUDA Cache, it is recommended to limit the number of cores or jobs that the process will take with the <code>--max-jobs</code> / <code>-j</code> and <code>--cores</code> flags whenever calling a command that will be building Blender, see: [https://github.com/NixOS/nix/blob/master/doc/manual/source/advanced-topics/cores-vs-jobs.md Tuning Cores & Jobs] for more information.
+If installing Blender with <code>cudaSupport</code>, it is highly recommended you set up the [[CUDA#Setting up CUDA Binary Cache|CUDA Binary Cache]]. If you do not have it set up, and install Blender with <code>cudaSupport</code>, your machine will be compiling Blender from source.
+Compiling Blender is very resource-intensive, so if you are unable to use the CUDA Cache, please see the associated warning and information in [[CUDA#Enabling CUDA In Packages]].
 ==== Community Flakes ====
@@ Line 159: / Line 164: @@
 <syntaxhighlight lang="nix">
 environment.systemPackages = with pkgs; [
    pkgsRocm.blender
-# (blender.override {config.rocmSupport=true;}) # (equivalent to `pkgsRocm.blender`)
-# (pkgsRocm.blender.override {config.cudaSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support
+/* (blender.override {
+    config.rocmSupport=true;
+    config.cudaSupport=false;}) # (equivalent to `pkgsRocm.blender`) */
+/* (blender.override {
+    config.cudaSupport=true;
+    config.rocmSupport=true;}) # to compile blender with both HIP and CUDA/OptiX support */
 ];
 </syntaxhighlight>
@@ Line 175: / Line 187: @@
 === UI is dim on Vulkan backend and KDE Plasma ===
-This is a cross-distro issue on current KDE Plasma (Wayland Session, KDE Version 6.6.3) and NVIDIA drivers (Versions 595.XX). A workaround option that doesn't require downgrading is to force XWayland by running Blender with the following command. See more information at the related {{issue|link=https://projects.blender.org/blender/blender/issues/155467||issue}} on Blender's repo.
+This is a cross-distro issue on current KDE Plasma with NVIDIA, (confirmed issue on KDE Version 6.6.2-6.6.4 Wayland Session with NVIDIA drivers Versions 595.XX, though may affect others too). A workaround option that doesn't require downgrading is to force XWayland by running Blender with the following command. See more information at the related {{issue|link=https://projects.blender.org/blender/blender/issues/155467||issue}} on Blender's repo.
 <syntaxhighlight lang="sh">
 WAYLAND_DISPLAY=0 blender
 </syntaxhighlight>
 == References ==
 <references />