Jun 9 2019
Jun 8 2019
Jun 7 2019
That is right, however this could break stuff again. Not sure if it is worth it.
It feels like a dependency cycle or so in the file. Just going back and forth in time, changes where the object is in the same frame.
I removed the settings from the UI (they still exist internally), because they are not doing anything in Blender 2.80 currently. Nobody says that they are not useful. We just don't have the manpower to make them work for the Blender 2.80 release. It does not make sense to keep them in the UI if they do nothing.
Jun 6 2019
Particle trails are not supported currently. The settings for it are not in the ui anymore: rB87fde57b63887aa3082917eebcff5f3f069d610a
Seems to be related to sound.
Collections do not have to be in a scene to exist. I agree that the current behavior is a bit confusing from a users point of view. Not sure if there is something good we can do about it for Blender 2.80. @William Reynish (billreynish), ideas?
Turns out there are a lot of options that don't seem to do anything anymore. Almost none of the flags in eParticleDrawFlag is used. But all the options are in the UI still.
I suggest for Blender 2.80 we just remove the python part of these options instead of removing the C code.
If necessary, the C code can be cut out later, or we wait with that until we can remove the entire particle code.
Actually, I don't know what this option is supposed to do.
Did particle trails ever work in Blender 2.8? It looks like no code actually uses the trail_count variable currently.
That is quite confusing, indeed. Can't really explain why the behavior.
Just contact me in https://blender.chat.
Jun 5 2019
@Brecht Van Lommel (brecht), seems to be this old bug again: keyframed properties reset all the time.
This should already be fixed in the newest Blender builds. You're build is a couple of weeks old already.
@Clément Foucault (fclem), just replacing CustomData_get_active_layer with CustomData_get_render_layer seems to solve the issue for me. Unfortunately, I don't know the implications..
Please make sure that your gpu driver is up to date.
What exactly do you mean by the "Material Menu"? (screenshot)
Did this work before?
I'm still able to reproduce the issue.
This is what I get when I paint most of the hdr black.
Will try to simplify the example to see if we can do something about it.
The issue is probably caused by some very light pixels directly in the sun on the image (> 27000).
rBb79976a9bd94dc372bb8f215c766d4ef03d67bcb, rB8b1ca3ec537cc13d87e15dc80dc04d53ee2d95ca, rB04bac387315ce09822c36bc20e0fe4e7d533fec8, rBab5219af345721e888ce6832b281369f834843ba, rB8e125f278c52b38cf3be53b2296f0dc30885bae4
Does the problem persist, when you download the newest version of Blender 2.8?
Looks like some weird refresh issue. Thanks for the report.
We have to reproduce this somehow. Can you share the .blend file in which the error happens when you click bake?
I think the shading is actually technically correct here. The issue is, that the sphere is not actually round when you use smooth shading. Instead, only the normals are interpolated across the surface. However, the ray intersection testing does not really care about the normals, only about where the triangles actually are.
Looks like the normals change for some reason.
I can reproduce it in a new file with a subdivided suzanne.
Hm, that's what I did as well. Still cannot reproduce it.
Please make sure that your gpu driver is up to date.
I guess you are talking about this addon: https://github.com/Radivarig/UvSquares ?
I cannot reproduce the issue. Can you be more specific by what you mean with "Assign"?
@William Reynish (billreynish) is there anything to do here? I'm not sure what a better solution would be.
I cannot reproduce the bug. Waiting for someone else to check.
That does not relate to the subsurface modifier. The crash can be reproduced with other generate-modifiers as well.
Please pack the image into the .blend file.
rna_Node_refine(struct PointerRNA * ptr) (/home/jacques/blender-git/blender/source/blender/makesrna/intern/rna_nodetree.c:1185) RNA_pointer_create(ID * id, StructRNA * type, void * data, PointerRNA * r_ptr) (/home/jacques/blender-git/blender/source/blender/makesrna/intern/rna_access.c:168) ccl::BlenderSession::builtin_image_float_pixels(ccl::BlenderSession * const this, const std::__cxx11::string & builtin_name, void * builtin_data, float * pixels, const size_t pixels_size, const bool free_cache) (/home/jacques/blender-git/blender/intern/cycles/blender/blender_session.cpp:1431) ccl::ImageManager::file_load_image<(OpenImageIO_v1_8::TypeDesc::BASETYPE)11, float, ccl::float4>(ccl::ImageManager * const this, ccl::ImageManager::Image * img, ccl::ImageDataType type, int texture_limit, ccl::device_vector<ccl::float4> & tex_img) (/home/jacques/blender-git/blender/intern/cycles/render/image.cpp:631) ccl::ImageManager::device_load_image(ccl::ImageManager * const this, ccl::Device * device, ccl::Scene * scene, ccl::ImageDataType type, int slot, ccl::Progress * progress) (/home/jacques/blender-git/blender/intern/cycles/render/image.cpp:807) ccl::TaskScheduler::thread_run(int thread_id) (/home/jacques/blender-git/blender/intern/cycles/util/util_task.cpp:396) ccl::thread::run(void * arg) (/home/jacques/blender-git/blender/intern/cycles/util/util_thread.cpp:52) start_thread(void * arg) (/build/glibc-OTsEL5/glibc-2.27/nptl/pthread_create.c:463) clone() (/build/glibc-OTsEL5/glibc-2.27/sysdeps/unix/sysv/linux/x86_64/clone.S:95)
Please create a new report using the Help -> Report a Bug button in Blender. This way we get more information we might need to reproduce the bug.
The problem is probably that opening the file browser will close all popup dialogs.
Later, when the dialog tries to close itself, it does not exist anymore and it crashes.