Re: [Bf-committers] Node type OUTPUT_MATERIAL undefined
Sorry, should have documented these changes better.
Here is a simple wiki page to collect all changes. The identifier
string change you ran into is the most important, most other things
should still work. Please let me know if you encounter more problems
of this sort:
http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes
The sphinx error seems to be a missing default value in RNA, will try
to track it down.
On Tue, Mar 19, 2013 at 2:33 AM, INTERLICHTSPIELHAUS
interlichtspielh...@gmail.com wrote:
hi
just did a fresh svn update
and a script just broke
i am creating a new shadernode with the following line
out_node = nodeTree.nodes.new('OUTPUT_MATERIAL')
i receive the following color
RuntimeError: Error: Node type OUTPUT_MATERIAL undefined
could someone point me to online dox with the recent python api changes ?
when i try to run sphinx_doc_gen.py locally
i get the following output + segmentation fault
/home/interlichtspielhaus/blender/doc/python_api/rst/bmesh.ops.rst
RNA Warning: Current value 0 matches no enum in 'EnumProperty',
'addon_filter', 'default'
./blender() [0x95f41e]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fd9dd28c4a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x162c01) [0x7fd9dd3b8c01]
./blender(StringProperty_default_value_length+0x2b) [0x139772b]
./blender(RNA_property_string_length+0x61) [0x12fd831]
./blender(RNA_property_string_get_alloc+0x36) [0x12fd896]
./blender(pyrna_prop_to_py+0x168) [0xcc0b98]
./blender() [0xcc0ec0]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0xbf9cb) [0x7fd9e1aea9cb]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x6003)
[0x7fd9e1a92743]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b)
[0x7fd9e1a9593b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyRun_FileExFlags+0xb9)
[0x7fd9e1bdefc9]
./blender() [0xcb6f96]
./blender() [0x95e871]
./blender(BLI_argsParse+0xc7) [0xf82e97]
./blender(main+0xace) [0x9404fe]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fd9dd27776d]
./blender() [0x95e089]
thanks
inS
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] PyNodes branch merge
Made a temporary wiki page to collect API changes. Is there a preferred place to put this other than my personal pages? http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes On Mon, Mar 18, 2013 at 5:35 PM, Lukas Tönne lukas.toe...@gmail.com wrote: It's finally happening, PyNodes branch (aka custom nodes) ready for merge into trunk. PyNodes opens up the node system in Blender to scripters and adds a number of UI-level improvements. === Dynamic node type registration === Node types can now be added at runtime, using the RNA registration mechanism from python. This enables addons such as render engines to create a complete user interface with nodes. Examples of how such nodes can be defined can be found in my personal wiki docs atm [1] and as a script template in release/scripts/templates_py/custom_nodes.py [2]. === Node group improvements === Each node editor now has a tree history of edited node groups, which allows opening and editing nested node groups. The node editor also supports pinning now, so that different spaces can be used to edit different node groups simultaneously. For more ramblings and rationale see (really old) blog post on code.blender.org [3]. The interface of node groups has been overhauled. Sockets of a node group are no longer displayed in columns on either side, but instead special input/output nodes are used to mirror group sockets inside a node tree. This solves the problem of long node lines in groups and allows more adaptable node layout. Internal sockets can be exposed from a group by either connecting to the extension sockets in input/output nodes (shown as empty circle) or by adding sockets from the node property bar in the Interface panel. Further details such as the socket name can also be changed there. For the next release (2.67) i will update the official wiki pages as well. The wiki node docs are totally outdated anyway (still on 2.49 level in many parts). I'd like to make a general section about common node editor tools. Docs about the python API and registration should probably go to the bpy reference docs as examples [4] Please report any possible bugs you encounter to the bug tracker [5]. Regards, Lukas Tönne [1] http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes [2] http://projects.blender.org/scm/viewvc.php/trunk/blender/release/scripts/templates_py/custom_nodes.py?view=markuproot=bf-blender [3] http://code.blender.org/index.php/2012/01/improving-node-group-interface-editing/ [4] http://www.blender.org/documentation/blender_python_api_2_66a_release/bpy.types.NodeTree.html [5] http://projects.blender.org/tracker/?atid=498group_id=9func=browse ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] PyNodes branch merge
Maybe add a page in the release notes: http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.67 On Tue, Mar 19, 2013 at 10:50 AM, Lukas Tönne lukas.toe...@gmail.com wrote: Made a temporary wiki page to collect API changes. Is there a preferred place to put this other than my personal pages? http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes On Mon, Mar 18, 2013 at 5:35 PM, Lukas Tönne lukas.toe...@gmail.com wrote: It's finally happening, PyNodes branch (aka custom nodes) ready for merge into trunk. PyNodes opens up the node system in Blender to scripters and adds a number of UI-level improvements. === Dynamic node type registration === Node types can now be added at runtime, using the RNA registration mechanism from python. This enables addons such as render engines to create a complete user interface with nodes. Examples of how such nodes can be defined can be found in my personal wiki docs atm [1] and as a script template in release/scripts/templates_py/custom_nodes.py [2]. === Node group improvements === Each node editor now has a tree history of edited node groups, which allows opening and editing nested node groups. The node editor also supports pinning now, so that different spaces can be used to edit different node groups simultaneously. For more ramblings and rationale see (really old) blog post on code.blender.org [3]. The interface of node groups has been overhauled. Sockets of a node group are no longer displayed in columns on either side, but instead special input/output nodes are used to mirror group sockets inside a node tree. This solves the problem of long node lines in groups and allows more adaptable node layout. Internal sockets can be exposed from a group by either connecting to the extension sockets in input/output nodes (shown as empty circle) or by adding sockets from the node property bar in the Interface panel. Further details such as the socket name can also be changed there. For the next release (2.67) i will update the official wiki pages as well. The wiki node docs are totally outdated anyway (still on 2.49 level in many parts). I'd like to make a general section about common node editor tools. Docs about the python API and registration should probably go to the bpy reference docs as examples [4] Please report any possible bugs you encounter to the bug tracker [5]. Regards, Lukas Tönne [1] http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes [2] http://projects.blender.org/scm/viewvc.php/trunk/blender/release/scripts/templates_py/custom_nodes.py?view=markuproot=bf-blender [3] http://code.blender.org/index.php/2012/01/improving-node-group-interface-editing/ [4] http://www.blender.org/documentation/blender_python_api_2_66a_release/bpy.types.NodeTree.html [5] http://projects.blender.org/tracker/?atid=498group_id=9func=browse ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] Google Summer of Code 2013
Hi all, It's the time of the year again! GSoC 2013 starts soon. Here are important dates to mark in calendars: April 8: Google announces if we're accepted as Mentor organization. April 22: Students can start applications May 3: Student application deadline May 27: Google announces accepted students June 17: GSoC official start August 2: Midterm evaluation deadline Sept 23: Pencils down Sept 27: Final evaluation deadline Note that the program runs longer than previously, with a lot of time for us to review student proposals, and a 3 month period for students to work. Work for the active devs during the next weeks is to fill in project proposals for the Ideas page. This is not for feature requests! We should stick to well defined acceptable targets for which we know a developer/mentor can be found. http://wiki.blender.org/index.php/Dev:Ref/GoogleSummerOfCode/2013/Ideas For GSoC 2013 I would like to introduce a special focus: we could organize a stronger connection between the stakholders (users) and students/mentors. Speficially I'd like to invite teams/studios to think of useful targets, to define projects they really need (and will use), and to get involved as artist-buddies for the students. Discussions can be here and in irc as usual. Early april a 'mentors' mailing list will be opened as well, for developers and reviewers of student applications. Laters, -Ton- Ton Roosendaal Blender Foundation t...@blender.orgwww.blender.org Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Node type OUTPUT_MATERIAL undefined
On Tue, Mar 19, 2013 at 8:49 PM, Lukas Tönne lukas.toe...@gmail.com wrote:
Sorry, should have documented these changes better.
Here is a simple wiki page to collect all changes. The identifier
string change you ran into is the most important, most other things
should still work. Please let me know if you encounter more problems
of this sort:
http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes
The sphinx error seems to be a missing default value in RNA, will try
to track it down.
On Tue, Mar 19, 2013 at 2:33 AM, INTERLICHTSPIELHAUS
interlichtspielh...@gmail.com wrote:
hi
just did a fresh svn update
and a script just broke
i am creating a new shadernode with the following line
out_node = nodeTree.nodes.new('OUTPUT_MATERIAL')
i receive the following color
RuntimeError: Error: Node type OUTPUT_MATERIAL undefined
could someone point me to online dox with the recent python api changes ?
when i try to run sphinx_doc_gen.py locally
i get the following output + segmentation fault
/home/interlichtspielhaus/blender/doc/python_api/rst/bmesh.ops.rst
RNA Warning: Current value 0 matches no enum in 'EnumProperty',
'addon_filter', 'default'
./blender() [0x95f41e]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fd9dd28c4a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x162c01) [0x7fd9dd3b8c01]
./blender(StringProperty_default_value_length+0x2b) [0x139772b]
./blender(RNA_property_string_length+0x61) [0x12fd831]
./blender(RNA_property_string_get_alloc+0x36) [0x12fd896]
./blender(pyrna_prop_to_py+0x168) [0xcc0b98]
./blender() [0xcc0ec0]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0xbf9cb) [0x7fd9e1aea9cb]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x6003)
[0x7fd9e1a92743]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b)
[0x7fd9e1a9593b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyRun_FileExFlags+0xb9)
[0x7fd9e1bdefc9]
./blender() [0xcb6f96]
./blender() [0x95e871]
./blender(BLI_argsParse+0xc7) [0xf82e97]
./blender(main+0xace) [0x9404fe]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fd9dd27776d]
./blender() [0x95e089]
thanks
inS
The crash isnt caused by pynodes, rather BLF_I18NCONTEXT_DEFAULT being NULL,
This gets passed to RNA as the default translation context - and rna
functions don't check for a null default when getting that string.
Bastien, you added comment about why having BLF_I18NCONTEXT_DEFAULT
set to NULL is important, any suggestions on how to fix?
--
- Campbell
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Node type OUTPUT_MATERIAL undefined
Ek… Didn’t thought it could cause crashes (had no problems during my
tests here... :/ ).
Anyway, current situation is a bit fuzzy, I already intended to clean it
up so that RNA-related stuff always use BLF_I18NCONTEXT_DEFAULT_BPY, as
py stuff, instead of the NULL BLF_I18NCONTEXT_DEFAULT one. Will do that
asap.
Bastien
On 19/03/2013 14:17, Campbell Barton wrote:
On Tue, Mar 19, 2013 at 8:49 PM, Lukas Tönnelukas.toe...@gmail.com wrote:
Sorry, should have documented these changes better.
Here is a simple wiki page to collect all changes. The identifier
string change you ran into is the most important, most other things
should still work. Please let me know if you encounter more problems
of this sort:
http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes
The sphinx error seems to be a missing default value in RNA, will try
to track it down.
On Tue, Mar 19, 2013 at 2:33 AM, INTERLICHTSPIELHAUS
interlichtspielh...@gmail.com wrote:
hi
just did a fresh svn update
and a script just broke
i am creating a new shadernode with the following line
out_node = nodeTree.nodes.new('OUTPUT_MATERIAL')
i receive the following color
RuntimeError: Error: Node type OUTPUT_MATERIAL undefined
could someone point me to online dox with the recent python api changes ?
when i try to run sphinx_doc_gen.py locally
i get the following output + segmentation fault
/home/interlichtspielhaus/blender/doc/python_api/rst/bmesh.ops.rst
RNA Warning: Current value 0 matches no enum in 'EnumProperty',
'addon_filter', 'default'
./blender() [0x95f41e]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fd9dd28c4a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x162c01) [0x7fd9dd3b8c01]
./blender(StringProperty_default_value_length+0x2b) [0x139772b]
./blender(RNA_property_string_length+0x61) [0x12fd831]
./blender(RNA_property_string_get_alloc+0x36) [0x12fd896]
./blender(pyrna_prop_to_py+0x168) [0xcc0b98]
./blender() [0xcc0ec0]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0xbf9cb) [0x7fd9e1aea9cb]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x6003)
[0x7fd9e1a92743]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b)
[0x7fd9e1a9593b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyRun_FileExFlags+0xb9)
[0x7fd9e1bdefc9]
./blender() [0xcb6f96]
./blender() [0x95e871]
./blender(BLI_argsParse+0xc7) [0xf82e97]
./blender(main+0xace) [0x9404fe]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fd9dd27776d]
./blender() [0x95e089]
thanks
inS
The crash isnt caused by pynodes, rather BLF_I18NCONTEXT_DEFAULT being NULL,
This gets passed to RNA as the default translation context - and rna
functions don't check for a null default when getting that string.
Bastien, you added comment about why having BLF_I18NCONTEXT_DEFAULT
set to NULL is important, any suggestions on how to fix?
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Node type OUTPUT_MATERIAL undefined
How do I add 'REROUTE' node now?
I tried 'CompositorNodeReroute', but it doesn't work.
Bartek Skorupa
www.bartekskorupa.com
On 19 mar 2013, at 10:49, Lukas Tönne lukas.toe...@gmail.com wrote:
Sorry, should have documented these changes better.
Here is a simple wiki page to collect all changes. The identifier
string change you ran into is the most important, most other things
should still work. Please let me know if you encounter more problems
of this sort:
http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes
The sphinx error seems to be a missing default value in RNA, will try
to track it down.
On Tue, Mar 19, 2013 at 2:33 AM, INTERLICHTSPIELHAUS
interlichtspielh...@gmail.com wrote:
hi
just did a fresh svn update
and a script just broke
i am creating a new shadernode with the following line
out_node = nodeTree.nodes.new('OUTPUT_MATERIAL')
i receive the following color
RuntimeError: Error: Node type OUTPUT_MATERIAL undefined
could someone point me to online dox with the recent python api changes ?
when i try to run sphinx_doc_gen.py locally
i get the following output + segmentation fault
/home/interlichtspielhaus/blender/doc/python_api/rst/bmesh.ops.rst
RNA Warning: Current value 0 matches no enum in 'EnumProperty',
'addon_filter', 'default'
./blender() [0x95f41e]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fd9dd28c4a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x162c01) [0x7fd9dd3b8c01]
./blender(StringProperty_default_value_length+0x2b) [0x139772b]
./blender(RNA_property_string_length+0x61) [0x12fd831]
./blender(RNA_property_string_get_alloc+0x36) [0x12fd896]
./blender(pyrna_prop_to_py+0x168) [0xcc0b98]
./blender() [0xcc0ec0]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0xbf9cb) [0x7fd9e1aea9cb]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x6003)
[0x7fd9e1a92743]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b)
[0x7fd9e1a9593b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyRun_FileExFlags+0xb9)
[0x7fd9e1bdefc9]
./blender() [0xcb6f96]
./blender() [0x95e871]
./blender(BLI_argsParse+0xc7) [0xf82e97]
./blender(main+0xace) [0x9404fe]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fd9dd27776d]
./blender() [0x95e089]
thanks
inS
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Google Summer of Code 2013
On Tue, Mar 19, 2013 at 6:15 AM, Ton Roosendaal t...@blender.org wrote: For GSoC 2013 I would like to introduce a special focus: we could organize a stronger connection between the stakholders (users) and students/mentors. Speficially I'd like to invite teams/studios to think of useful targets, to define projects they really need (and will use), and to get involved as artist-buddies for the students. Ton, it would be good if you, brecht, Campbell and Sergey (and others) can brainstorm for what things would be useful for the next film. Ie what parts of the film (rendering, compositing, animating, modeling, texturing, cloth, physics and other simulations etc.) will be most labor and time intensive and then create a wishlist based on that. I'm sure there are probably useful papers from siggraph and other conferences that might be worth suggesting based on that. LetterRip ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Node type OUTPUT_MATERIAL undefined
Please don't mind my previous question. Found it.
nodes.new('NodeReroute')
Bartek Skorupa
www.bartekskorupa.com
On 19 mar 2013, at 15:10, Bartek Skorupa (priv)
bartekskor...@bartekskorupa.com wrote:
How do I add 'REROUTE' node now?
I tried 'CompositorNodeReroute', but it doesn't work.
Bartek Skorupa
www.bartekskorupa.com
On 19 mar 2013, at 10:49, Lukas Tönne lukas.toe...@gmail.com wrote:
Sorry, should have documented these changes better.
Here is a simple wiki page to collect all changes. The identifier
string change you ran into is the most important, most other things
should still work. Please let me know if you encounter more problems
of this sort:
http://wiki.blender.org/index.php/User:Phonybone/Python_Nodes/API_changes
The sphinx error seems to be a missing default value in RNA, will try
to track it down.
On Tue, Mar 19, 2013 at 2:33 AM, INTERLICHTSPIELHAUS
interlichtspielh...@gmail.com wrote:
hi
just did a fresh svn update
and a script just broke
i am creating a new shadernode with the following line
out_node = nodeTree.nodes.new('OUTPUT_MATERIAL')
i receive the following color
RuntimeError: Error: Node type OUTPUT_MATERIAL undefined
could someone point me to online dox with the recent python api changes ?
when i try to run sphinx_doc_gen.py locally
i get the following output + segmentation fault
/home/interlichtspielhaus/blender/doc/python_api/rst/bmesh.ops.rst
RNA Warning: Current value 0 matches no enum in 'EnumProperty',
'addon_filter', 'default'
./blender() [0x95f41e]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fd9dd28c4a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x162c01) [0x7fd9dd3b8c01]
./blender(StringProperty_default_value_length+0x2b) [0x139772b]
./blender(RNA_property_string_length+0x61) [0x12fd831]
./blender(RNA_property_string_get_alloc+0x36) [0x12fd896]
./blender(pyrna_prop_to_py+0x168) [0xcc0b98]
./blender() [0xcc0ec0]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0xbf9cb) [0x7fd9e1aea9cb]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x6003)
[0x7fd9e1a92743]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x59f5)
[0x7fd9e1a92135]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5f62)
[0x7fd9e1a926a2]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x816)
[0x7fd9e1a95656]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b)
[0x7fd9e1a9593b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyRun_FileExFlags+0xb9)
[0x7fd9e1bdefc9]
./blender() [0xcb6f96]
./blender() [0x95e871]
./blender(BLI_argsParse+0xc7) [0xf82e97]
./blender(main+0xace) [0x9404fe]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fd9dd27776d]
./blender() [0x95e089]
thanks
inS
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] MSVC2010 maintainer? Python 3.3 libs missing, or only me?
Good idea. Let's drop VS2008 :) Cheers, Morten. On Sun, Mar 17, 2013 at 3:32 AM, Thomas Dinges blen...@dingto.org wrote: Hi, I was never a fan of those mixed repositories, and the few vc2010 libs we have only work with cmake as well. Whatever we do, one day we really need to get rid of the old VC2008 crap... Most Blender users use Windows and we use a 6 year old compiler here. I have no idea if current VC20112 is better, produces faster code etc, but there must be something that we can do. It always hurts when I compare Blender Render performance between VC2008 and GCC/MinGW :/ Best regards, Thomas Am 17.03.2013 05:40, schrieb Alexandr Kuznetsov: Hi. I think we can drop vc10 for several reasons: 1) No one actively maintains it. 2) Visual Studio 2010 works fine with regular libs if vs2008 is installed. Also all c-only libs are working perfectly with all compilers! C++ lacks standard ABI afaik. 3) VS 2012 Personally, I switch to 2012 version (after disabling Cap Locks menus). Most libs work fine. Also, I think we should support only x64 for non standard compilers (aka not vc2008). People who download custom builds, probably have modern x64 system. It was 5 years of windows x64 (not counting xp). Best, Alex. On 3/15/2013 7:28 PM, Dalai Felinto wrote: Hi, is there any update on this? If we can't have all the libs working for vc10 I propose we simply drop support for msvc10 and remove the other libs for vc10 that are already in the repository. Better than mislead people to download the libs and frustrating them with a half-working setup. Thanks, Dalai blendernetwork.org/member/dalai-felinto www.dalaifelinto.com 2012/12/23 Chad Fraleigh ch...@triularity.org And to be thorough, the VS2012 scripted builds I could manage at this time: http://www.triularity.org/download/blender/install-vs11.0-x32.zip (141M) http://www.triularity.org/download/blender/install-vs11.0-x64.zip (154M) install-vs11.0-x32: boost freetype jack jpeg lcms llvm openal png python samplerate sdl sndfile tiff zlib zlibwapi install-vs11.0-x64: boost jack llvm openal png sndfile tiff zlib zlibwapi -Chad ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- Thomas Dinges Blender Developer, Artist and Musician www.dingto.org ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Google Summer of Code 2013
Hi, We usually can manage topics via open movie funding quite well too. And since there's nothing tangible really for a next movie project, I rather check on what existing (bigger) blender projects would need now. I also don't think they'd come with real surprises though... we have a lot of known issues. It's not so much that we need ideas, what we need is stakeholders - people who need development for a real world use case. -Ton- Ton Roosendaal Blender Foundation t...@blender.orgwww.blender.org Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands On 19 Mar, 2013, at 16:25, Tom M wrote: On Tue, Mar 19, 2013 at 6:15 AM, Ton Roosendaal t...@blender.org wrote: For GSoC 2013 I would like to introduce a special focus: we could organize a stronger connection between the stakholders (users) and students/mentors. Speficially I'd like to invite teams/studios to think of useful targets, to define projects they really need (and will use), and to get involved as artist-buddies for the students. Ton, it would be good if you, brecht, Campbell and Sergey (and others) can brainstorm for what things would be useful for the next film. Ie what parts of the film (rendering, compositing, animating, modeling, texturing, cloth, physics and other simulations etc.) will be most labor and time intensive and then create a wishlist based on that. I'm sure there are probably useful papers from siggraph and other conferences that might be worth suggesting based on that. LetterRip ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Freestyle: edge/face marks not working since r55228
A comment in readfile.c says: /* The code segment below will be removed when the trunk merger is done. For now it is kept for backward compatibility, giving branch users time to migrate to the new CustomData-based edge/face marks. */ I worry the branch users might not be able to convert their existing data if the migration code doesn't work until the branch merge. IRIE Shinsuke Tamito KAJIYAMA wrote: Yes, the revision 55228 is intended to address review comments and still work in progress. Among mesh modifiers, only the subdivision surface modifier works. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] A way to apply transformation to all key frames?
Hello, I would like to move an animated object. There does not appear to be a way to do so without applying the transformation to every relevant key. Is there a script or a way to apply a transformation to all relevant keys? Presumably, a workflow would look something like: Select relevant keys in the graph editor and change their transformation matrix by the specified amounts. Another workflow could be: Select all relevant objects. Hit a key to enter into key transformation mode. Make a transformation. The transformation is applied to all the keys for that object. Save this transformation. Then you can select other objects that not visible in the frame on which you performed the transformation and apply the stored transformation to the objects. This workflow would be a further convenience. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] A way to apply transformation to all key frames?
Hello, I would like to move an animated object. There does not appear to be a way to do so without applying the transformation to every relevant key. Is there a script or a way to apply a transformation to all relevant keys? Is parenting your object to an armature and do the transformation that way not an option for you? best Rasmus ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
