Indigo Renderer Forum

fused wrote:The benchmark needs to compile some kernels on the first run, which can take up to a few minutes. It should say so in the log line in the bottom right corner (or maybe the current benchmark doesn't say it, not entirely sure what version is out).

Is that before the bedroom scene is rendered? If so, then kernel compiling was done as first scene renders, but either doesn't finish or doesn't progress past that point.

Kernel parsing should require a good amount of CPU time, no? Why would the CPU be at 1% utilization after first scene?

It's possible it is a bug, but kernel compilations happens on on core only (at least in the current Indigo Benchmark, I think). It happens right before rendering a scene with GPU but should only happen the first time rendering that scene.

I'm using 388.43 drivers. Ran the bench again with the CPU module deselected. It came up with the following message:

Error: clCreateContextFromType failed: CL_DEVICE_NOT_AVAILABLE

From this it seems as though the GPU isn't responding?

I've also tried WHQL 388.59, still nada.

had same issue almost a month ago with 388.13 drivers - one of devices gone, 'lost OCL capabilities' ?
installed 378.66 & haven't checked since

thanks for notice

burnin wrote:had same issue almost a month ago with 388.13 drivers - one of devices gone, 'lost OCL capabilities' ?
installed 378.66 & haven't checked since

thanks for notice

Are you on Win 10? If so, any trouble using it as it doesn't say that 378.66 is Win 10 certified.

Juju wrote: Are you on Win 10? If so, any trouble using it as it doesn't say that 378.66 is Win 10 certified.

No, am w7 user.
Tho, even if not officially certified they should work.
Win10 is from my tests & experience counter-productive (constant updates, notifications... disrupting my workflow, inner peace... ;).

Have looked around & found some more info on driver regression (if interested):
- Best NVIDIA GeForce Driver Win/Linux (@ RedShift forums)
- NVIDIA's Current Linux Driver Is Hungry For vRAM This Holiday

Will most probably run some tests during the weekend to see how it performs on windows (since above shared experience is based on Linux platform).

burnin wrote: Win10 is from my tests & experience counter-productive (constant updates, notifications... disrupting my workflow, inner peace... ;).

This is a new machine, so not much choice in the matter.

burnin wrote: Have looked around & found some more info on driver regression (if interested):
- Best NVIDIA GeForce Driver Win/Linux (@ RedShift forums)

Link only seems to work if you have a RedShift account, which I don't.

About post on RS forums
It's basically still just an intro, started last week, so nothing definitive yet. Goes about questioning the stability of drivers & consuming much more vRAM, leading to the next article (linked above.)

As written, OCL capabilities are gone with drivers 388.xx on my side. Am also testing RadeonPro Render (which recently got much faster & denoiser (3 variations) included for Blender integration). So i must further test & experience myself to make any fair statement... but it takes time (free time) - so, you too are welcome to do it on your side (Indigo on w10) and share experience ;)

got maybe some stupid question here, but does Indigo 4.0.61 does work on your system with GPU?

The benchmark is based on Indigo 4.0.46, so maybe that issue got fixed already and your system will work with a updated benchmark that will be released for sure once Indigo 4 left beta stage...

If Indigo 4.0.61 doesn't work with your GPU, then we have a up to date version to do some bugtracking on!

Since you are on a laptop, how much RAM is allocated to the GPU? Or is it nowadays a own dedicated RAM pool for the GPU...?

Zom-B wrote:got maybe some stupid question here, but does Indigo 4.0.61 does work on your system with GPU?

It works.

Zom-B wrote: Since you are on a laptop, how much RAM is allocated to the GPU? Or is it nowadays a own dedicated RAM pool for the GPU...?

It's an OriginPC EON17-X laptop with a desktop grade CPU & GPU.

CPU: Intel i7 7700K
GPU: nVidia GTX 1080 (8GB)
System RAM: 64GB
OS: Win 10 Pro

Juju wrote: It works.

Something to do with this specific Indigo render core version (.46) then? I guess next IndigoBench version might solve it. :)

I'll put up a new benchmark soon.

New Benchmark released: https://www.indigorenderer.com/forum/vi ... =1&t=14563

The Indigo CPU is the best unit for the users. I am getting the error code 0x3e9(1001) in my system. I also try on fix error code 0x3e9(1001) for the help purpose but did not get any response.