Blender - Revision history

Smudgebun: /* UI is dim on Vulkan backend and KDE Plasma */ Updated known affected versions

2026-04-11T07:46:39Z

UI is dim on Vulkan backend and KDE Plasma: Updated known affected versions

← Older revision		Revision as of 07:46, 11 April 2026
Line 187:		Line 187:
	=== UI is dim on Vulkan backend and KDE Plasma ===		=== 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">		<syntaxhighlight lang="sh">
	WAYLAND_DISPLAY=0 blender		WAYLAND_DISPLAY=0 blender
	</syntaxhighlight>		</syntaxhighlight>


	== References ==		== References ==
	<references />		<references />

Smudgebun: /* The cudaSupport Flag */ Fixed example

2026-04-11T07:40:34Z

The cudaSupport Flag: Fixed example

← Older revision		Revision as of 07:40, 11 April 2026
Line 143:		Line 143:
	environment.systemPackages = with pkgs; [		environment.systemPackages = with pkgs; [
	(blender.override {config.cudaSupport=true;})		(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>		</syntaxhighlight>

Smudgebun: /* HIP */ Fixed example

2026-04-11T07:39:58Z

HIP: Fixed example

← Older revision		Revision as of 07:39, 11 April 2026
Line 161:		Line 161:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	environment.systemPackages = with pkgs; [		environment.systemPackages = with pkgs; [

	pkgsRocm.blender		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>		</syntaxhighlight>

Smudgebun: /* The cudaSupport Flag */ Made section more concise, less repeated information between this and the CUDA page.

2026-04-11T06:45:16Z

The cudaSupport Flag: Made section more concise, less repeated information between this and the CUDA page.

← Older revision		Revision as of 06:45, 11 April 2026
Line 147:		Line 147:
	</syntaxhighlight>		</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 ====		==== Community Flakes ====

Smudgebun: /* oneAPI */ Tidied use of Issue Template

2026-04-11T05:48:07Z

oneAPI: Tidied use of Issue Template

← Older revision		Revision as of 05:48, 11 April 2026
Line 166:		Line 166:

	=== oneAPI ===		=== oneAPI ===
	Currently, Nixpkgs has extremely limited oneAPI support, (see: {{issue\|367722\|~~oneAPI~~ Tracking}}), which is explicitly blocking ~~oneAPI integration into the Blender package (see:~~ {{issue\|447245\|Blender oneAPI Support}}). As such, the current only way to have oneAPI support on NixOS is through one of the [[#Binary Packages\|#Binary Packages]]		Currently, Nixpkgs has extremely limited oneAPI support (see: {{issue\|367722\|<nowiki>[Tracking] OneAPI Packages</nowiki>}}), which is explicitly blocking {{issue\|447245\|Blender oneAPI Support}}. As such, the current only way to have oneAPI support on NixOS is through one of the [[#Binary Packages\|#Binary Packages]].

	=== Last Resorts ===		=== Last Resorts ===

Smudgebun: Added a section on installing with additional python modules

2026-04-11T05:32:42Z

Added a section on installing with additional python modules

← Older revision		Revision as of 05:32, 11 April 2026
Line 11:		Line 11:

	If you want to install Blender with support for compute APIs, see: [[#Advanced Installation]]		If you want to install Blender with support for compute APIs, see: [[#Advanced Installation]]

			== Configuration ==
			=== Installing With Additional Python Packages ===
			To install additional Python modules into Blender, use the <code>withPackages</code> attribute.

			Example using a normal Blender package:

			<syntaxhighlight lang="nix">
			environment.systemPackages = with pkgs; [
			(blender.withPackages(ps: [ ps.pyserial ps.fs ])
			];
			</syntaxhighlight>

			Examples using abnormal Blender Packages:
			<syntaxhighlight lang="nix">
			let
			blender-cuda = blender.override {config.cudaSupport=true;};
			in {

			environment.systemPackages = with pkgs; [
			(blender-cuda.withPackages(ps: [ ps.yq ])
			# (pkgsRocm.blender.withPackages(ps: [ ps.pyserial ps.fs ])
			];
			}
			</syntaxhighlight>

			In these functions, <code>ps</code> is an alias for <code>python313Packages</code>.

			Installing with additional packages will result in a binary named <code>blender-wrapped</code> as it adds the python modules by wrapping Blender in a custom Python environment. When using a binary or unofficial Blender nix package, support for this feature will vary depending on if and how the packager implemented it.

			A workaround if using a package that doesn't support <code>withPackages</code> is to install the python packages globally.

			<syntaxhighlight lang="nix">
			environment.systemPackages = with pkgs; [
			python313Packages.yq
			python313Packages.pyserial
			];
			</syntaxhighlight>

			Or if it fits your use case better, you can install them in a nix-shell and run Blender from within that shell.

			{{file\|shell.nix\|nix\|
			<nowiki>
			let
			nixpkgs = fetchTarball "https://github.com/NixOS/nixpkgs/tarball/nixos-25.11";
			pkgs = import nixpkgs { config = {}; overlays = []; };
			in

			pkgs.mkShellNoCC {
			packages = with pkgs; [
			python313Packages.yq
			python313Packages.fs
			# Optionally you can declare the Blender package you want to use in the shell, so you can run the shell in --pure.
			# Can be useful if you're trying to make a reproducible development shell or similar.
			pkgsRocm.blender
			];

			}
			</nowiki>
			}}

	== Tips & Tricks ==		== Tips & Tricks ==

Smudgebun: /* The cudaSupport Flag */ Moved some non-Blender-specific information to the CUDA page, and added a link to that section. Clarified build information.

2026-04-11T02:17:32Z

The cudaSupport Flag: Moved some non-Blender-specific information to the CUDA page, and added a link to that section. Clarified build information.

← Older revision		Revision as of 02:17, 11 April 2026
Line 76:		Line 76:

	==== The cudaSupport Flag ====		==== The cudaSupport Flag ====
	Whether a compatible package is built with CUDA support is managed by the <code>cudaSupport</code> flag enabled. ~~This can either be done with a global flag~~		Whether a compatible package is built with CUDA support is managed by the <code>cudaSupport</code> flag enabled.

	~~<syntaxhighlight lang="nix"> nixpkgs.config.cudaSupport = true; </syntaxhighlight>~~		The following example shows how to override specifically the Blender package for CUDA support, for general information on the topic see: [[CUDA#Enabling CUDA In Packages\|Enabling CUDA In Packages]].

	~~Or by overriding~~ specifically the Blender package.

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
Line 89:		Line 87:
	</syntaxhighlight>		</syntaxhighlight>

	~~It's important to note that any package installed with~~ the ~~<code>cudaSupport</code> flag enabled that is~~ CUDA~~-compatible~~ will be ~~compiled~~ from source~~, as Hydra does not build (and therefore cache~~.~~nixos.org does not cache) with CUDA support enabled. With larger programs like~~ Blender ~~this can be~~ very resource-intensive, so 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 ~~when~~ calling ~~for example <code>~~nix-~~shell<~~/~~code> or <code>nixos~~-~~rebuild</code>~~. ~~This is also why it is recommended to only enable <code>cudaSupport</code> for the programs you need it~~ for.		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.

	==== Community Flakes ====		==== Community Flakes ====

Smudgebun: /* HIP */ Moved some non-Blender-specific information to AMD GPU, linked to there for more

2026-04-11T00:56:42Z

HIP: Moved some non-Blender-specific information to AMD GPU, linked to there for more

← Older revision		Revision as of 00:56, 11 April 2026
Line 95:		Line 95:

	=== HIP ===		=== HIP ===
	With the deprecation of the <code>blender-hip</code> package,<ref name="deprecate-hip"> {{pull\|463064}}</ref> the easiest way to add Blender with HIP support is now with the <code>pkgsRocm.blender</code> package. Other methods are to use the <code>rocmSupport</code> ~~flag the same way as [[#The cudaSupport Flag\|#The cudaSupport Flag]]~~, or to use a [[#Binary Packages\|#Binary Package]].		With the deprecation of the <code>blender-hip</code> package,<ref name="deprecate-hip"> {{pull\|463064}}</ref> the easiest way to add Blender with HIP support is now with the <code>pkgsRocm.blender</code> package. Other methods are to use the <code>rocmSupport</code> config variable, or to use a [[#Binary Packages\|#Binary Package]].

	~~Unlike <code>cudaSupport</code>, most if not all packages with <code>rocmSuppport</code> are built by Hydra and cached into cache~~.~~nixos.org. That said, it is still recommended to enable <code>rocmSupport<~~/~~code> only as much as you will need it, to avoid the chance of pointless recompilation on~~ your ~~machine.~~		The below example is Blender-specific. For more general information on enabling ROCm/HIP in your configuration, see: [[AMD GPU#Enabling ROCm & HIP For Packages]].

	~~To activate the flag globally, run the following.~~

	~~<syntaxhighlight lang="nix"> nixpkgs.config.rocmSupport = true; </syntaxhighlight>~~

	Or, ~~override specifically Blender with~~ HIP ~~support~~.

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Smudgebun: /* Blendfarm */Converted link to option template

2026-04-10T23:19:25Z

Blendfarm: Converted link to option template

← Older revision		Revision as of 23:19, 10 April 2026
Line 15:		Line 15:

	=== Blendfarm ===		=== Blendfarm ===
	The Blendfarm ~~Network Renderer~~ for Blender is ~~provided~~ by ~~[https~~:~~//github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/blenderfarm.nix~~ services.blendfarm]. A very simple example configuration is shown below.		The Blendfarm network renderer for Blender is handled by {{nixos:option\|services.blendfarm}}. A very simple example configuration is shown below.

	{{file\|configuration.nix\|nix\|		{{file\|configuration.nix\|nix\|

Smudgebun: /* Community Flakes */ slightly changed wording

2026-04-10T22:53:40Z

Community Flakes: slightly changed wording

← Older revision		Revision as of 22:53, 10 April 2026
Line 92:		Line 92:

	==== Community Flakes ====		==== Community Flakes ====
	In addition to the [[#The blender-bin Flake\|#blender-bin flake]], there is also [https://github.com/adithyagenie/blender-cuda-nixos blender-cuda-nixos], which compiles Blender with <code>cudaSupport</code> enabled and caches it on cachix so you don't need to build it yourself. For instructions on adding it to your configuration, see its [https://github.com/adithyagenie/blender-cuda-nixos/blob/master/README.md README].		In addition to the [[#The blender-bin Flake\|#blender-bin flake]], there is also [https://github.com/adithyagenie/blender-cuda-nixos blender-cuda-nixos], which compiles Blender with <code>cudaSupport</code> enabled and caches it on cachix so you don't need to build it yourself. For the most up-to-date instructions on adding it to your configuration, see its [https://github.com/adithyagenie/blender-cuda-nixos/blob/master/README.md README].

	=== HIP ===		=== HIP ===