- User Since
- Feb 24 2021, 10:46 AM (76 w, 4 d)
Thu, Jul 28
Tue, Jul 26
Jul 15 2022
Yepp, issue resolved.
Thanks for the solution. 😉
Jul 13 2022
Jul 10 2022
Just for info !
Jul 6 2022
The way E-Cycles uses Light Linking is the worst way I have ever seen in a 3D App.
We all have to make sure to not end up with a rubbish solution like E-Cycles is using / offering.
Otherwise you'll be in bad dudu with heavy scenes. Or can you remember what kinda light 3, 11, 45, 47, 89 is !?
Jun 27 2022
Maybe we get this fixed too in version 3.2.1 on wednesday !?
Jun 9 2022
Jun 1 2022
May 30 2022
I guess I found the cause of it.
When changing the execution mode to "Fullframe" (like in the image below) the resulting exr-file will have all output layers being the same image.
Just Checked with version: 3.3.0 Alpha, branch: master, commit date: 2022-05-29 19:25, hash: rB3c0d7152c89d
and CPU with the same result.
May 29 2022
May 10 2022
With all those inspirations we should not forget that, however it will be implemented it must be animatable as well.
(Thinking of fade transitions etc.)
May 2 2022
Apr 28 2022
So I just switched off 'Noise Threshold' and can now render with insane smple numbers like for fun with 28514 samples, without crash/stripes.
With tile size 2048 it is rendering fine without stripes.
And the set resolution as tile size 5120px, it get's stripes again.
It was just an update on the latest intel version for compare with the above tests.
Your test showed that, the intel side is propably not fixed yet.
Must be on the Intel side so !?
Apr 27 2022
That's my setup, and I'm pretty happy with it!
What's wrong with this setup?
Apr 26 2022
I can confirm the difference in brightness on both CPU & GPU
with the below listed setup
needs reinstall of svn and apr-util via brew to compile
I can confirm this also for blender 3.2
version: 3.2.0 Alpha, branch: master, commit date: 2022-04-24 12:33, hash: rB17eb8a9cebd5
Apr 22 2022
Can you please make another screenshot, WHEN you render the next time.
Apr 21 2022
resolved after 3 try and #b719fa267ac9 version...
Apr 13 2022
https://developer.blender.org/T96471 got closed BUT still present in :
Operating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15
@Ryan Rickett (glencandle)
So then managing many lights,, you have to go to each light instead of the manager that keeps all of the lights/objects in one place.
Also Gurra already explained using lights or objects.
Apr 8 2022
Also noticed if you use ONLY two lightgroups, rendering is fine.
One more and it will break.
Apr 7 2022
makes no difference.
But I noticed with the last updates that you can't get over 8192 pix anymore.
It's about the ""LightGroups"" and a bigger render resolution ON macOS !
see scene file above & use with macOS & blender 3.2
render 100% 5120x2048pix as set in the file.
Apr 6 2022
fatal crash = macOS and hole mashine crashed in a blink -- NOT blender crashed
total mac, macos and blender reboot happened
What OS etc. did you use to test? Please don't tell me it wasn't macos...
I mentioned it at least 3 times that I use Intel Mac, latest macos 12.3.1 with AMD Radeon & blender 3.2 from yesterday and tonights latest build.
Makes no sense to state here that you don't have the bug, without mentioning the OS you tested with.
(Every time the same)
Apr 5 2022
When I use the ACES 1.2 Lut-folder and the config.ocio from Git, in blenders 'colormanagement' folder, it works fine.
Apr 4 2022
**Each light (standard light & mesh light) needs a dropdown menu for everything that can be lit and is in the actual scene file (switched on/off) + linked groups or meshes from other blendfiles.
By defauls everything + groups gets added to this dropdown list of each light .
Apr 1 2022
Still continuing on latest blender version:
Mar 24 2022
Only thing I can think of it the simplify option in render settings. Your settings there and the fact that the subsurf is basically switched off for some of the meshes, could produce a problem.
I had a similar thing with just a plane, ADAPTIVE subdevided (unapplied) and it used up all my RAM and after 20 min. I stopped it.
Mar 22 2022
To check for the OS and OS version you could use some of those sites,
You'll get the info like this:
Mar 20 2022
Plroblem is here...in the users blend file...
Mar 18 2022
Mar 17 2022
Well Germano Cavalcante, do you except a hug ! :-)
Mar 16 2022
I use the latest macOS 12.3 already, as of the day of this report when the 12.3 update arrived !
Those versions (say 3.0.0, 2,.93LTS) AREN'T able to, because Metal for Intel Mac's and AMD cards was introduced with blender 3.1, 3.2 etc...
Mar 15 2022
Mar 9 2022
Mar 3 2022
Mar 2 2022
Feb 17 2022
Feb 16 2022
One question to understand better:
Thanks for the info..not the first time on blender.
If you can't reproduce it AND say: (because the last weeks commits in this area might actually make a difference here) , makes no sense but me wonderering!
The crash text is also provided by me ! (See first post)
Feb 7 2022
Did this already before sending the bugreport :-)
It happens with factory & personal settings with blender 3.1 / 3.2
Feb 4 2022
Feb 3 2022
Can confirm it working on Build: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: rBdc2d18018171
Feb 1 2022
Works only with still but when having an already set animation of the coordinates of the light, you can do it all over again...
Jan 21 2022
First you tell that you relay on user testing, than you don't want updates on it.
Makes no sense, BUT explains why it took soo long to understand what's the issue.
Continuing with build: Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-20 22:26, hash: rB5fca280c803b
Jan 20 2022
3DViewport is missing visuals . No grid, selections,...to see
continueing on the following build:
It's continueing on the following build:
Jan 19 2022
I'm pretty sure any mac will have this issue.
Anyways, hope it's getting tested soon.
Question: Are those builds getting tested in any kind (if it even starts up) before upload to git etc.., OR
how is it working with the daily builds? Is it automated !?
Dec 28 2021
Two interesting things:
Dec 18 2021
Dec 14 2021
Just for Information on todays macos updates:
Dec 13 2021
Sounds good to me, since light linking is coming and could maybe managed at the same time.
Dec 9 2021
I tested it again several times with 3.0 stable and beta.
One time everything works, the next time not. It works one/off.
Totally wired. Not kidding!
On macOS 12..0.1
blender 2.93.5 keeps existing vgroup
blender 3.0 stable & last beta keeps both vgroups
blender 3.1 from blender.org works as intended
blender 3.1 self compiled & works as intended (as of 9-december 12o'clock updated and compiled)
Dec 8 2021
This was a related question. I thought maybe the warnings coming up because of a misconfig of my workflow.
I just compiled it, and it works fine now. THX Brecht :-)
Here is the terminal log from compiling blender on macos 12.0.1 Intel and Terminal and Xcode 13.1 with this guide https://wiki.blender.org/wiki/Building_Blender/Mac
Dec 7 2021
To be honest, if you can make it work for all lights and that it works with transforms than it's fine to me.
That's how I learned it since 25 years ago. You have the textured light that can be moved, rotated, etc. including rotating z axis of the light to not have to move the light itself.
Operating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29
Using terminal with this https://wiki.blender.org/wiki/Building_Blender/Mac guide, always ends up without the ability to select.
I can't select the objet left, right, top, aside and direct. BUT I can select it when selecting it underneath itself.
Feels like that everything is abobe 0 can't be selected and vice versa.
Dec 5 2021
Oct 29 2021
Oct 18 2021
Nice, and the tiny curve points are still not managable !
Oct 14 2021
Sep 3 2021
when having several different blender 3.0 versions for testing && they are sharing the same prefferences (config/scripts) folder for all 3.0 versions with the same startup.blend file, keymap config and themes,
It can happen that the startup.blend, keymaps and theme files getting corrupted.
So tested versions from 2.8x to 3.0 + got rid of all the addons and still no luck.
Then I was lucky to put all addons back to work corectly.
I only have 2.93.5 and 3.0 versions.