Page MenuHome

Defocus - not able to set fstop value
Closed, ArchivedPublicKNOWN ISSUE

Description


I made a basic scene with just one light and a bunch of cubes, to try out the defocus node filter.

I turned on the DofDist on the camera to point at the front of the cube I wanted to focus on. Also turned on "Do composite" in the render buttons.

Now on to the nodes editor.

If I turn off the "no z buffer" option in the Defocus filter node, it will then
show the fstop button. However, when I adjust the fstop value, after I release the mouse button (I adjust it by clicking down with the mouse, and moving leftward), after I releae the mouse button, the fstop button disappears, and the "no z buffer" button re-enables itself. I then cannot disable it again at all.

So the problem is I can't adjust the node's fstop value, it keeps turning off and switching back to "no z buffer" option, which I don't want.

Event Timeline

Logged In: YES
user_id=103

I cannot redo this... We need more information:

- what OS you use, what gfx card?
- what build is this, is the build reliable? (get the official 2.43 RC from blender.org)
- can you verify if this is maybe a redraw error (move view around a bit with middlemouse)
- make a .blend file for us, there might be something else...

Logged In: YES
user_id=4923

Oh man, I am such an idiot, I'm sorry I should have given more info

This is on Windows XP pro with SP2, on a Pentium D (dual core) 3.4 ghz system, with an Intel 82945G display chipset.

The build is the official 2.43RC1 install.

It does seem to be redraw issue, since it flickers a lot. I will try it out on my other system, that has an nvidia card.

Logged In: YES
user_id=103

Ahh, the intel chipset is really really bad!

Logged In: YES
user_id=4923

you can cancel this bug, it was an error on my part, I did not connect the z buffer correctly

This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.

Matt Ebb (broken) changed the task status from Unknown Status to Unknown Status.Mar 26 2010, 6:30 AM