Indigo 1.0.1

[Kram1032]

No sense, Stur, I already said that hundreds of times, before - he won't stop
Btw, very nice pic, filippo

[manitwo]

just have to say i LOVE the new camera-tonemapping.
camera-tonemapped images look much better in my eyes. thanks a bunch for that ono.

[CoolColJ]

ONO

I don't think the exposure duration works with the Sun-Sky

[OnoSendai]

Exposure duration works just fine with sun + sky, not sure what you're doing CCJ.

[CoolColJ]

well it doesn't do anything for any of my own scenes. Everything looks as normal in the IGS file

[OnoSendai]

It will only have an effect if you use camera or linear tonemapping, perhaps that's the problem?

[CoolColJ]

I am using camera - but it's sorted now I think

does shutter_duration in the renderer settings do anything now, if so what does it do visually in Indigo?

[OnoSendai]

shutter_duration in the renderer_settings does absolutely nothing, it's not even processed.
I've added errors on spurious elements to renderere_settings now.

[CoolColJ]

ok
didn't you add that setting a while back?

no wonder I have been scratching my head about it

[OnoSendai]

Yeah possibly...
Anyway, in general, renderer_settings overrides stuff in the inifile.
So if it's not in the inifile it won't be in renderer_settings.

[blendergat]

great work Ono!
question:
Shouldn't it be 1.0 test 1?

[Big Fan]

bringing this back from the dead
I was looking at tabulated values and thinking of incorporating it into blendigo - seeing as how it is missing yet

here I have a question..
it would be fairly straight forward to incorporate a setting for this with the xml but how would it be if the actual values instead of being listed were put in a text file that was refered to??

it would look like this perhaps -

Code: Select all

  <material> 
      <name>mat1</name> 
      <diffuse> 
         <albedo_spectrum> 
            <regular_tabulated> 
               <start_wavelength>0.4E-06</start_wavelength> 
               <end_wavelength>0.7E-06</end_wavelength> 
               <num_values>10</num_values> 
               <values> 
                  <path>C:\my_most_ excellent_material_values.txt</path> 
               </values> 
            </regular_tabulated> 
         </albedo_spectrum> 
      </diffuse> 
   </material> 

is that good idea people? can it be done ono??

maybe wavelength numbers and no. of values should be in there too...?
- so you just call for example..
tropical sea water.txt

Code: Select all

  <material> 
      <name>mat1</name> 
      <diffuse> 
         <albedo_spectrum> 
            <regular_tabulated> 
                <values> 
                  <path>C:\tropical_sea_water.txt</path> 
               </values> 
            </regular_tabulated> 
         </albedo_spectrum> 
      </diffuse> 
   </material> 

[Big Fan]

hmmm well surprisingly no replies to this from the chattering classes

so - ono request please - if it was all in a text file it would be much easier to use/ impliment and consistant with other stuff.
we could have a folder of tabulated material.txt to choose from then rather than cut and paste into the .igs or try to make some weird arrangement to load this in the exporter Ui

[Kram1032]

Would it be possible to let the python script read the text and insert it? (as a provisoric in-between solution, obviously)
AFAIK, it works with every rgb-valued thing and IoR.... No idea if it works for diffuse or lights though.


Btw: I'm not sure about how to translate the stuff, but renderlight has an own nk format (with the ending .dat, though) with transparency and stuff. There are some other glass catalogues, besides the full Schott one and additionally, some gem-data
If anyone knows, how to translate the values, that would be great a full featured gem- and an even more expanded glass catalogue (As renderlight can't render SSS, yet, those values aren't included, though)

Is that, what you wanted to see, BF?

[dougal2]

i was under the impression that you can use an <include> tag anywhere... have you tried that ?