I can see that smoothstep is very useful and yes, maybe more useful than the others. I did not mean to discard the idea of having a single node that does this operation. The two-node-setup I showed was just to show how the operation works internally.
Tue, Dec 3
Pretty sure this has the same roots as T71552: Material view and Eevee Rendered View display glitch when scene contains hair particle systems with high amount of instances.
Thx for this!
The face skipping in the volume calculation seems wrong. Functionality wise that looks good. Could not test it right now because I'm fighting some other linking issue...
Can confirm, was working in 2.80
Cleaned up the margin use in the textview code:
Thx @Benjamin Sauder (kioku) for checking! (in the end this might boil down to simply a performance issue)
In the video, this seems to kick in pretty early though, cannot reproduce something similar on my end.
This was fixed, see T71932: Crash when type "ext" in search.
And you already noted, that this works fine in 2.82 alpha, so... not sure what you are asking?
As mentioned in my review some posts back, there are unused imports.
Going over the code with pylint, there are still quite some unused imports & variables being defined.
These were generated from running:pylint *.py | pcregrep "Unused.*(variable|imported)"
I cannot reproduce this with either the latest stable or current development versions of Blender:
please test with latest blender from https://builder.blender.org/download/ and if you still have this error, reopen this task.
I assume this is something specific to your setup (blender launches very quickly here):
rather duplicate of T71774
duplicate of T71774. Please test your file and if it still fails to import, reopen this task.
Unable to reproduce with B281, B282 using 19.30 AMD Pro drivers, but I don't have the exact card that the user reported (Vega64).
Please when reporting GPU issues always provide us with the system-info.txt generated by Blender. Help -> Save System Info.
duplicate of T71845
So, I've checked that I have the latest drivers available for my integrated graphics card. The PC is a HP (maybe it controls something of the drivers?).
I think this is probably acceptable, overall.
Seems the outline of the selected object is still drawn.
@Clément Foucault (fclem) just a sanity check that this won't break other logic.
hi @Wayne Dixon (waylow) You have access now to the documentation. Please read this first: https://docs.blender.org/manual/en/dev/about/contribute/patch_commit.html
If you need help or have any issues, feel free to contact me in irc or preferably blender.chat python channel.
Thanks, we will need to organize your commit rights as currently your not yet a member of the addons project. We can discuss this also.
Thanks again also for the great update.
I'm going to try that
Fine, while I still regard this as a bug, I can see how it would be better to be designed with and approved by module owners. But even though the current behavior is expected by developers, it is not clear to the user what to expect. Could the tooltips at least be made more consistent so that the user has a better idea what is View Layer specific and what is global across all View Layers?
Re: info editor, adding icon at start of each line and reversing the text drawing direction seems like something that the current text-view could support easily enough.
If there are other changes in the future... there may be some reason not to share code. For now I think sharing code is fine.
Suggest to do this in steps
Thanks for the report, we have refactoring this part last week, so it can be that some of these regressions happen.
Thanks for the report. It appears this crashes because Blender ran out of memory. (seems like a single mesh allocates 8GB of memory even without any textures and other related issues). The GPU you have can only handle 2048(GDDR5) or 4096(DDR3) depending on the exact model.
I found removing the current offsets gives results closer to the middle of each character.
Thank you @Brendon Murphy (meta-androcto).
Warning message for GPU cache size overflow. Useful in big scenes that could hint the user to use bigger sized cache.
Up to date with latest origin/master
Still the have a problem with latest 2.82 nightly build (from 3 december):
Slow performance of EEVEE viewport with some ghost:
Forgot to delete that.
The visual would still be different enough to be consider a bug yeah?
Forgot to delete that.
@Julian Eisel (Severin) could you check if this is ok for inclusion in 2.82?
You have a spot light disabled in a viewport, but on render it enabled:
if the light enabling, render result is lighter than preview on viewport:
But viewport material is darker than the rendered version
Clément, you're exactly right! I disconnected all of the bump nodes in the scene and it now renders in Eevee in 2.81+
i have this bug all the time when wireframe is staying and u have to go to object mode >> edit mode >> object mode and it disapears.. however it is still visible on all other objects so u have to go every single one or just restart blender.
@Philipp Oeser (lichtwerk) Yes I think this is probably the best solution for now. ND_TOOLSETTINGS at least will update multiple headers and not whole areas. You will want to do something similar just above that code were it saves out proportional editing toolsettings also. At least now the button display will not be stale.
Hi, thanks for the report.
It works. Both your keys have the same value.
@Brian Staub (invertedNormal) Can you try simplifying until it works?
The question is not whether it happened but how we can reproduce it.
We appreciate you filling a report, but without that information, the report will be closed.
hi, still some work to do here. After discussions we will remove the not working world map and restore some sane presets.
Small code clean up will follow and committed to contrib.
We will then look at viability of 2.82 release.
I can confirm happen.
Hello Omar, can I know this bug is already fixed or is in progress. I was it is moved to resolved?
If yes, where I can find the fix build for it. Is it cumming as fixed package in 2.80 or 2.81 or in 2.82 release?
I have some questions about the new layout: