Package Details: raytracinginvulkan-git 7.r32.g92170b6-1

Git Clone URL: https://aur.archlinux.org/raytracinginvulkan-git.git (read-only, click to copy)
Package Base: raytracinginvulkan-git
Description: Implementation of Peter Shirley's Ray Tracing In One Weekend book
Upstream URL: https://github.com/GPSnoopy/RayTracingInVulkan
Licenses: BSD-3-Clause
Conflicts: raytracinginvulkan
Provides: raytracinginvulkan
Submitter: PedroHLC
Maintainer: PedroHLC (a821, chaotic-aur)
Last Packager: a821
Votes: 1
Popularity: 0.000007
First Submitted: 2021-04-21 02:27 (UTC)
Last Updated: 2025-04-03 19:54 (UTC)

Pinned Comments

<deleted-account> commented on 2023-04-22 09:37 (UTC)

Also I would like to note that upstream here is extremely careless about their code change consequences, and dont perform any kind of QA of their code at all. But, despite that, I would still like to keep this package as upstream as possible to welcome new features as they pop in.

So, If this package does not build anymore, please, let me know! Thank you!

PedroHLC commented on 2021-04-21 02:45 (UTC) (edited on 2021-05-09 15:16 (UTC) by PedroHLC)

How to run?:

cd /opt/raytracinginvulkan/bin
./RayTracer --benchmark --width 1920 --height 1080 --fullscreen --scene 1 --next-scenes --present-mode 0

Contribution and issues in: https://github.com/chaotic-aur/pkgbuild-raytracinginvulkan-git

Latest Comments

1 2 3 4 Next › Last »

a821 commented on 2025-04-03 19:53 (UTC)

@theriddick: :) also https://aur.archlinux.org/packages/raytracinginvulkan-git?O=20#comment-911371

I'll push a commit soon. It's basically the same test PKGBUILD plus an additional launcher script to avoid the cd command.

I have the same issue "cannot find a device" with an NVidia GeForce 730. Not sure what I'm doing wrong, and the wiki doesn't help... I don't have the power to investigate further, but at the very least the package builds.

Not sure what to do about the other issues you have, maybe they should be upstreamed.

And finally, if you have suggestions/patches let me know.

theriddick commented on 2025-04-03 13:19 (UTC) (edited on 2025-04-03 13:26 (UTC) by theriddick)

@a821 No I didn't go into the folder and run it like that. And I just did then and well, it works! LMAO oops.

So I guess you just gotta figure out why your iGPU isn't liking RT.

I should test this on my AMD 9950X3D iGPU which I have hooked up. Not sure if it handles RT really. (NOPE, spat out FATAL: failed to enumerate (ERROR_SURFACE_LOST_KHR))

I do notice the app doesn't adjust the resolution with scaling set. I have %150 scaling and its setting a resolution %50 higher then specified.

a821 commented on 2025-04-03 13:17 (UTC)

yes, probably some setting or env var is missing on my setup, but vulkaninfo output looks OK to me and I don't have time to debug ATM here.

Just a little thing before I deep dive into the issue: in your previous comment you ran /opt/raytracinginvulkan/bin/RayTracer, but did you try to run it like the pinned comment? (cd /opt/raytracinginvulkan/bin ; ./RayTracer ...)

theriddick commented on 2025-04-03 10:13 (UTC) (edited on 2025-04-03 10:20 (UTC) by theriddick)

a821 For that iGPU you may need specific environmental settings or some additional driver component. For Ray Tracing under Vulkan that is.

Btw that png file exists where it should be.

a821 commented on 2025-04-03 09:58 (UTC) 

openat(AT_FDCWD, "../assets/textures/Vulkan.png", O_RDONLY) = -1 ENOENT (No such file or directory)

Thanks, that looks like a clue.

FWIW, I compiled it on my work notebook using the vcpkg_linux.sh and build_linux.sh scripts, and then cd build/linux/bin && ./RayTracer ... and also fails with a different error :(

$ ./RayTracer --benchmark --width 1920 --height 1080 --fullscreen --scene 1 --next-scenes --present-mode 0  
Vulkan SDK Header Version: 296

Vulkan Devices: 
- [5686] AMD 'AMD Radeon Graphics (RADV RENOIR)' (Integrated GPU: vulkan 1.4.305, driver radv Mesa 25.0.2-arch1.2 - 25.0.2)

FATAL: cannot find a suitable device

 0# 0x0000615A8B4B4D13 in ./RayTracer
 1# 0x0000615A8B4B82A0 in ./RayTracer
 2# 0x00007BC219835488 in /usr/lib/libc.so.6
 3# __libc_start_main in /usr/lib/libc.so.6
 4# 0x0000615A8B4C6A65 in ./RayTracer

theriddick commented on 2025-04-03 09:15 (UTC)

@a821

Here is the strace output, pretty big.

https://ctxt.io/2/AAB4G0uvEQ

a821 commented on 2025-04-03 09:08 (UTC)

Thanks for testing.

I just checked that it build but didn't actually run it. There's probably an icon missing. but it's hard to say what's wrong without looking at the code, maybe you could strace it? I can have a look later today, or if you can figure a fix let me know.

theriddick commented on 2025-04-03 08:45 (UTC) (edited on 2025-04-03 08:49 (UTC) by theriddick)

It compiled and installed correctly but outputs this when ran with and without arguments. 

❯ /opt/raytracinginvulkan/bin/RayTracer --benchmark --width 1920 --height 1080 --scene 1 --next-scenes --present-mode 0
FATAL: failed to load icon

 0# 0x000064366FDBEF32 in /opt/raytracinginvulkan/bin/RayTracer
 1# 0x000064366FDC0681 in /opt/raytracinginvulkan/bin/RayTracer
 2# 0x000064366FDCD23D in /opt/raytracinginvulkan/bin/RayTracer
 3# 0x000071C83E16188E in /usr/lib/libc.so.6
 4# __libc_start_main in /usr/lib/libc.so.6
 5# 0x000064366FDCF9B5 in /opt/raytracinginvulkan/bin/RayTracer

Here is my full compile and install output btw. https://ctxt.io/2/AAB4pbgFEA

a821 commented on 2025-04-03 07:56 (UTC)

@theriddick

I get the same error with the latest imgui-1.19.9b ("OR" "OR" argument). I initially tried with 1.19.6, which seemed to work so I used that. I arranged the PKGBUILD so it builds imgui statically to be independent of the aur package. Also, the imgui-full package does not build with freetype support which is needed.

Here is the test PKGBUILD and the patch (the file should be called imgui-cmake.patch). I just checked that it builds in a clean chroot. It would be great if you can actually test the software.

theriddick commented on 2025-04-03 02:14 (UTC)

@a821

Yes feel free to post a test PKGBUILD. I tried to make it with latest imgui as well but it spat out a different error, be nice if it could be updated against that. Might just be a few things to change. I can post the output but I'm sure you could get it yourself.

1 2 3 4 Next › Last »