Indigo Renderer 4 public beta

[Esenistras]

Yes, it crashed ^^

Edit:
it seems to work normally on Luxmark 3.
Hotel scene: 1904
is it a normal score ?

[Originalplan®]

Can we look forward to have some support for Open VDB in V4?
( i seen some test from ONO somewhere in the forum)
Or native stl support?

Or is that unlikely?

[Oscar J]

Nick said he had done native STL support for V4, though I haven't actually tested it: http://www.indigorenderer.com/node/2014

[davide445]

Testing a scene created from iClone 6, strange is working with CPU rendering, on GPU all is remaining black.
A simpler version with the two characters, a terrain and a tree was working without problems (just some materials to fix).
Same settings PT etc, here you can find the pigs file and the igs scene

https://drive.google.com/file/d/0BxbefK ... sp=sharing

https://drive.google.com/file/d/0BxbefK ... sp=sharing

[Oscar J]

That scene works fine for me with GPU, it just takes like a minute to build the OpenCL kernels due to the many textures.

[contegufo]

Hi

Three material FastSSS.

[davide445]

That scene works fine for me with GPU, it just takes like a minute to build the OpenCL kernels due to the many textures.

I can't understood why, your 7970 GPU it's the same architecture as mine.
Tried now to change Environment, ISO, Response function, nothing changes.
Attached the screen of CPU and GPU render, can't find the Render advanced options logging to post this also.

--------
Edit: testing the same scene with edited terrain (added some grass) the render is apparently working but noting happen and looking at the log did find this message:
GPU path tracing initialisation failed: clCreateBuffer failed: CL_INVALID_BUFFER_SIZE

[Zom-B]

Hey davide445,

please close the OpenGL preview and the material preview, since they both eat up your GPU RAM without any need!

**edit**
sorry: only the OpenGL preview eats up GPU RAM, not the material preview!

[davide445]

Thanks Zom-B

Same result: all black with the pigs I did posted and same error with the modified one, with both preview closed.

Noticed in the Render settings>Device information it's stated: Max allocation 2.062 GB, mean nothing the fact the Dedicated memory it's 2.2GB at runtime?

Attached the screenshot with the GPU usage parameters, next the render log

Rendering with GPU acceleration
Forcing bidirectional=false, hybrid=false, batched=true
Object tree build done. (Time Taken: 0.002 s)
Num buffer layers: 1
Master buffer size: 32.643 MB
Settings:
Image width: 1115 px
Image height: 627 px
Internal image width: 2246 px
Internal image height: 1270 px
Verbose: false
Image save period: 60 s
Splat filter: FastBox
Downsize filter: mn_cubic, blur=1.000, ring=-0.000, support=3.200px
Render region: false
Supersample factor: 2
Metropolis: false
Bidirectional: false
Hybrid: false
Aperture diffraction: false
Post-process diffraction: true
Auto setting number of threads to 4.
Finished initialisation (Time Taken: 4.40 s)
AutoFocus: setting camera focus distance to 19.289 m.
Starting threads... (num threads: 4)
Starting render thread. (RNG seed=0)
OpenCL program built. (elapsed: 27.38 s)

[Oscar J]

As has been explained earlier, Max Allocation is the limit per allocation. Indigo does multiple allocations for textures, geometry, etc.

This could be a bug, have you checked the render log? Do simpler scenes render fine?

[davide445]

Simpler scene render fine, as stated I can't find the Advanced render settings so to enable logging, where does need to be?

[Oscar J]

The render log window inside Indigo? It's where you select Render Settings, Imaging, etc.

[davide445]

Did already paste what's inside this Render log in the above message.

Was searching for the Advanced settings read about in the manual
http://indigorenderer.com/documentation ... r-settings
if this logging is more detailed.

If it's the same i can see in the UI panel don't mind.

[Oscar J]

Sorry, major reading comprehension fail. :)

[davide445]

Thanks for your support on Saturday :)

About this kind of image I did want try recreate the same using C4D, so to better compare the result and the effort.