Blender 2.61 is approaching fast; Bcon4 (the development phase where a release candidate is prepared - see the Blender Release Cycle) is today.
Ton Roosendaal writes:
1) Blender 2.61 release progress
- Translation (.po) files: will be added to svn tomorrow by Bastien Montagne. Meeting agrees that .po files should be added before we enter BCon4 (official release candidate builds).
- Motion tracker:
- Keir Meirle has updated solvers, using a hybrid of previous methods. Camera tracking is working great.
- Sergey Sharybin was trying to finish object tracking as well, but couldn't finish it today yet.
- Meeting then spent a long time on pros and cons of having last minute cool features - like object tracking. Basically the module owner (Sergey) could decide it's good enough to add today or tomorrow. But if it needs more time (week or more) to mature, it's better to wait. Sergey thinks he'll wait for 2.62 with it... but we don't exclude a miracle. :)
- As planned, we move to BCon4 tomorrow: all work for release has been wrapped up, we make release candidates and focus on essential bug fixes only.
- Release Candidate build call: this Tuesday evening (EU time).
- NOTE!! Files saved with svn trunk Blender, between Nov 29 and Dec 4, have a delta scaling issue, which makes objects appear zero scaled. Best solution then is to run this 1 liner in the python terminal: >>> for ob in bpy.data.objects: ob.delta_scale = (1,) * 3
- To get ready for a fabulous release, we do a call for demos! We can use excellent files to show all the new features in 2.61. Mail links to files to this list?
- Thomas Dinges added a cool Cycles test material blend file in svn:
2) Other projects
- Antonis Ryakiotakis (Psy-Fi) worked on improved selection code, it appears ATI cards keep badly supporting OpenGL's standard (but ancient) glSelect() function. More tests will be needed; especially if ATI/AMD really didn't fix this in last year...
- Campbell Barton reminds everyone about the BMesh compatibility issue: is it needed to save out in new .blend files Meshes that will read in old binaries still? Ton suggests to make decision next week, after examining issue closer.
-Ton-
24 Comments
Great job everyone involved! 2.61 gonna be fantastic :-)
Very interesting read about the selection issue with graphics cards drivers!
BMesh nears trunk merge ;-)
Probably not the best place to write about it but I get an odd reaction (bug?) when using Blender 2.60a. I use cycles and have no issues when rendering and all but Blender freezes when hitting Tab to move from object to edit mode (especially when trying to do so on appended/imported objects). The freeze is followed by a Windows blue screen (Win XP Pro) and my PC restarts. My GPU is Nvidia GTS 450.
Anyone else having the same issue?
On topic: Great job everybody!!! Can't wait for 2.61!
Use an up-to-date OS, check your graphics drivers, file a bug report.
You're right but it's weird that I never had such issues when using Cycles builds from graphicall.
Can't wait for the official release of Camera Tracking and Cycles. Using Blender for visual effects in live-action movies is a BIG step up for the Blender. Great job everyone!
Hello to all,firstly let me thanks all the Devs for their hard work. I know its not the place for putting this but I'm having rendering problem with cycle. Putting it simple, I have a glossy plane on which I apply a normal map. Small holes are rendered everywhere, even though the normal map is rendered well.
If this is already fixed then great but for the work now I have to use geometry instead of normal maps.
Thanks for everything.
"NOTE!!
Files saved with svn trunk Blender, between Nov 29 and Dec 4, have a
delta scaling issue, which makes objects appear zero scaled. Best
solution then is to run this 1 liner in the python terminal:
for ob in bpy.data.objects: ob.delta_scale = (1,) * 3
thanks god, this command saved me from a heart attack, for noobs like me, enter this command inside blender in the console window a hit the Enter button twice !
Love to hear of the selection slowness getting some attention
If it were me, I would write “(1,1,1)” instead of “(1,) * 3”. Saves one keystroke. :)
A big Thank you! goes out to all the DEVS .
Not sure what's happening here, but the scale on some of the objects in the test scene are WAY out for me when I downloaded??
Oh and I tried to copy the script from eMirage in the comments above, and I executed in the python window, but nothing seemed to change?? I must be doing something wrong.
for ob in bpy.data.objects: ob.delta_scale = (1,) * 3
copy the line above and past it on the console inside blender, to get the console select it from the icon on the bottom left, past the code and hit the Enter button twice,
it worked for me on two different blend files; hope the same for you !
This is just weird, I open the .blend file, change the text area to a python console screen. enter the text:
for ob in bpy.data.objects: ob.delta_scale = (1,) * 3
hit enter twice..... and..... nothing happens.... everything is still out of scale.
I dunno what I am doing wrong. maybe someone will upload a fixed version later.
maybe it works only with recent builds, I'm using the r42420
Great work everyone, appreciate the re-posting the notes here and look forward to playing with final builds, having some great fun with test builds from Graphicall! :D
Files saved with svn trunk Blender, between Nov 29 and Dec 4, have a
delta scaling issue, which makes objects appear zero scaled. Best
solution then is to run this 1 liner in the python terminal:
for ob in bpy.data.objects: ob.delta_scale = (1,) * 3
That's great! Thanks a lot to all developers :)
this one liner does not seem to work for me??
I open the .blend file, change the text area to a python console screen. enter the text:
for ob in bpy.data.objects: ob.delta_scale = (1,) * 3
hit enter twice..... and..... nothing happens.... everything is still out of scale.
Could I be doing something wrong?
Can someone update me on the whole Cycles - OpenCL (AMD Cards) stuff?
What's ATI doing wrong and how can we help it? I could spam AMD all day asking friendly how things work.... But I could also mail them with questions to support OpenCL better? I just have no idea what's wrong so please tell me :)
Next week AMD will release Catalyst 11.12 with new OpenCL drivers. Those should fix the OpenCL problem.
Psy-Fi I think I love you.
Your selection improovement is awesome!
About bmesh, would it be possible to have both object types. The mesh and also the bmesh types with a converter allowing to convert in both ways(old and new). This is like in 3ds max which has mesh objects and poly objects. I don't think it is an elegant solution to keep in all future versions but I think it could be interesting to have both in at least one blender version.