Indigo 1.0.4

[Kram1032]

how does your exact code look like? c+p

[Big Fan]

I'm not saying maybe tomorrow... after sleep..

just to show I'm getting better at this despite things going bump here is a doodle
I did code a couple of special settings for fstop and shutter..
it doesn't seem to affect the colours with a camera response - not sure really
havent quite got my 'light meter' sorted though
not too sure about the general usefulness of these items - another doubtful Big Fan experiment in progress

[CTZn]

Big Fan, isn't the crash caused by this bug ?

[Big Fan]

ok details at last - sorry for the spam about to follow

so a script screeny, the error, and part of the code ( lost the formatting but you see)...really hope this isnt me
its only the combination of images that causes the crash
the images in this case are 1024px

<scene>
<renderer_settings>
<width>480</width>
<height>270</height>
<large_mutation_prob>0.4</large_mutation_prob>
<max_change>0.03</max_change>
<max_num_consec_rejections>1000</max_num_consec_rejections>
<max_depth>1000</max_depth>
<aperture_diffraction>true</aperture_diffraction>
<super_sample_factor>3</super_sample_factor>
<ray_origin_nudge_distance>0.0001</ray_origin_nudge_distance>
<metropolis>true</metropolis>
<bidirectional>true</bidirectional>
<hybrid>false</hybrid>
<bih_tri_threshold>500000</bih_tri_threshold>
<num_threads>1</num_threads>
<auto_choose_num_threads>false</auto_choose_num_threads>
<frame_upload_period>60</frame_upload_period>
<halt_time>-1</halt_time>
<halt_samples_per_pixel>-1</halt_samples_per_pixel>
<display_period>60.0</display_period>
<image_save_period>300</image_save_period>
<cache_trees>false</cache_trees>
<logging>false</logging>
<watermark>false</watermark>
<save_untonemapped_exr>false</save_untonemapped_exr>
<save_tonemapped_exr>false</save_tonemapped_exr>
<save_igi>false</save_igi>
</renderer_settings>

<tonemapping>
<camera>
<ev_adjust>-3</ev_adjust>
<film_iso>125.000000</film_iso>
<response_function_path>data\camera_response_functions\F125CD.txt</response_function_path>
</camera>
</tonemapping>

<camera>
<pos>7.406914 -6.805959 5.043668</pos>
<up>-0.317370 0.312469 0.895343</up>
<forwards>-0.654862 0.610666 -0.445245</forwards>
<exposure_duration>525.000000</exposure_duration>
<aperture_radius>0.000798</aperture_radius>
<focus_distance>10.932673</focus_distance>
<aspect_ratio>1.77778</aspect_ratio>
<sensor_width>0.036000</sensor_width>
<lens_sensor_dist>0.039375</lens_sensor_dist>
<white_balance>E</white_balance>
<aperture_shape>
<image>
<path>..\indigo\aperture maps\7 rad sides small.png</path>
</image>
</aperture_shape>
<obstacle_map>
<path>..\indigo\obstacle maps\90deg grid small.png</path>
</obstacle_map>
</camera>

[psor]

@Big Fan

Erm, ... did you try a path without any spaces ... e.g.:

Code: Select all

  <path>..\indigo\aperture_maps\7_rad_sides_small.png</path>

You should get rid of the habit to use spaces in names, because a lot of
programs are getting hick ups with them ... dunno if it's the case with your
path, but I'm sure it was an issue with textures earlier. ;o))

btw. to keep the formatting, use the "code" element on the forum!



take care
psor

[Kram1032]

nice UI what's f-glint supposed to be?

[Big Fan]

@psor
code!... ak ok
um no I don't think its spaces I thought of that and tried it

@kram
I coded 5 special settings as an experiment with very small aperture and large exposure
F(fine) glint is one. I called them glint to distinguish from a general glare.
they just make twinkly highlights easily accessible - or thats the idea
at the moment there is something unusual about the exposure changing despite the light meter balance so there is moving match (blue dot) on the far right
This is partly what I was referring to about the reciprosity failure

btw ono there are small things still happening with dof control here so dont look too hard at the exposure numbers in the code
warm fuzzies

[psor]

@Big Fan

Just to be sure, ... did you check if the AR = 1:1 (eg. 512x512) of the images you used? ;o))



take care
psor

[Kram1032]

I see
Nice ideas.

[Roger]

Perhaps I shouldn't bother for this isn't the newest version anymore, but I had an odd result with Indigo 1.0.4.

The diffusemap in this image works fine, no problem at all. But the bumpmap seems shifted somehow. I turned off the bumpmapping and the result was fine. See:

I don't wanna complain, I don't wanna wine, I don't need a cookie, but I thought I'd let you know for it seems somewhat odd to me.

And yes, Nick, Ono, Sir, I am very grateful indeed for the time and effort you've put in Indigo . Thanks pal!

Now that I am posting replies and all, I might wanna post this question, I can't find the answer anywhere near. I would very much want dof and I can't seem to figure it out with my very limited brain. I am using the 104 version of Blendigo, any ideas what buttons to switch?

[psor]

@Roger

Sorry, I can't help you with the shifting ...

For the DOF, model your scene to world scale and take a look at this
thread in the blender subforum. ;o))




take care
psor

[Roger]

psor, I'm glad ye were able to help gmaisg in that threat, but when I change the camera settings to the ones the Maxwell renderer program suggested, see settings below, everythings stays perfectly in focus.

If ye know how to achieve dof, please help me out here .
Btw, I've made two renders with a Cornell-ish scene I made, one with a cube with SSS, the other render just a reflective cube. The render with a tiny bit of SSS in the scene rendered like 2,5 times slower, is this possible?

Still on 1.0.4

Cheers.

[Kram1032]

If your scene is perfectly in focus, although F-Stop is that low, your scene must be huge
You need to check your scene scale... Under circumstances, Maxwell assumes Centimetres or something as it's default Unit-scale. If that's the case, you need to set your World Scale Factor to 0.01
You'll find that factor in "Environment"

Yes, 2.5 times is entirely possible. SSS is the slowest unblended mat, besides mats with chromatic dispersion or some other special features enabled.
(Blends are as slow as the mats which are blended...)

[psor]

@Roger

Ok then the first quick question for ya. Is your scene modeled to
"World Scale"? What I mean is, is 1 unit = 1 Meter? Just to give
you an example. If you scene is much bigger, you'll not get any
DOF. If your scene is much smaller you will have to much DOF.

And from my POV, your settings should be right. Because with
f-stop 2 you should have a pretty small DOF. Which means that
just a small part of your scene will be in focus.

Probably I'm missing something here ...

edit: Kram, you beat me to it! ;o))




take care
psor

[Kram1032]

always