I knew I should’ve waited a few days before downloading 2.67!
very easy! hahah c’mon it is not yes you can fix this in some way. No we should think what to do to don’t have to fix it. add input or output button and that’s it.
If that’s too hard for you then hit Ctrl+Z to bring the node back, but since it bothers you too much go and report it…
I agree that it’s always the same story, fews days/weeks after the main release, a version “a” is available, fixing many bugs.
But as it’s said earlier in this thread, not many people are downloading the RC and using it to work. And among the ones who do it, I guess that not everybody is filling bug reports.
Well… I will see the positive side of all this.
First, there is a simple solution, wait for the “a” version.
Second, I wouldn’t complain about the development of the application because usually, there is no big bug going through several versions. The development team is doing a great job most of the time. When you think about the number of functionalities added during the last months, it’s really impressive to have such a stable application. For free. Some commercial applications cannot compare.
I’m not saying that everything is perfect, I just try to compare the evolution rate with the number of problems and for me, I think the siutation is not too bad.
Let’s blend with the “a” realease 
If that’s too hard for you then hit Ctrl+Z to bring the node back, but since it bothers you too much go and report it…
Of course we should file a report. It is a bug, confirmed on OSX builds as well.
Until everyone has figured that out. Then the solution is to wait for the “b” version…
Or maybe that function is removed because it conflicts with other features, i’m not a coder but reading the commit logs that seems to be the case, Rev 56375
This time, even the fixed version is too buggy for production. I decided to stick with 2.66a
The problem is the blender crashing. Crashing is always an issue.
You guys, That’s not the solution at all. The problem is that to many people just wait and don’t download the RC and find bugs. So when the release comes, it’s full of bug cuz everyone waited. See?
The solution is for everyone who knows the software well and who is not involved in production to download the RC and hammer and report like crazy.
i found something pretty odd while testing the new 2.67a (i am on mac os10.6.8, using version r56914), i wanted testing the new multires performance, as it was said it has improved … and, when i smooth in multiresmode it deletes polygons and makes holes. :-(((
left is object mode, middle sculpt mode, right edit mode…
I’ve been hanging out on this forum for more than two years and I don’t ever remember seeing any mention of an official beta programme for Blender.
I’m sure there are people in the community who would like to contribute, but aren’t programmers, technical writers or what-have-you, so putting together a programme like this should work.
If it’s well-organized, with each person testing a specific part (or sub-part) of Blender and other people testing how various parts work together, the beta testing could be done in a timely manner. It might save the developers an ‘a’ version and give us a more stable and respected end product.
Does anyone here have experience putting together a beta-testing programme?
@doris.
I can’t confirm it. 2.67a 56914 OSX build.
Can you be more specific? Or, maybe you can check if all normals are OK?
michalis, normals are ok. it was after the mesh has produced spike, i don’t know why the spike appeared… i did sculpt only in multires, and actually i never sculpted anywhere close to this area where the spike appeared, but suddenly after a stroke with claytubes brush along the cheek area the spike pooped out … then, i tried to smooth the spike, and the hole was result.
Any luck with remove doubles?
psy-fi, i tried, it has no effect, … i trashed the mesh now , as i could not figure out what was going on, and started new, in older version of blender… my intention was to report that weird things happen in this version,… but, as it seems its a random problem, that cannot be reproduced easily.
Yesterday I came across with the same problem in sculpting mode. Thought that that was my mistake with dynamic topology, and the hole appeared after a little spike. Unfortunatly didnt save the file. Im on win7