Developer Meeting Notes, July 22, 2012
Ooooh :)
Ton Roosendaal writes:Hi all,
Here’s the notes from today’s meeting in irc.freenode.net #blendercoders:
1) Blender 2.64 – upcoming release
- The bug tracker is still on 300 open issue, a too high total!
- Release notes: Sergey Sharybin started to list bugfixes, but needs help.
- OpenColorIO work stays in Tomato branch for now, but can go to trunk – if finished & tested & approved at least.
- Jens Verwiebe suggests to make multitouch / trackpads support a user-preference option, easier to control behaviour that way (as opposed to automatic checks).
- Collada reports: these were moved to the todo wiki in the past. Now it can get accepted in tracker and assigned to Gaia Clary.
- Campbell Barton: new mask rasterizer now is finished – it also supports unfilled curves (nice for masking out wires) and different interpolation falloff.
- Mask UI is still messy, will get cleaned/improved. A doc needs to be published still too, this will clear up confusion as well.
- Voronoi fracture now is usable: recursion bugs and a bad crash were fixed.
2) Other projects
- code.blender.org blog: Ton Roosendaal reminds everyone to also use it to copy over posts from own blogs.
3) Google Summer of Code
- Alex Kuznetsov released a new Android Blender game player. It now supports mouse emulation and .blend reading.
- Nicholas Rishel: will check with Alex on multitouch ghost help
- Miika Hamalainen added smoke color – see video above.
Great to see developments on smoke sims and android! All the best to the devs and GSoC guys!
any news on freestyle?
AMD/OpenCL support in Cycles?
This will come when AMD fix their drivers… it is not a programming fault, its a bad implementation of the OpenCL specification on AMD’s part
More info on the AMD difficulties with OpenCL:
https://www.linux.com/news/featured-blogs/147:high-performance/533055:amds-opencl–the-good-the-bad-and-the-ugly
Oh, so many bugs! If they were in Python code only, I could help. C and C++ is still alien world for me.
Thanks everyone for your hard work. Just a point about the smoke sim. I’ve always had to adjust the domain due to clipping. And it is doing the same in the example (watch the top of the sim). Suggest a manual offset with the auto resizing of the domain.
this is not really necessary anymore, because we have adaptive and animatable domain already. you can scale the domain to whatever size you want without slowing down simulation times, because it reduces the necessary cells to calculate dynamically. i just forgot to scale the domain to a size where the smoke doesn’t hit the walls.
But it runs into the top!
I gave a look at the bug tracker as I know both Python ad C++. I must admit I don’t know really where to start. The bugs there seem VERY specific, nested in systems that require special knowledge (rendering, physics sim…). This is a side effect of getting high end features inside : you get high end bugs :)
I Agree… I know Python and C/C++ but there is so much code to look at that it’s almost scary…
There are a few good coding resources for Blender these days, plus the irc channel is active and friendly.
https://www.youtube.com/watch?v=_kniMTbcCko
https://www.youtube.com/watch?v=5Ymoav0nNWQ
for starters
more stabile exporter for indigo renderer
I agree , if blender wants to really fight those bugs 2 things must happend
a) Better documentation of the code , plus cleaner code
b) Start porting code to python (yes it can be done without slowing down Blender)
Blender may need to have some releases focusing only on bugs and force developers to concetrate on bugs. I am a developer , I hate fixing bugs like the next guys but it needs to get done and I do it.
all non edited primatives segments could be changable
(now short time could use, after added another previus could not editable)
The bug tracker is still at 300?
This is madness!
so you can help to cut off some “non-bugs” or tell reporters about incomplete reports.
No this is SSSSSSparta! Just kidding. :P
That was exactly the response I was waiting for, so thank you. ;)
Your welcome. :)
I would really like to hear news from the outline modifier. It seems like such an AWESOME tool for presenting technical machines. Edge rendering just isn’t good enough for that.
Collada go away from newest builds?
IM TIRED OF ALL THIS NEWS BUGS HERE BUGS THAT JUST GET MAYA 2013 FOR GOD SAKE
A big thak you to the development team, guys, you have been doing a great effort on this wonderful software!
Regarding bugs:
You need multiple domains to fix bugs sadly. Not only a person must understand C/C++ or Python, but also the mathematics / logic / physics behind the bugs itself. And depending on the domain, that could include other libraries, or api (read: windows file system, etc).
At least that is my understanding…
Yeah, I do download the code via TortoiseSVN, its not scary, but yeah, complex for a beginner like me.
Glow material for Cycles
Cycles documents, tutorials, material database