- User Since
- Oct 25 2018, 10:38 PM (42 w, 6 d)
Feb 19 2019
That’s a pity. I knew cycles didn’t support them but assumed that eevee did since the option was still present. If it’s not supported at all the option should under be removed from the UI.
Feb 7 2019
Feb 6 2019
Here's what the console shows me on Mac on build 766741b0aa8c
( 0.0001 sec | 0.0001 sec) Importing OBJ '/Users/admin/Downloads/OBJ_EXAMPLE/BODY_OBJ_EXAMPLE.obj'... ( 0.0017 sec | 0.0006 sec) Parsing OBJ file... ( 2.2181 sec | 2.2155 sec) Done, loading materials and images... WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. WARNING, currently unsupported 'tf' filter color option, skipped. ( 2.2389 sec | 2.2363 sec) Done, building geometries (verts:84104 faces:84102 materials: 7 smoothgroups:1) ... ( 3.5119 sec | 3.5093 sec) Done. ( 3.5131 sec | 3.5120 sec) Finished importing: '/Users/admin/Downloads/OBJ_EXAMPLE/BODY_OBJ_EXAMPLE.obj' Progress: 100.00%
Could you provide a sample file which exhibits this behavior?
Feb 4 2019
As of macOS 10.14 build 38984b10ff7b it seems to open just fine, so it appears to be resolved.
Feb 3 2019
Yup, error fixed now. Thanks!
On macOS 10.14 this results in the following build error:
Jan 22 2019
The sample file does not include the textures. Could you pack all the textures into the file and re-upload?
Jan 8 2019
Nope, no success on my laptop. It's probably an issue with macOS when waking up and changing image resolution to match the external monitor. After waking if you resize it does the UI go back to the correct size?
It didn't happen for me on 3d2ff33c2615. Does it have to be plugged into an external display?
Jan 7 2019
Could not replicate on 2edd32c168d3 on windows 10.
Dec 29 2018
Confirmed on 7c438e5366b2. The BMesh API seems to have changed, and this script needs updating. I'm not sure line 11 bm.faces.layers.tex.verify() is even necessary.
Dec 24 2018
Duplicate of T59799
Dec 23 2018
Confirmed on e5e885d0ecb9.
This also happens on Mac on e5e885d0ecb9.
A sample file would be invaluable, even if it’s just the Suzanne head in those screenshots. Does increasing the samples affect it?
Dec 22 2018
Confirmed on c9df453ce70b.
This is still an issue on c9df453ce70b. It stops at powers of 10 multiplied bu 1, 2, and 5:
2.79 does not support files saved by 2.80, and issues are to be expected.
Dec 20 2018
Glad it's working!
Other things worth noting:
Could you provide a description of the problem? It rendered fine on my machine on b49699b1ec6d.
Confirmed on b49699b1ec6d. Here's my traceback:
Could not reproduce on b49699b1ec6d. Does it happen in the default scene?
That's a very old build. Could you try it again with the latest from the website? https://builder.blender.org/download/
Dec 18 2018
Here's another file that does it:
Nevermind, I think the issue I am having is unrelated.
This issue still exists in 42b9df5907d041a5a68585308b1e11b2eac2c947 on master.
Dec 16 2018
Confirmed, though I doubt they will want to spend time fixing anything since Blender Internal has been removed from 2.80. For comparison, here are the results I got from 2.79b release:
Dec 15 2018
Can confirm on 4e3562f45ad on 10.14, but it seems to depend on the particular file. This is a relatively recent problem I think, because I did not run into this issue on master 2 or 3 weeks ago.
Dec 14 2018
Tested this on de662e7cd3b and it does seem to resolve T59351.
I noticed this as well. The threshold of the clipping start where the artifacts begin to be noticeable varies depending on the zoom level as well.
Got a debug build working, and this is the stacktrace I get when it crashes:
I updated the drivers just to be sure, and it still happens. Must be a Windows thing?
I attempted to reproduce this on Mac on hash f4c70a35a292, but it did not crash and the animation render was successful. System info:
Confirmed on be0c8ed734b on windows. It's intermittent for me too: sometimes it will crash immediately, sometimes I have to revert the file a couple of times, always with an EXCEPTION_ACCESS_VIOLATION error.
FYI, 2.79 is not compatible with files saved by 2.80, and eevee is a 2.80-only feature.
Dec 11 2018
Does the wiki log whenever someone tries to visit a missing page? That would be a good way to identify broken links.
Dec 9 2018
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.
Dec 8 2018
Dec 6 2018
Dec 5 2018
Dec 3 2018
Dec 2 2018
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.
Dec 1 2018
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:
Nov 30 2018
@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:
Nov 29 2018
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
Nov 28 2018
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