Long time ago since i wrote something in here. One reason is that i don't felt so well in the indigo-community as years ago - too much spamming and people who want to raise their post-counts no matter what crap they post - but it looks like that changed a bit now. The other reason was i was switching the operating system (i'm on ubuntu now and it really rocks!) and theres no native linux version of my beloved c4d (runs in wine but not as good as i hoped it would) so i had to get familiar with blender. The relationship between blender and me is best described as a love-hate-relationship. I already tried several times to switch to blender but always went back to c4d. On the one hand blender has a really outstanding featurelist but on the other hand blender has still enough areas which are feature-lacking + the much discussed contrary gui + too much fanboys with blinders on. But the person who dont see that blender is getting better and better with every release is also blind. So i decided to switch.
Blender is not as comfortable as i would like and in some areas much more complicated than any other 3d-package i had worked with but now i am (after a long time) able to work with.
puhh
enough from me!So started to use indigo again and therefore discovering blendigo.
I already sent smartden a pm with some suggestion but now i have a "few" more of those and wanted to to know what the community thinks about.
Let me summarize those things which i've noticed:
-- the default material blendigo creates has <rgb>1 1 1</rgb>, wouldnt it be better to clamp to values to <rgb>0.8 0.8 0.8</rgb>?
-- blendigo claims it can't find IndigoWrapper.conf cause the included file in the .zip is named Indigowrapper.conf (linux is case-sensitive)
-- can you make blendigo's rendersettings-export optional? maybe some people (include me
) want indigo to use the settings of the inifile ... (or give the user the choice to decide wich parameter gets exported and which not [if i want to export only the render resolution for example])-- The default gamma value for "Albedo" is 2.3 .... shouldn't it be 2.2?
-- For newbies it might be more understandable if "Albedo" is renamed to "ImageMap" (also "BumpMap" and "ExponentMap")
-- It would be more logical if the camera-tonemapping specific options (ISO, Exposure) could be found under "Tonemap - Camera" rather than under "Camera" cause these options won't do anything if linear or reinhard is enabled.
-- I would dump the "Extra Atmospheric" button - no one uses it. (this is a really experimental function and should be hidden from the average user)
-- "ray nudge" should also be hidden. nobody should be able to touch that value except those who know what it is - and those who know are able to change that value manually.
-- whats "hybrid_threshold"? bih_tri_threshold? if yes - dump that also (same reason as above) - or hide it - or give it another name cause the average user will think its connected with the hybrid-rendering-mode
-- for what is the "uvset" option under the texture-slots in blendigo? any reason a user should touch that? (as i said im not [yet] familiar enough with blendigo/blender)
-- it's not really obvious (for those who dont read it anywhere) that the "b" parameter of the bumpmap influences the bump-strength. dont know whats the best way to solve that problem myself tho.
-- most people nowadays have a muli-core-cpu but the default setting in blendigo is "t - 1". So if you dont alter that value indigo is running at half speed. Use indigos auto_num_thread instead and make the thread parameter optional.
Those are, of course, only suggestions to improve the already wonderfull blendigo. Many thanks to all which have contributed in this exporter!
Hope you guys dont mind the long post
