- User Since
- Jan 3 2003, 6:23 PM (846 w, 1 d)
Dynamic topology is intentionally disabled for these options in the code. It might be good to improve the code to support cases, but it's not considered a bug.
@Antonio Vazquez (antoniov): shift + numpad 4/6 view roll is like rotating the canvas I think.
Just close as Archived if you don't think it's a bug.
It's crashing somewhere in the drawing of the background, but it's hard to say why from the backtrace and difficult to try to fix remotely. It may be something in the specific OpenGL state or shader and not the way the crashing function is called.
@matc (matc) does not have commit rights.
Fri, Mar 22
Looking at this closer, I think your original patch is actually the right one to user here. Sorry for that.
Underlying bug in Blender fixed in rB8b4e0eb88e71: Fix T59962, T60130: error adding image sequence with node wrangler., I'd rather not add workarounds for that kind of thing.
The result looks wrong to me:
Looks to me, but please also commit the tooltips change because a description like "buffer (temp .blend file)" is not at all relevant to users.
I've restored it in the 2.79 branch now, but it stays removed in master / 2.8.
@Tim Stullich (tstullich), search for SUN in source/blender/draw/engines/eevee.
TabExpand will be removed once the clang migration is done, so not worth optimizing.
Clip End in the 3D view sidebar is set to inf, that's not a valid value. Was that set intentionally? It can only work for Cycles to use a very high clip end without artifacts, and even then it should be a regular number instead of inf.
Yes, we should fix such crashes.
The mention is fine, it's just linking to the commit that matches your build.
@LazyDodo (LazyDodo), committed your fixes and batching to improve performance. Did not test performance on Windows yet, on Linux here time went from 10s to 6s.
This was changed for T55921: Toggling visibility for collections doesn't work in Pose mode, but should only apply to object and pose mode and I think.
You can go into the preferences of this add-on, and disable the pie menu that overrides the Q key.
Ok, then it's a general issue with Eevee rendering for which we have a report open.
Is this still an issue in the latest builds?
Is this still an issue in the latest builds?
Does setting the 3D viewport to Rendered display mode crash?
Does editing materials work for you outside of 2D animation, or does that crash as well?
@LazyDodo (LazyDodo), maybe installing the older driver again will let you repro the crash again?
You can send me the file privately (to my username @blender.org), however we still expect users to try to isolate the problem.
We still need to have one example .blend to reproduce the problem.
@Dont Want (McLP), please create a new bug report for your case.
RNA_def_property_range imposes a hard limit.
Shutter speed should be 0.0 or higher, there should be no other hard minimum or maximum on it.
Thanks for the suggestion, but this website is not for these kinds of feature requests:
We need a .blend file to investigate the issue, it's unclear what in this scene might be causing issues.
The API could be improved here and we are rethinking the visibility controls in general, but no bug here.
Please see if the problem is fixed in the latest 2.79 build:
Thu, Mar 21
Please try the latest 2.79 build from:
@Johnson Smith (vignette), try installing the latest drivers (126.96.36.19959), your version (10.18.10.5059) is quite old.
I've added a script to rebase and merge master into branches: rBDTa64a4237d820: Add script to merge clang-format changes into branches.
I do indeed prefer Align personally.
Snapping for rotation and scale is disabled by default now, you can enable it in the snapping menu in the 3D viewport.
Then I think the plugin that you are using to open the scene in 3ds max needs to be updated, 2.63 was released 7 years ago, we can't keep supporting that forever.
I think the main confusing thing with this will be if you paste e.g. a material, it's not obvious where it ends up. Objects appear in the viewport but for other datablocks it's not clear.
clinfo shows the same GPU twice, so I think there is something wrong with your AMD driver installation. Maybe there are remnants from an older driver install, or a bug in the AMD driver.
Started docs here:
We haven't been able to reproduce this ourselves as developers, but marking as high priority due to the number of reports.
Updating drivers may help, meanwhile this is also a duplicate report.
Thanks for the suggestion, but we do not handle them on this website:
When rendering with CPU only, the tiles sizes might be too big for all cores to be used. That's something we want to improve still, so you don't have to tweak tile size for best performance, but it's outside the scope of the bug tracker.
Wed, Mar 20
Color sockets in Cycles and Eevee do not actually have an alpha value, this is a leftover from old Blender Internal code. This needs to be cleaned up in the UI still. For transparency you should mix with the Transparent BSDF.