Greater functionality

[pvbeeber]

While I appreciate all the effort that's put into keeping Blendigo current, there are still some basic functionality/control issues that tend to hamper full utilization of Indigo's features. For example:

- can't set Halt SPP above 10,000
- can't set max. number of bounces
- can only adjust EV in 1-stop increments
- motion blur does not appear to be affected by length of exposure
- Autostart does not seem to work when exporting an animation

I realize that all of these things can be set manually in the .igs file, but incorporating them into Blendigo seems to be in line with the Indigo 2.4 "Don't make me think" approach. Perhaps assembling a "laundry list" of these issues would help get them addressed. Anybody have any others?

[StompinTom]

Good ideas, but be sure to mention them in the 2.3.x Blendigo thread: http://www.indigorenderer.com/forum/vie ... f=8&t=8106

[dougal2]

Good ideas, but be sure to mention them in the 2.3.x Blendigo thread: http://www.indigorenderer.com/forum/vie ... f=8&t=8106

... that is, if they are relevant to 2.3.x then please do.

Things like arbitrary input limits can easily be changed.

I'm intrigued by what you mean by "motion blur does not appear to be affected by length of exposure" - I've recently done a fair amount of work on the MB code, and was reasonably satisfied that it was working. Can you produce some examples demonstrating the problem please ?

[pvbeeber]

In revisiting this, I realized that MB is affected by exposure length, but there still seem to be irregularities. See the sequence below. The first image has a nice MB streak, which is as expected. In the second image, the streak is about half as long, which makes sense since the exposure length is roughly half that of the first image. But when the exposure is halved again, the results are indistinguishable from the same setup with no motion blur.

Also, I see that the amount of motion blur is also keyed to the frame rate, but the amount of motion blur still doesn't seem to make sense. For example, if my frame rate is 30 fps, and my exposure is 1/30 sec, shouldn't the resulting MB streak be exactly the same length that the object moves between one frame and the next?

I don't mean to make a big deal of this, but for those of us who render animations with Indigo this can cause problems that aren't apparent until after days of rendering! Thanks.

[dougal2]

Thanks for the detailed reply. Everything you said seems to make sense, and I'll cross-check your logic with what Blendigo is doing.

I have a feeling that if Blendigo detects that the MB time is less than 1 frame, then no MB is exported (or identical MB keys) instead of exporting a fractional-frame keyframe.

[Godzilla]

- can only adjust EV in 1-stop increments

In my opinion, these are what the increments should be when you click an arrow-

*Render Dimensions*

Width: 10Px increments
Height: 10Px increments

*Lens Shift*

0.0001 mm increments

*Camera Settings*

Focus distance: 0.1 m increments

*Environment tab*

All gain levels should be adjusted in increments of 1000 (And why is it that env maps can only have a gain of 10000?)

*Materials*

Exponent: 100 increments

Index of refraction: 0.1 increments

*Power (In light emission*

increments of 500

*All bump/displacement settings*

0.10 mm increments

[dougal2]

@GodZilla
If only Blender's UI controls allows such settings as that
Input precision and increments are severely crippled in Blender 2.4x - however there are some improvements in 2.5+ and I hope that the new exporter will make full use of that.