- User Since
- Jul 23 2010, 10:58 PM (574 w, 4 d)
Mar 8 2021
the delayed update has been reported here [it is a known limitation due to performance reasons
I would like to use GP for live illustration purposes (since the annotation tool is too simple and doesn’t allow custom strokes etc), so having the GP only show on mouse release will not work for me. Maybe such optimization can be turned off if i don’t care about performance issues?
Feb 27 2021
And for what it’s worth.. here’s another example illustrating the occlusion for different camera orientations.. for each orientation the occlusion seems to be different, which indicates it may be related to not just the camera but also its orientation relative to the world.
And another example with the background image opacity set to 1.0.. where the occluded part of the stroke has a different blending and it is more pronounced.
More findings.. actually this behavior may not even be related to having meshes in the scene at all. If I add a picture (e.g. a chalkboard pattern) to the camera to be displayed (thorough the camera) as a background image, the same occlusion effect occurs.
Feb 26 2021
Jan 20 2021
@Falk David (filedescriptor) Not exactly what i’m looking for. I want to render the scene for the active camera at the resolution set for the final render, e.g. 32x32 pixels. The viewport renders at th e viewport/display resolution, not the render setting resolution. Why would I need 32x32 resolution you may ask? because I am working on a technique to voxelize a surface via rendering and I need to see the final render at the specified resolution. Besides, why does this event handler crash blender is the question. How can this be normal behavior?
Jan 19 2021
Aug 17 2020
Also.. one minor esthetic thing.. can the dmg installer get a little TLC to make it look a little bit more polished? :) Here's a comparison between Blender's and firefox/minecraft dmg installers.
@Campbell Barton (campbellbarton) this isn't fixed. I have the same issue. I installed 2.8.4 by simply drag and drop from the opened dmg file into the /Application folder.. I can open it fine in my user, but my son is not able to open it in his user.
Apr 17 2020
If this doesn’t get fixed I would suggest you to use sverchok nodes (add-on for parametric, node-based, mesh generation) which has a torus node (among many others) with no such limitations.. plus it has many other features that the native blender add-on torus functionality lacks.
@Campbell Barton (campbellbarton) A vertex is different than a node.. there is no reason to zoom into a vertex, but there are 1000 reasons to zoom into a node: e..g. I need to see or change node values so I need to see the text and values and be able to manipulate the values. Your analogy with the viewport behavior is a bit weak.
Apr 3 2020
Can you even GET a linewidth > 1 on a mac system?? AFAK blender 2.8x fails to accomplish that unfortunately for the mac users. Any working solution out there of how to render thick lines on a mac? perhaps some GLSL gurus in BF can figure this out (geometry shaders, fragment shaders..whatever it takes)
Apr 1 2020
Is there a plan to solve this problem for mac users?
Anybody has any suggestions of how the thicker than 1px line widths are possible on mac? (shaders?)
Mar 24 2020
Yeah. I have the same problem. This has been an issue since the very beginning of 2.8.. Now we have 2.83 (alpha) and this issue is STILL an issue on mac systems. Annotations are completely useless for me with 1px thickness.
Dec 15 2019
FYI, this still doesn’t work in 2.82 alpha experimental builds (on macOS). Perhaps because the experimental builds are not yet beta?
Nov 28 2019
How come this is marked as a LOW priority? The annotations are useless without proper thickness. I’m running Blender 2.81 on Mojave 10.14.6 on a MacBook pro 15” 2018 and the annotations are 1px thick regardless of the line thickness settings.
Oct 11 2019
This still doesn’t seem to work on a mac (MacBook Pro + Mojave).
Oct 7 2019
I checked the experimental version as well (blender-2.81-54a9649e2636-macOS) and it seems to still have this issue, so either a fix for this was not yet integrated into 2.81.. or if it was integrated, the fix was not really fixing this issue. :)
I have the same problem with Blender 2.80 on a mac (MacBook Pro / OSX 10.14.6). also the highlight of selected nodes (in composer, material nodes etc) is too thin and hard to distinguish what the selected nodes are. As a matter of fact many lines displayed throughout the Blender 2.80’s UI are too thin, compared to 2.79
Apr 22 2017
Oct 24 2016
That is unfortunate, since this would help tremendously with testing out animation in the viewport in realtime. Besides, why does the image update properly in the viewport when scrubbing the timeline (assuming the image node is selected in the node editor) but it does not work when turning on animation (ALT+A) ?
Oct 14 2016
Dec 7 2015
Great. Thanks for the flowers.. and the commit access :) I made the requested changes (e.g. import specific properties instead of import *) and here’s the updated version (plus other minor cleanup edits) of the add-on and the presets.
Nov 28 2015
Here is also a screen capture collage illustrating the UI props remapping between the old and the new implementation. The colors indicate where each property was relocated. The white marks indicate the newly added properties.
Oct 29 2015
Sergey, but what about the drivers not working while they are in a group node ? (rendered mode in particular, which i assume is not GLSL based).
Oct 26 2015
And btw, if you place the driven nodes inside of a group node then the drivers do not work in "Rendered" mode either (viewport does not get updated). The values seem to update properly in the driven node (when moving the cube) but the viewport does not reflect the changes (e.g. texture scale stays the same). Tapping the mapping node's tab buttons can enforce the viewport to update though. And what's more, when using the new depsgraph (--enable-new-depsgraph) putting the driven nodes inside of a group node the driven values don't seem to update at all in the node. (e.g. try to group the first three nodes: tex coord, mapping and image texture into a group node to test this). Also in this case the driven values in the node do not update when taping the mapping node's tab buttons either (e.g. you cannot enforce an update this way with the new depsgraph enabled).
Oct 22 2015
Aug 31 2015
Sindra, try to push the action onto the NLA stack (creating a new action-strip).. then try to animate the Strip Time of that strip, effectively remapping its time. See if you succeed to get the ocean animation to go from normal speed to slow-mo speed as you playback. It seems that aligorith thinks it's probably a Dependency Graph issue.
Aug 29 2015
Aug 28 2015
Aug 15 2015
Aug 13 2015
Jul 22 2015
Nov 24 2014
Nov 17 2014
Oct 6 2014
Btw.. to complete my system information: