- User Since
- Oct 25 2018, 10:38 PM (6 w, 6 d)
Tue, Dec 11
Does the wiki log whenever someone tries to visit a missing page? That would be a good way to identify broken links.
Sun, Dec 9
Confirmed on macOS 10.14 hash 168a6a4bfc1. It looks as though the viewport text is only being updated when manipulating the value and curves, but not when changing the frame.
Confirmed on 168a6a4bfc1 on windows. Running the script AND setting the renderer from the command line does not update which engine is used in the renderer shading mode in the 3d viewport, despite the mode being set:
>>> bpy.context.scene.render.engine 'custom_renderer'
This works just fine on MacOS Mojave 10.14 hash 168a6a4bfc1. Try using a newer build and see if it still happens.
It seems contradictory when something called is_xxx_dirty being True actually means "not updated".
Could not reproduce on windows 10 x64 879877295d0. Try downloading the latest nightly and see if the problem is resolved.
A patch was made for several similar bug reports yesterday. Download the latest nightly and try again, it should be fixed.
Looks like you are launching whichever version is installed in C:\Program Files\Blender Foundation\Blender. Try downloading the latest build and unzip it somewhere rather than installing it, and open the exe file in that folder.
I couldn't reproduce this on 879877295d0. There were several similar bug reports earlier that were patched already, so see if the newest nightly build fixes the issue.
I couldn't reproduce this on 879877295d0. Try downloading the latest nightly build and see if you encounter it again.
Confirmed on windows 879877295d0. It happened the first couple of times I opened the file, but then it stopped happening until I ran blender with --debug. It seems to consistently happen with --debug enabled.. When it does crash, it crashes when undoing a group node move operation.
Could not reproduce on windows 879877295d0.
This add-on needs to be updated. bpy.context.scene.master_collection was renamed to bpy.context.scene.collection.
The problem is the message does not correctly show all the valid enum values. For example, 'CONSOLE' is truncated.
I could not reproduce on e79bb957fc3. Have you tried downloading a newer version of 2.80? New builds are released daily.
I couldn't reproduce this on e79bb957fc3 on Windows. Try a newer version, that one is two days old.
Sat, Dec 8
Thu, Dec 6
Wed, Dec 5
Mon, Dec 3
Sun, Dec 2
Confirmed, got the following when running from CMD:
Read prefs: C:\Users\moogl_000\AppData\Roaming\Blender Foundation\Blender\2.80\config\userpref.blend AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead found bundled python: C:\Users\moogl_000\Desktop\blender-2.80.0-git.925380050d0-windows64\2.80\python Read blend: C:\Users\moogl_000\Downloads\crashes_on_load.blend Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF7E152F7B9 Module : C:\Users\moogl_000\Desktop\blender-2.80.0-git.925380050d0-windows64\blender.exe
@Campbell Barton (campbellbarton) Fair enough. I can see how changing it to work with sys.path could be more effort than it’s worth. It’s good to know what the issue is, this was bugging me for weeks! If I find a solution I’ll pass it along.
Sat, Dec 1
Why is it looking there instead of searching the sys.path of the python interpreter?
This is not OSX-specific, I have the same issue on Windows too, most recently with build 84285c1e3440. Here is the system trace from Procmon on windows:
Fri, Nov 30
@Campbell Barton (campbellbarton) Using make install does not fix the issue. I just did a fresh build and the results were the same:
git pull make update make cd ../build_darwin make install
I created a virtual environment using these instructions from @sybren, sim linking both blender/release and boy.so inside of the site-packages directory of the virtual environment:
Thu, Nov 29
My apologies. I've created a thread on devtalk for further discussion.
Certain keybindings are set based on the build target (operating system). Different operating systems have different conventions.
Are there any plans for helping a user migrate old materials when opened in 2.80?
On latest builds I can only reproduce under the conditions described in T58075.
Confirmed on build a740cc53ea1 on macOS. Running from console produces the following error:
Confirmed on MacOS 10.14 build a740cc53ea1
Wed, Nov 28
Upon further examination, this appears to be an issue of not migrating blender internal materials to cycles. In 2.79 when using cycles the textures do not appear either. However, the texture data still does not show up as orphaned, as it does in 2.80.
Have you tried running bm.update_edit_mesh() before switching back to the view?
Possible duplicate of T58075
Actually this is related to T57653, and happens under the same circumstances: when the selected object has only a base shape key, OR when it has a shape key with a nonzero value. If either of those are true, directly changing from edit mode to vertex paint mode will trigger a crash.
Related to this is T58075, which crashes under the same conditions (only one shape key, or one or more nonzero shape keys) when switching from edit mode to vertex paint mode.
Confirmed working on the new 11-28 builds on both mac and windows.
I was able to confirm this on windows 10 x64 2018-11-28 hash 4c6e7ef11f3
This appears to happen for .obj files which contain no material data. Starting with the sample capsule from this web pade, I noticed that it would import even if I removed the .mtl and jpeg files. Only after removing the lines with usemtl and mtllib could I replicate the issue.
Possibly related to T57653
Confirmed on Mac build b205cb369a8 (From build bot), but it does work fine on my fresh build, hash 9d535f7ce8d. Issue may have already been resolved.
Tue, Nov 27
Duplicate of T58066. Patch will be in the next build.
Duplicate of T58066, and was patched earlier today. It should be fixed in tomorrow’s build.
Duplicate of T85066. The patch should be in tomorrow’s daily build.
Just did a fresh build, and the issue does seem to be fixed now.
Also confirmed on the latest build for Mac. UV Editing -> Sculpting also crashes.
Mon, Nov 26
Fri, Nov 16
Nov 12 2018
One request regarding the new wiki I would like to see: explicit version numbers. The new wiki does not specify which version of Blender the articles are relevant to. Something I appreciate that the Python documentation does and the old wiki does is have a selectable version dropdown menu which allows you to make sure the version of the page you are reading is correct for the version you are working with, and select a different version and be immediately taken to the correct page. I've been hitting a lot of dead links lately trying to figure out which set of build instructions is correct for 2.7, which has been a bit difficult since the old wiki does not have anything labeled 2.7, but the instructions in the new wiki are specific to the latest builds of 2.8.