- User Since
- Apr 28 2013, 12:18 AM (204 w, 2 d)
Sat, Mar 11
Sun, Mar 5
Feb 17 2017
Maybe we can do it in 2.8 branch, but only if it's indeed something important to solve.
Feb 12 2017
Dec 4 2016
Interestingly, it appears the standalone player works fine.
Sep 21 2016
@Sergey Sharybin (sergey) I see, thanks.
Sep 13 2016
Sep 6 2016
Unless we get search to work massively better, I'm in favor of having the content tree on the landing page (python style).
Perhaps language and version drop-downs could be perpetually in the top corner somewhere,
and in addition, perhaps we may want to make them more prominent on the landing page (wikipedia style).
+1 for releasing a separate version of the manual for each blender release.
Sep 5 2016
Sep 1 2016
Resolved by rBM2523
Aug 30 2016
Aug 17 2016
Aug 16 2016
Aug 14 2016
For some reason it's not compiling against latest master for me on linux:
Aug 9 2016
Aug 1 2016
Jul 31 2016
Jul 5 2016
Jun 30 2016
Jun 21 2016
Jun 4 2016
What I find strange is that the cursor warp used while rotating the view seems unbreakable.
Even if the cursor is moving fast enough to be briefly drawn far outside the window, blender warps it back no problem.
Only translations seem to allow the cursor to escape in this manner.
Jun 2 2016
Jun 1 2016
May 20 2016
May 12 2016
Would it really be that bad if the patch was committed in its initial form?
Apr 17 2016
Apr 16 2016
Seems none of the node wrangler shortcuts are updating the viewport render in 2.77, even Ctrl Shift LMB (emission preview) fails to update.
Works with official blender downloaded from blender.org, so seems to be a packaging issue?
Apr 14 2016
Mar 26 2016
Feb 22 2016
Feb 18 2016
Feb 16 2016
Jan 26 2016
Jan 25 2016
Jan 19 2016
Jan 10 2016
Jan 6 2016
Dec 30 2015
Yes I believe there is.
I was confused about the exact circumstances which are required to produce it, and unfortunately I can't edit the task description. For clarity, I'll restate it the way I currently understand it:
Dec 22 2015
Scratch that. It's actually just objects with 'triangle mesh' collision bounds that are causing the reversed normal
Nov 20 2015
Nov 9 2015
Nov 5 2015
Nov 3 2015
It's supposed to auto-close this revision when committed, but for some reason it sometimes doesn't work..
Nov 2 2015
@Dennis Brown (DBrown) Thanks for the heads up, I already commited a fix for that :P
I also changed the hyphens to underscores to be consistent with the style guide (http://blender.org/manual/about/markup_style_guide.html#files)
Oct 25 2015
Oct 20 2015
For consistency, and since it would be good to ensure nodes screenshots are all a similar size when floated next to text (see T46082), I suggest taking such floated node screenshots in the following manner:
Oct 19 2015
It *looks* fine from what I can see in the diff, but I can't check for compile issues etc. without applying the diff.
Not too sure what's to be done in such situations.. If you can commit it okay then perhaps that will do
Oct 17 2015
It's still only partially applying to volume.rst
Are you creating the diff against an up-to-date working copy?
Include "Differential revision: https://developer.blender.org/D1560" somewhere in the commit message (where url points to the revision you want to close)
Someone with commit access must download and apply the diff locally, then commit (and credit all the proper authors etc.)
Looks good to me!
Oh, I missed the image the in the description. Oops :P
Images aren't included with the diff, could you upload the image here (drag and drop into a comment?)
Hm.. Maybe instead of attempting to describe each force-field's behavior it would be clearer to have an image showing the behavior visually. As a side benefit, these images could also show the appearance of the empty for each force type.
E.g. something like this:
This looks pretty good to me, but couldn't get the diff to apply properly here.. Are you able to apply it on your end?
Oct 13 2015
Thanks for your patch :)
I don't see any particular reason to go with a more tutorial like style here when we (try to) avoid this everywhere else..?
Perhaps a short "workflow" section (e.g. like this) couldn't hurt, but I think it would be good to document each setting as well.