Cambo I’m having some troubles with the Library module… it crashes Blender when appending objects , using python , that were saved using 2.42a or prior. It appends camera with no trouble but meshes and particle systems just crash RC1.
Bug? or the module is under still under unfinished changes? I know its now a module used very often…
As for future developments I’m looking forward to - a native UI toolkit like scriptUI, and better integration with Blender interface. It would be great to get a reference to the Blender buttons window, add a new panel to the objects tab, then populate it with some custom object controls. Being able to create custom floating panels is also an often requested feature. Unfortunately the event refactor probably needs to happen before these, or everything may fall a part when the event system changes…
kitsu, yes- we definetly need a better way for python scripts to use the UI and manage events, and yes this will need to wait a release.
I think somebody was working on this so its do’able but better wait.
Another thing thats possible is an editmesh wrapper. so mesh tools can avoid switching in and out of editmode. Editmesh data structure will hopefully be rewritten to be more efficient and allow python to better interface it.
Iv got the basics working for a Sequencer API as well (can loop through sequencer strips, move them, and get data from them, as well as loop through nested metastrips), so that opens up blender video editor for scripts to automate tasks, effects as well as import formats such as
It would be really nice if you could add the constant Pose.QUAT into the Blender.Object.Pose module, it seems that for now it’s not possible to update PoseBone using Quat.
Thanks a lot ideasman! However, it still doesn’t solve the problem with the rotations/translations of the PoseBones, I already mentioned all the problems with the Armature and PoseBone modules in this thread: http://blenderartists.org/forum/showthread.php?t=85970 . Would it be possible for you have a look? Please let me know if you wish to see the data and code I used. Thanks a lot!!
Hi, it seems zmat.mode |= Material.Modes.ZTRANSP | Material.Modes.RAYTRANSP has stopped working. The UI also now refuses to allow me to set both. The net effect of this is, so far as I can see, that I can’t have raytraced transparency with raytraced renders and z-buffer transparency with scanline renders … unless I want to go reset every material’s transparency bits individually every time I switch from one kind of render to another.
Yeah, I forgot about the sequencer! That was a request of mine several months ago. Now though I mainly use the compositor. I’m not sure how you would go about making an API for the node windows though…
jthill - looks like blenders changed the way it works, best take it up with bf-funboard mailing list,
Kitsu
This is one of the things Im wonderuing about now, do we want to wrap ‘everything’, making python access to nodes may not be toooo hard, but Im not sure its worth doing. - Another eg is adding Python support for modifying blenders ‘brushes’ used for image painting and sculpting.
at any rate, for compositing its probably best we wait until the internals are set in stone, and talk to Ton and see what he thinks about adding python access. - bascly after 2.43 release.
I foresee broken scripts with some of these changes. (existing scripts). Growing pains I guess…
I would like to see python commands to generate all the primitives that are available in the menu system of blender. They obviously exist if the interface can generate them.
I have also posted concerns about how variables fall out of scope with script events. What I would like to see there is an INIT area for script events
I’d like a way to find out which IPO curve and IPO a user has selected. I know you can try to work out which IPO connected to a selected object, but you can also select an IPO curve in the IPO window and it would be really useful for me to find out which it is.
If you already know a way of finding this, please let me know!
O… and good work btw
Thanks J
not exactly an api request, but it would be nice to have external files for each material (e.g. glass.xml, coffe.xml) and a drag and drop interface for the materials. So you could go to the materials editor, and simply drag and drop the material file onto the material editor.
dunno, just my 2 cents
except for …
DDS support, I think were going the File OpenEXR route instead.
MP3/Ogg- nothing todo with python?
Seperate by material is a blender function. not hard to do in Python. - could be wrapped still.
Just added stress and tangent mapping options and IpoCurve.sel.
deltaepsylon: This would be pretty easy to do through Python (maybe even with drag and drop), but isn’t it easier to just use a blend file and the append function? You could even write a nice Python script to manage/automate your blend file material and texture collection!
Cambo: I just downloaded a fresh cvs build yesterday and it has an old version of my dxf script included I think. Can you make sure the freshest version is in cvs and that the dxfimportobjects module is removed? Actually I just finished a complete rewrite of the dxfReader module too, but it probably isn’t ready for inclusion…