Blendigo for v0.9

Kram1032 · Post by **Kram1032** » Sun Oct 07, 2007 11:13 am

[REQ] for both versions of Blendigo:
non-uniformal henyey-greenstein g-values

[REQ] to Ono: explain, what that exactly does xD

Big Fan · Post by **Big Fan** » Sun Oct 07, 2007 11:55 am

well i already told you I wont be doing that and why elsewhere

EDIT ok kram wins after heavy weight discussion

henyey-greenstein is now rgb see previous script post for update

Kram1032 · Post by **Kram1032** » Sun Oct 07, 2007 8:49 pm

lol, actually, the discussion wasn't heavy at all

Anyway, thank you, very much

WytRaven · Post by **WytRaven** » Sun Oct 07, 2007 9:07 pm

Thx BigFan, saves me hand editing it in the igs all the time

Kram1032 · Post by **Kram1032** » Sun Oct 07, 2007 10:48 pm

ok.
Following problems:
My glossy transparent SSS and rgb-g-value thingy didn't get exported!

Far less important "problem": The ray nudge distance got exported slightly wrong... after about 5 unneeded "0", it added 149 at the end of the thing... some precession error?

The rest appears to be fine

The mat didn't only have no g-value, btw, but it simply got fully ignored

That causes the export progress, finishing without any bug, but then, Indigo writes "Material.003 isn't defined" and closes a nanosec later, so that it was really hard to read, what's wrong^^

Big Fan · Post by **Big Fan** » Sun Oct 07, 2007 11:21 pm

well I just tried glossy transparent here and it seemed to work ok kram so perhaps you missed setting it somehow?
if there is a problem it would help to know more - can you post your material or something

I am aware of the 149 not sure where that comes from presently but it is very small error so I leave it at the moment

Kram1032 · Post by **Kram1032** » Sun Oct 07, 2007 11:26 pm

I'm not sure, what's the problem, now....
I noticed, that I put the material on the object instead of the mesh, but even after changing, it still didn't work...
I also tried to use different material typed...
I guess, that such a "noone knows, how or why, but it never'll show up again"-bug... I'm pretty sure, when I rebuild it, it's gone...
If it still doesn't work after rebuilding, I'll post my mat

Kram1032 · Post by **Kram1032** » Sun Oct 07, 2007 11:47 pm

ok, bug tracked!
I think, the problem occurs, when you define a material ONLY on a sphere primitive.
If you use it twice, I bet, it works just fine.

sk2k · Post by **sk2k** » Mon Oct 08, 2007 3:03 am

Hi,

@bf

Do you changed the calculation for the aperture radius? I get much darker pictures with your t8 exporter so i looked into the exported .igs files to see what's the difference. With the previous t7 exporter i get <aperture_radius>0.005617</aperture_radius>. With your new exporter i get <aperture_radius>0.054894</aperture_radius>.

MfG
sk2k

Kram1032 · Post by **Kram1032** » Mon Oct 08, 2007 3:12 am

he changed the DoF export way and DoF is directly related to the aperture size^^
but ten times larger apertude? xD

Big Fan · Post by **Big Fan** » Mon Oct 08, 2007 6:15 pm

ok so sorry for the delay posting a response.
well yes it is 'different' than previous.
when zeugs did this before he wasn't sure if he had done it correctly.
I think you will find he had some unusual values as well.
I have gone about this a different way but I will take a look at what I did again...
the trouble was that the rendered dof effect wasn't strong enough using realistic aperture values and the estimated dof wasn't agreeing with the rendered image either - I have reasonable confidence in the dof calcs being sound.
I set in place calc to generate 0.8mm-5.8mm radius for f64-f1.2 which I think is reasonable but somehow this doesn't equate to a realistic looking blur when rendered.
so there is a fudge factor of 8.6 ( my best estimate) in there ATM - I have asked ono about this discrepency...
.
possibly you should ask yourself if the image looks correct at this point rather than be too concerned that the values are different.. but as I say I will take a look at it again.
please remember this is my variant WIP I give you to test its not 'the' official exporter

neepneep · Post by **neepneep** » Tue Oct 09, 2007 6:41 am

Code: Select all

INDIGO EXPORT

Object Ground in layer 2
Object Grass in layer 2
Object Empty in layer 1
Object Camera in layer 1
Object Sun in layer 1
processing DupObject "Ground"...
Traceback (most recent call last):
  File "<string>", line 2561, in buttonEvt
  File "<string>", line 1962, in exportStill
  File "<string>", line 1933, in export
  File "<string>", line 1624, in exportObjects
  File "<string>", line 1610, in exportObject
TypeError: exportObject() takes exactly 5 arguments (4 given)

I am trying to duplivert/instance a blade of grass onto a static particle emitting plane.

It don't work

BbB · Post by **BbB** » Tue Oct 09, 2007 10:16 am

Hi BigFan. Sorry but I missed the link. I looked and when I looked again it was gone. Could you post it for a second so that I can grab it before it is gone again?

Big Fan · Post by **Big Fan** » Tue Oct 09, 2007 5:55 pm

@neepneep
which exporter version is that you are using?

also what do you mean about 'a static particle emitting plane' ?
the script doesnt handle Blender particles...sorry
if you want to do particles you are going to have to make the particles into meshes somehow... apparently there is a script around somewhere in the blender community for that

@BbB
in your pm

BbB · Post by **BbB** » Tue Oct 09, 2007 6:32 pm

Thanks a zillion BF

Blendigo for v0.9

Who is online