This projects includes function nodes, dependency graph, rigid body, particles & hair, cloth, fluid & smoke (mantaflow), softbody, node editor and more.
Important links
Contacts
Subprojects
I still have an issue with baking in 2.92 with multiple domains. Any update on the bug?
@Sebastian Parborg (zeddb)
This is becoming a bit weirder than may artist brain can understand, first the tests.
@Nahuel Belich (belich) Great!
Note the I have never myself been able to reproduce broken files it is only from bug reports that I have gotten them.
So if you could figure out how to break it that would be super!
@Sebastian Parborg (zeddb) ill try tonight and let you know
I can confirm a high consumption of memory.
It must have a recursive dependency.
@Fernando Alcala (TriFractal) Please do not the status of the report, leave that to the developers and bug triagers.
@Robert Guetzkow (rjg) Read my last comment please. I don't think it's invalid, but it's your forum, I will not change the status again
I hope, from the bottom of my heart, that this time will be clear what I'm saying! No excuses, I have the blend file and a video showing whats the issue. Something changed in smoke simulations and I think is only when usining the INITIAL VELOCITY option. If this change was intentionaly, wasn't in the realease notes! But i suppose that it is not intentionaly once the fire and smoke simulation looks horrible compared with the last version of Blender!
Here I annex a blend file that was simulated at 2.91 and 2.82 AT THE SAME SETTINGS WITH A PROPER SIZE! If you don't belive me, download it and try it yourself!
Since there is ongoing work for geometry nodes:
I can confirm this behavior, however I am unsure how exactly this is supposed to work.
@Nahuel Belich (belich) can you see if you can reproduce the issue by starting with the original working file and then try to make it break like in the new example file?
I'm guessing it is related to saving and loading the file.
Seems like something is wrong with the hosted test file!
Can confirm.
Hi sorry I was busy with non-3d-related work. I did have a crash in 2.92. I will give it a try again, and I will test 2.93 and see if it crashes. I will be back to you during the next few days!
It's a limitation.
Good to hear. Should you be able to reproduce the issue again, please let us know and create a new report.
Sorry for the delay. I have not been able to reproduce this using the newer builds, so I imagine the issue should be closed.
@Jorge (Newoldschool) Where you able to check if this still occurs in 2.92 or 2.93?
@Fernando Alcala (TriFractal) @Vitor Druzian (Druzian) Am I understanding you correctly that this is considered resolved then?
@Jack Schaberg (Jay_Blend) Could you please check if this problem still occurs in the current versions? Perhaps it is already fixed or we are missing a particular steps that triggers this behavior.
Been trying this out, it is tricky to unplug many noodles to the same socket, and to visually understand the socket array index. Most software has one socket to start, and if it's an array node, they will add another empty socket below. Plug that in, then another will show, plug that new one in, and another will show. In this case you can easily tell how many are in the array, what could be the index position of the socket, and also unplug conventionally without needing to rely on a few pixel wide hotspots.
Can confirm.
Looked a bit into this issue. The crash seems to be resolved and so I'm adjusting the priority.