Cycles : Update to 5.1.0 with even sample motion blur patches#298
Cycles : Update to 5.1.0 with even sample motion blur patches#298boberfly wants to merge 1 commit intoGafferHQ:mainfrom
Conversation
So the build might change from one day to the next if something changes on that branch? If so, we can't accept that - we need dependencies builds to be completely repeatable. Maybe you can tie it to a specific commit by SHA? How does this branch relate to the official 5.1 release anyway? Is it where maintenance will be done for patch versions? And is a tag for a patch likely to appear before we release 1.7? |
|
Hey @johnhaddon The difference is just that |
|
I don't mind if |
|
@murraystevenson I have an SSE2NEON/config.py that I could bring over to this for macOS silicon if you'd like? |
5f5dc99 to
5acf47f
Compare
|
Ok I added SSE2NEON in there, @murraystevenson I needed to use |
5acf47f to
ef2bed1
Compare
|
BitstreamVera mirror failing again? Argg... :) |
|
@boberfly the BitstreamVera mirror is back online so I reran CI. It looks like the newly added |
ef2bed1 to
a56ad64
Compare
I was able to upstream the
type_names()from Brecht however it isn't using the tagged release but rather the release/v5.1 branch link just to note.https://projects.blender.org/blender/cycles/src/branch/release/v5.1/
I don't use gafferDependencies anymore and haven't fully tested the build process, they did quite a bit of cmake changes so I suspect this may not build out of the box fully.
I have changes for Gaffer to go with this as well coming.