Andrzej Janik

Closing because no longer relevant. Feel free to open a new issue if it applies to the new version

Here's a breakdown of all known (by ZLUDA) functions from the cuGetExportTable: https://github.com/vosen/ZLUDA/blob/1b9ba2b2333746c5e2b05a2bf24fa6ec3828dcdf/zluda_dark_api/src/lib.rs#L197 The grammer is: ``` [GUID] => INTERFACE_NAME[NUMBER_OF_FUNCTIONS_IN_THE_INTERFACE] { FUNCTION_INDEX =>FUNCTION_SIGNATURE } ``` Closing, but feel free to...

Closing because no longer relevant. Feel free to open a new issue if it applies to the new version

I am closing this as no longer relevant. Feel free to reopen if it still appplies to the new version

@dumblob I've closed this issue (and all the old issues) because it applies to the old, Intel-based version. The discussion here is 3 years and ~300k lines of code out...

Check here: https://github.com/vosen/ZLUDA/blob/master/TROUBLESHOOTING.md

What happens if you render from the command line? I used this command (adjust for you blender and zluda paths) ``` c:\dev\zluda\target\debug\zluda_with.exe -- "C:\Program Files\Blender Foundation\Blender 3.4\blender.exe" -d --debug-cycles -noaudio...

It's very possible it does not work with the recent llama.cpp. I've tried llama.cpp a year ago: specifically commit 2322ec223a21625dfe9bd73ee677444a98a24ac9. I'm not staying on top of every application. Even for...

I took a look at llama.cpp and it requires minor additions to the compiler to compile first GPU module. I'm out most of this week, but I'll continue next week

Or maybe not. Please try this pull request: #102. I'm getting a different text output than on an NVIDIA card. Is it ok? I ran it like this ``` LD_LIBRARY_PATH=/home/vosen/dev/zluda_private/target/release...