| Age | Commit message (Collapse) | Author |
|---|
|
Needed for UI scripts to detect mixed weight paint + pose mode.
|
|
* Added a TL;DR first paragraph summarizing that one shall not keep any
reference to Blender data when modifying its container.
* Added some info about fact that adding items to some data containers
(like Collection) can also invalidate existing items (due to array
re-allocation).
* Added a Do/Don't example which shows a crash after adding some items
to a collection.
Related to T61297.
|
|
|
|
|
|
We don't attempt to have docs for all args, so don't warn about this.
|
|
|
|
Following removal from C source code.
See: 8c68ed6df16d8893
|
|
|
|
|
|
Needed for Python to easily support multi-object edit/pose modes.
|
|
We don't have this for other painting modes,
no need for a special case here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Makes it clear seconds are not integers,
also avoids conversion to float.
|
|
|
|
`gpu_extras` was always visible
|
|
There is a new `bpy.app.timers` api.
For more details, look in the Python API documentation.
Reviewers: campbellbarton
Differential Revision: https://developer.blender.org/D3994
|
|
The HTML title did not make it clear that these are docs for the API rather
than a general Blender documentation. Some of the page titles were also too
long and redundant.
|
|
|
|
|
|
|
|
I think this example does not belong into the api docs and certainly not in the place where it was until now.
Maybe this can become a template in Blender but personally I don't see much value in it as an "official example" because it is hard to see what is going on exactly.
There are a few other examples that show how to use the GPUOffScreen object now.
|
|
|
|
|
|
|
|
found by Omar Ahmad
|
|
|
|
|
|
Technically this is only the view matrix, not model view matrix.
And view layer was missing from the pydoc.
|
|
- Was setting active state, making it necessary to backup/restore
active object in cases where this isn't needed.
Existing scripts are explicitly setting the active object when needed.
- Use a boolean select arg (toggle selection wasn't used anywhere).
- Add an optional view layer argument since scripts should be able to
operate outside the user context.
|
|
|
|
|
|
RNA's ViewLayer would present 'first level' of layer collection as a
list (collection property), when it is actually now only a single item,
same as the scene's master collection.
Note: did not try to update view_layer python tests, those are already
fully broken for quiet some time I guess (they still assume
view_layer.collections to be mutable e.g.)...
|
|
Was still 2.7x code... ;)
|
|
|
|
|
|
|
|
Loop triangles are tessellated triangles create from polygons, for renderers
or exporters that need to match Blender's polygon tesselation exactly. These
are a read-only runtime cache.
Tessfaces are a legacy data structure from before Blender supported n-gons,
and were already mostly removed from the C code.
Details on porting code to loop triangles is in the release notes.
Differential Revision: https://developer.blender.org/D3539
|
|
|
|
Addressing the changes introduced on: 43fa51835adee390aa4bcb9fe3bda1034480b7cf
|
|
code to execute on __main__
|
|
shader.
Strange that the `bpy.utils.register_class` utility does not remove the reference of the class with same name.
|
|
The image I get is a bit too dark, which is the same I get in the viewport
itself when there is no Display Device. So I believe for cases like this
we need to have color management on top of the buffer.
Also, on EEVEE it looks like it needs to clear some extra buffers. You can see
that, by rotating the camera view around.
That said, this is the first step to bring back fun addons
that use external offscreen buffers.
Note: When using gpu offscreen with POST_VIEW (as oppose to POST_PIXEL)
I get a crash with DST having 0xFF..
|
|
|
|
Differential Revision: https://developer.blender.org/D3700
|
|
Also some syntax corrections.
|
