Github messages for voidlinux
 help / color / mirror / Atom feed
From: vanessa-vd98 <vanessa-vd98@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Support for Nvidia OptiX in Blender 3.0
Date: Mon, 07 Feb 2022 08:44:35 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35456@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

New issue by vanessa-vd98 on void-packages repository

https://github.com/void-linux/void-packages/issues/35456

Description:

### System

* xuname:  
Void 5.15.19_1 x86_64 AuthenticAMD uptodate rrDFFF

* package:  
  *affected package(s) including the version*: blender-3.0.0_4

### Bug
There is no option for choosing the Nvidia Optix ray tracing engine in the build in Void's repo. Only CUDA is available. But in the same system, if I download the official build from blender.org, both CUDA and OptiX is available.

Before I updated, Blender 2.9 also had the option but it is not available in in the latest 3.0 version. A similar issue was reported to Blender's official bug tracker here: https://developer.blender.org/T93901

![no-optix](https://user-images.githubusercontent.com/99168064/152745330-609ae109-dde4-476f-b273-77f8fdf38612.png)





             reply	other threads:[~2022-02-07  7:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  7:44 vanessa-vd98 [this message]
2022-02-07 14:26 ` notthewave
2022-02-07 14:30 ` notthewave
2022-02-07 14:32 ` notthewave
2022-02-07 14:34 ` notthewave
2022-06-23  2:15 ` github-actions
2022-07-08  2:14 ` [ISSUE] [CLOSED] " github-actions
2024-02-07 16:48 ` too-vague

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35456@inbox.vuxu.org \
    --to=vanessa-vd98@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).