[Bf-committers] Platform maintainers: Collada library update needed
Hi. As recommended by Sergey i kindly request for help from platform maintainers for updating the Collada libraries: OpenCOLLADA had a bug that was discovered in this blender report: https://projects.blender.org/tracker/?func=detailatid=498aid=36325group_id=9 The bug has been fixed by now. So please update to the new OpenCOLLADA commit number: 828b60384552b83e55d2af7055f07d2c40b4d3f4 See also: https://github.com/KhronosGroup/OpenCOLLADA/commits/master For linux i believe there is a build script that only needs to refer to the new commit ? For Windows and MAC the Collada libraries need to be updated in svn: * Windows-32 vs-2008 (debug and release) * Windows-32 Mingw (debug and release) * Windows-64 vs-2008 (debug and release) * Windows-64 Mingw (debug and release) * Mac-OSX Thanks a lot. -gaia- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] Please report Issues with building OpenCollada for Blender
Hi; Sergey has mentioned that building the OpenCOLLADA libraries on linux is troublesome and always needs manual tweeking. However i believe if there are such issues, then the openCollada maintainers would be more than happy to get informed about these problems and how they have been fixed by the Blender developers. So please if you find that you have to fix the build of the collada libraries, then also report to the OpenCollada bug tracker at https://github.com/KhronosGroup/OpenCOLLADA/issues?state=open They actually take some care about what Blender developers say. thanks -gaia- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Trusted blend files and scripted drivers bug and annoyance
I have already asked for an alternative to the #frame driver for rendering animation in Cycles. It is realy not a good aproach anymore due to new security policies. Seed should always vary per frame. Static seed is an exception, it is only usefull in very rare situations when you need to compare renders. #frame is not obvious for most users, and with new policies it leeds to mistakes, like Daniel points out. Adriano A. Oliveira 2013/8/9 Daniel Salazar - 3Developer.com zan...@gmail.com I'm also having problems with students in the simple case of a #frame driver in cycles seed. I can never be sure they all have the enable python setting on in all the computers they use even if I tell them to enable it, this stuff is just never guaranteed in the real world because people forget this stuff. Of course renders turn out useless because of fixed noise. Daniel Salazar patazstudio.com On Fri, Aug 9, 2013 at 2:30 PM, Jace Priester jacepries...@threespaceimaging.com wrote: I expressed a lot of disagreement with the Trusted feature when there was talk about implementing it, and I'm here to voice a complaint again now that it has become a problem. I have created an animation using a scripted expression driver and that driver's value evaluates to zero. I did not notice the Continue Untrusted button appear at the top right. I've spent hours trying to figure out why scripted drivers don't work, only to save and reload and then be prompted to Reload Trusted. This has been a gigantic waste of my time and is precisely the reason I did not want this trusted junk in the first place. I am aware of the command line options to disable it, but I never expected to have to do that. I understand the Reload Trusted prompt when opening a file. However, when I create a brand new driver and enter the expression myself it should work immediately. In any case, it damn sure should not show a value of zero without a notice right next to it that it skipped evaluation entirely. As-is, this is very misleading and indicates that the expression did in fact resolve to a value of zero. -- -- Jace Priester Threespace Imaging jacepries...@threespaceimaging.com 559-284-0904 -- ___ 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] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [58752] trunk/blender/source/blender/ editors/object/object_bake.c: Fix #36302: Multires baking to zero 0 was showing error but st
Not sure if we're supposed to respond to these, but I've been meaning to
ask: Why can't we bake to level 0?
On Tue, Jul 30, 2013 at 11:35 PM, Sergey Sharybin sergey@gmail.comwrote:
Revision: 58752
http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=58752
Author: nazgul
Date: 2013-07-31 03:35:45 + (Wed, 31 Jul 2013)
Log Message:
---
Fix #36302: Multires baking to zero 0 was showing error but still was
baking
We do not support baking to level 0, disabled this completely now.
Modified Paths:
--
trunk/blender/source/blender/editors/object/object_bake.c
Modified: trunk/blender/source/blender/editors/object/object_bake.c
===
--- trunk/blender/source/blender/editors/object/object_bake.c 2013-07-31
02:32:00 UTC (rev 58751)
+++ trunk/blender/source/blender/editors/object/object_bake.c 2013-07-31
03:35:45 UTC (rev 58752)
@@ -153,7 +153,7 @@
if (mmd-lvl == 0) {
BKE_report(op-reports, RPT_ERROR, Multires data
baking is not supported for preview subdivision level 0);
-
+ ok = 0;
break;
}
___
Bf-blender-cvs mailing list
bf-blender-...@blender.org
http://lists.blender.org/mailman/listinfo/bf-blender-cvs
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [58752] trunk/blender/source/blender/ editors/object/object_bake.c: Fix #36302: Multires baking to zero 0 was showing error but st
Hi, The answer it that during sculpting, the sculpt stroke does not propagate on the data on the zero level. This means that the mapping between displaced and base mesh breaks on this level and the algorithm that does the multires baking breaks there. My guess is that this is an architectural issue similar to modifiers are non-destructive? However, IMO, we should if possible make an exception to the multires modifier. Being able to bake to level zero is very important. There are two solutions I see here. Either make the strokes touch mesh data directly, or use an apply base modifier prior to baking, maybe with a warning that baking will alter the mesh data. Of course this requires an Apply to Base operator that actually works which currently is not the case. We had a few reports in our tracker where it resulted in spikes on the mesh (apparently some divide by small number errors). ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [58752] trunk/blender/source/blender/ editors/object/object_bake.c: Fix #36302: Multires baking to zero 0 was showing error but st
Either make the strokes touch mesh data directly, or use an apply base modifier prior to baking, maybe with a warning that baking will alter the mesh data. Make that an Apply Base operator instead of modifier, sorry for the confusion ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Trusted blend files and scripted drivers bug and annoyance
Hi, - If renders are useless it should do this by default? - the #frame tag shouldn't be using python, and work always. I'm quite sure more expression shortcuts can kept working... -Ton- Ton Roosendaal - t...@blender.org - www.blender.org Chairman Blender Foundation - Producer Blender Institute Entrepotdok 57A - 1018AD Amsterdam - The Netherlands On 9 Aug, 2013, at 23:36, Daniel Salazar - 3Developer.com wrote: I'm also having problems with students in the simple case of a #frame driver in cycles seed. I can never be sure they all have the enable python setting on in all the computers they use even if I tell them to enable it, this stuff is just never guaranteed in the real world because people forget this stuff. Of course renders turn out useless because of fixed noise. Daniel Salazar patazstudio.com On Fri, Aug 9, 2013 at 2:30 PM, Jace Priester jacepries...@threespaceimaging.com wrote: I expressed a lot of disagreement with the Trusted feature when there was talk about implementing it, and I'm here to voice a complaint again now that it has become a problem. I have created an animation using a scripted expression driver and that driver's value evaluates to zero. I did not notice the Continue Untrusted button appear at the top right. I've spent hours trying to figure out why scripted drivers don't work, only to save and reload and then be prompted to Reload Trusted. This has been a gigantic waste of my time and is precisely the reason I did not want this trusted junk in the first place. I am aware of the command line options to disable it, but I never expected to have to do that. I understand the Reload Trusted prompt when opening a file. However, when I create a brand new driver and enter the expression myself it should work immediately. In any case, it damn sure should not show a value of zero without a notice right next to it that it skipped evaluation entirely. As-is, this is very misleading and indicates that the expression did in fact resolve to a value of zero. -- -- Jace Priester Threespace Imaging jacepries...@threespaceimaging.com 559-284-0904 -- ___ 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] Trusted blend files and scripted drivers bug and annoyance
Hi, I understand the pain... apparently this header notice is not communicating, even when people already expressed disagreement and knew the feature was coming. However, you can set this all in user preferences to have things work forever as you want. It'swell documented in release logs: http://wiki.blender.org/index.php/Doc:2.6/Manual/Extensions/Python/Security One idea we missed to investigate was to make the default (for previous saved startups) to mimic the old behaviour, so existing users wouldn't notice the change. The new trusted source feature then would only get activated on new installs or new userprefs after upgrading Blender. -Ton- Ton Roosendaal - t...@blender.org - www.blender.org Chairman Blender Foundation - Producer Blender Institute Entrepotdok 57A - 1018AD Amsterdam - The Netherlands On 9 Aug, 2013, at 22:30, Jace Priester wrote: I expressed a lot of disagreement with the Trusted feature when there was talk about implementing it, and I'm here to voice a complaint again now that it has become a problem. I have created an animation using a scripted expression driver and that driver's value evaluates to zero. I did not notice the Continue Untrusted button appear at the top right. I've spent hours trying to figure out why scripted drivers don't work, only to save and reload and then be prompted to Reload Trusted. This has been a gigantic waste of my time and is precisely the reason I did not want this trusted junk in the first place. I am aware of the command line options to disable it, but I never expected to have to do that. I understand the Reload Trusted prompt when opening a file. However, when I create a brand new driver and enter the expression myself it should work immediately. In any case, it damn sure should not show a value of zero without a notice right next to it that it skipped evaluation entirely. As-is, this is very misleading and indicates that the expression did in fact resolve to a value of zero. -- -- Jace Priester Threespace Imaging jacepries...@threespaceimaging.com 559-284-0904 -- ___ 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] Trusted blend files and scripted drivers bug and annoyance
On Sun, Aug 11, 2013 at 3:35 AM, Ton Roosendaal t...@blender.org wrote: Hi, I understand the pain... apparently this header notice is not communicating, even when people already expressed disagreement and knew the feature was coming. However, you can set this all in user preferences to have things work forever as you want. It'swell documented in release logs: http://wiki.blender.org/index.php/Doc:2.6/Manual/Extensions/Python/Security One idea we missed to investigate was to make the default (for previous saved startups) to mimic the old behaviour, so existing users wouldn't notice the change. The new trusted source feature then would only get activated on new installs or new userprefs after upgrading Blender. We didn't miss this, thats how it works currently and I suspect why we didn't get much feedback initially when the change was made. But as users do new installs without using their old userprefs, or reset factory-defaults, they run into this problem. -Ton- Ton Roosendaal - t...@blender.org - www.blender.org Chairman Blender Foundation - Producer Blender Institute Entrepotdok 57A - 1018AD Amsterdam - The Netherlands On 9 Aug, 2013, at 22:30, Jace Priester wrote: I expressed a lot of disagreement with the Trusted feature when there was talk about implementing it, and I'm here to voice a complaint again now that it has become a problem. I have created an animation using a scripted expression driver and that driver's value evaluates to zero. I did not notice the Continue Untrusted button appear at the top right. I've spent hours trying to figure out why scripted drivers don't work, only to save and reload and then be prompted to Reload Trusted. This has been a gigantic waste of my time and is precisely the reason I did not want this trusted junk in the first place. I am aware of the command line options to disable it, but I never expected to have to do that. I understand the Reload Trusted prompt when opening a file. However, when I create a brand new driver and enter the expression myself it should work immediately. In any case, it damn sure should not show a value of zero without a notice right next to it that it skipped evaluation entirely. As-is, this is very misleading and indicates that the expression did in fact resolve to a value of zero. -- -- Jace Priester Threespace Imaging jacepries...@threespaceimaging.com 559-284-0904 -- ___ 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 -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [58752] trunk/blender/source/blender/ editors/object/object_bake.c: Fix #36302: Multires baking to zero 0 was showing error but st
I just wanted to say I think that sounds like a great idea. Cheers, Morten. On Sat, Aug 10, 2013 at 10:26 AM, Antony Riakiotakis kal...@gmail.comwrote: Either make the strokes touch mesh data directly, or use an apply base modifier prior to baking, maybe with a warning that baking will alter the mesh data. Make that an Apply Base operator instead of modifier, sorry for the confusion ___ 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
