Blender 3.1 release.
| Phase | Description | Start Date | Branch |
|---|---|---|---|
| Bcon1 | New features and changes | October 27, 2021 | master |
| Bcon2 | Improve and stabilize | January 5, 2022 | master |
| Bcon3 | Bug fixing only | January 28, 2022 | blender-v3.1-release |
| Bcon4 | Prepare release | March 2, 2022 | blender-v3.1-release |
| Bcon5 | Release | March 9, 2022 | blender-v3.1-release |
| Corrective Release | March 30, 2022 | blender-v3.1-release | |
Information about the release cycle and of Bcon phases
For features already committed check the release notes.
Not acceptable "trade-off", for architectural modeling...
Thanks for the report. While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.
I didn't notice a big drop in speed.
(group time = 30 milliseconds, 1 frame in game = 17)
But when animating it reduces fps from 30 to 18
I'm not sure if it's a digression, more like a cost. But if you want to speed things up, this might help:
MCH-spine.005 (or simply a head rig, with up to 2 neck bones) could be fixed by:
a) consinstent to other cases by adding a copy scale constranint pointing to the neck ctrl.
b) considering this a special case and enabling back ihnerit scale average on the MCH bone
As said before, we cannot fix issues inside of Quixel. Closing again.
Personally I've already been using git status --ignore-submodules=none for a long time. This just means I can return to plan git status and remove the alias I created for this.
Sorry, Didn't find same bug submitted before. So what about the people that don't have GPU with OptiX tech? Previously it was so convenient to not bother with overlapping geometry to render something. But now you always have to merge this meshes into a single mesh... Just consumes time for no reason honestly.
There is a report for this issue already T96475. In that report the Cycles developers came to the conclusion that it is not a bug. I will merge these two reports.