Looking at this more closely, it appears that changing the input vector manually (via the widget) has no effect. While this behavior matches what is in the shader editor, I can't see what the use of a widget that does nothing is. It only serves to confuse users IMO. I will re-title this a WIP. I am not sure how to remove the review request.
Sat, May 23
NO ISSUE of the APPEARANCE! The image you see on both 3D view-port and Image View-port as render result are completely the same! The decision what type format you will export this image, doesn't matter!!! You can export what ever you need and it will be correct compare to what you see on the screen!
I just fixed with commit b4613e0bca9b
- Keep handles always visible for Nurbs.
Additional info: T76992: Regression: Viewport render recalculations when nothing changed in scene.
Problem exist since 2.80.
The commit message should be "mesh lights" instead. I should have reused the description in the review which is way more accurate of what this actually does.
Yep, they didn`t fix it at 2.80+: there is also unnecessary calls when you add node) and it become worse now.
2.79 have only one case for unnecessary rerender. When reroute combines parallel routes.
Since there is a working and broken version, can anyone do a git bisect and find the problematic commit ?
In T71420 it was debated whether Blender would get it's own site-packages directory for the ones installed with the --user flag by setting PYTHONUSERBASE . Not sure if there's been a decision for these changes yet.
I'm ready to close this but can somebody offer a suggestion what addons relying on non-supplied modules should do?
I can just append the path to the sys.path of course. @Brecht Van Lommel (brecht)?
So, issue T62422 had gotten merged with this one, but then it got unmerged again. It seems very closely related to me. @Sebastian Parborg (zeddb) committed a fix, and @Vyacheslav (hitrpr) says it works now: rB27cac4a102b9
Apparently, its intentional? https://developer.blender.org/rBS79a58eef059ffc3f12d11bd68938cfb1b4cd2462
Hello Troy, I'm not here to spend time to arguing with you, but to report the facts! IF you really want to help please do so, otherwise I don't know what to say...
Same as T76273.
@Philipp Oeser (lichtwerk) Agree that It should be temporary hidden, until it will be implemented.
As far as it works fine for pixels, it can work as well for v-colors.
Initially when i posted my bug report i was on 220.127.116.1158
Updated to the latest .5126 made no difference the artifacts are still there.
After that gone down to:
And now I'm on .5107 supplied by lenovo(21.04.2020) - there is no difference between driver versions.
The issue is related to Anti-Aliasing. Change it to single-pass or none. This is a temporary fix.
@Rodger Davis (RodDavis) , does this work for you?
Forget to say, it seems to behavior a little normal on 2.83 beta. it does not crash, but weird preview might occur. (Hope the information is enough)
@Sebastian Parborg (zeddb) Thanks again. Just tested it. All works fine.
Hello Bastien, Campbell,
Seems the draco library is not included when building bpy as a python module.
Because this is a building issue, not sure if I need to open a new issue or not.
Reinserted the menu options.
J,K,L + alt is select inside handles.
J,K,L + alt is select neighbor handles.
IMHO this is a (technical) design task first, current code is really not ready for random items height, would need design and deep refactor for that.
Your description is rather unclear so this may not be the proper fix:
To render animations you must select the "render animation" button which can be found at the top of Blender under Render>Render Animation or by pressing the keyboard shortcut Ctrl+F12.
That's a real bad , because it's a very easy way to create terrain. If the anchored point doesn't create a detail size dyntopo under the brush I don't see what it's good for.
This report does not contain all the requested information, which is required for us to investigate the issue.
I just downloaded this 2.83Beta, but alas, no luck launching. It When I start it from the command prompt a new window frame appears briefly but will close before it is properly initialised. This is displayed in teh command prompt window:
Are you able to provide a copy of your scene?
@Aaron Carlisle (Blendify) Yet another patch. I'm sorry it took a while. I was going to get this patch committed last weekend but never got around to starting it. With bcon 3 ending in a few days (assuming no further set backs), this will most likely be my last commit for this task until the Blender 2.90 manual is available.