I don’t know if this is a bug, but I noticed that in 2.32, by default, both layers 1 and 2 are selected. Does anyone know if there is a reason for this?
Tsk, still no bug tracker report … I have a fix
on my hard drive for the original bug in this post that
I’m too lazy to commit until a certain somebody
posts the bug in the bug tracker.
… and as for the rest of you: shame on you too!
Chris
lol, hos, this thread it a good thing, because it will help us to sort out what is actually a bug before we go troubling you and others with it.
I think you miss what Hos is saying: If folks here are too lazy to report a bug (or a percieved bug, they have a filtering procedure at the tracker) then why should he take the time to scour the forums (here, blenderwars, nicodigital, French and Polish) to look for discussion. These guys are BUSY and we all know that. Let’s work with them!
%<
One of my friends found a bug with the Yafray integration earlier today; I’m posting it here because I’m not sure if it is just not supported yet, or is a problem with the current implementation.
The presence of empties deos not present a problem in a scene to be rendered, but as soon as an object is parented to an empty, Blender gives this error message in the Yafray render:
Starting scene conversion.
Added original matrix
Added dupli matrix for linked data object OBEmpty
Scene conversion done.
ERROR: Duplilist non_empty, but no srcobs
Any ideas?
Matt
GreyBeard: It might help to use “No V.Normal Flip” mode (button under “Double Sided”).
viktorivar
This is almost certainly 2.32 related, since I haven’t done anything else that could possibly affect it :
Since I installed 2.32, Ripsting’s Fiber 2.0.2 script refuses to work, under any Blender version. Worked very well only a few days ago, now I just get silly “No module named dynoise” (even though the dll is in the correct directory) or sometimes “No module named Fiber” error messages. Tried reinstalling python 2.2.2, no luck. Grrrr…
Q: I’m not sure if a bug has been reported already.
A: If it’s not there, it’s not officially reported.
Q: I’m not even sure if it’s a bug.
A: If it’s not, it will be filtered out.
Q: Even if it’s about the YafRay integration?
A: YES!
Martin
meestaplu, I’m getting the same error here.
Humm… I feel alluded somehow (LOL 
)
Bug-tracker report done under Request-ID #955, plus another old bug that has been ¨bugging¨ me since a long time. (Request-ID #956).
Hos, thanks.
Thy bug is fixed (#955).
Thank you for shopping the blender bug tracker! =D
Chris
This one is a bit strange to describe so I’ll just mention the symptom:
bones in one armature that were constrained to bones in another
armature, which in turn were constrained to a non-armature object
weren’t getting updated correctly.This fixes bf-blender bug #955 (thanks Appolux).
Thank YOU Hos!!. Any luck with #956? (On the bug-tracker #955 appears as still open, somebody please close it).
By the way, I’m Apollux, with double L. But that isn’t that important.