Indigo Renderer 3.4.4

[CTZn]

Hi Tom,

If I remember correctly the default Indigo void space has a precedence of 1 itself, this value should not be used. Agreed, it should not be available at all if the above is correct. Conflicts are to be expected then.

I have also noticed very slow startups while using shader scattering, it would be nice to know why exactly. I am assuming that a simple noise, constantly varying, requires a lot more of computations before the light can reach the scene ?

- Disable Shader or set back to None (for Scattering)
- Rendering still won't start, Indigo sometimes locks up

Yup there might be a fish under the rock, question mark.

[StompinTom]

Hi Tom,

If I remember correctly the default Indigo void space has a precedence of 1 itself, this value should not be used. Agreed, it should not be available at all if the above is correct. Conflicts are to be expected then.

I have also noticed very slow startups while using shader scattering, it would be nice to know why exactly. I am assuming that a simple noise, constantly varying, requires a lot more of computations before the light can reach the scene ?

- Disable Shader or set back to None (for Scattering)
- Rendering still won't start, Indigo sometimes locks up

Yup there might be a fish under the rock, question mark.

Ah, didn't know the 'void' had a precedence value. Makes sense then! But yes, should be not allowed in the material settings then.

I remember Nick had done some tests with shader scattering which looked as if they rendered fine (i.e. not extremely slowly). Any hints about shader scattering?

[Zom-B]

I remember Nick had done some tests with shader scattering which looked as if they rendered fine (i.e. not extremely slowly). Any hints about shader scattering?

For the Medium of a material there exists a variable named "Step Size" in the Indigo GUI.
Raising that should speed up rendering but be less "realistic"...

[Oscar J]

Good Stuff! Orthographic camera is very exciting!

Couple peeves as a Mac user:
Command-Q still reloads the scene, instead of quitting the application.
And we are still missing the "File > Save Material" menu for saving materials from an open scene (apparently this shows up in the property editor pane for Windows users - but we don't get it in OSX).

thanks!

Did the developers forget about these?

[fused]

Good Stuff! Orthographic camera is very exciting!

Couple peeves as a Mac user:
Command-Q still reloads the scene, instead of quitting the application.
And we are still missing the "File > Save Material" menu for saving materials from an open scene (apparently this shows up in the property editor pane for Windows users - but we don't get it in OSX).

thanks!

Did the developers forget about these?

No

Command-Q is fixed for the next release and File->Save on property editor will be looked into.

[zeitmeister]

Yeah!

[Bosseye]

Guys, can someone summarize how to work with EXR environment maps in this version please in Sketchup? I've just updated from v3.0.10 and the process is entirely different....

Thanks,

Edit: Its ok, figured it out now. Didn't notice the '...' button to quick link the EXR to the material. Might be worth someone updating the manual documentation to reflect this altered process though.

[Zom-B]

Might be worth someone updating the manual documentation to reflect this altered process though.

Here are some quite new video tutorials for some stuff:
http://www.youtube.com/playlist?list=PLD14E96A2CD263FE1

[Bosseye]

Oh, awesome. Thanks :)

[Bosseye]

Just a possible bug here, I'm getting a 'CUDA out of memory error' every so often, even on really simple scenes. Seems to do it when using Bi directional PT with GPU acceleration (as you might expect from the CUDA bit I suppose), and often does it when running a full model export. If I then run a quick export after the error occurs, then it generally renders ok

[Zom-B]

... Seems to do it when using Bi directional PT with GPU acceleration...

GPU rendering works only in pure PT!
By forcing BiDir using your exporter (shouldn't be possible at all dear Exporter dev ^^ ) that error could maybe happen...

[CTZn]

... Seems to do it when using Bi directional PT with GPU acceleration...

GPU rendering works only in pure PT!
By forcing BiDir using your exporter (shouldn't be possible at all dear Exporter dev ^^ ) that error could maybe happen...

As far as I know Indigo should adapt itself when the GPU tag is on, there is no way to force bidir on with gpu currently. Unless perhaps using the Indigo SDK but I'm not even sure.

Perhaps the geometry export is using the video memory somehow and fails in freeing it in time for Indigo ? Try to update the board drivers perhaps...

[Bosseye]

Thanks guys - I'll update my card drivers and see if that fixes things.

[CTZn]

*crosses fingers*