Oldie: Texture buttons - "Add New Image" - crashes on changing X or Y resolution.
I've greyed out these buttons now, changing image memory that's in use by the
preview render is not supported.
A real fix I did was assigning the new image to the texture, that was missing.
Storing this list in the node has the advantage of requiring far fewer calls to the potentially expensive internal_connect callback. This was called on every node redraw ...
Also it will allow Cycles to properly use the internal links for muted nodes, which ensures consistent behavior. The previous method was not applicable in Cycles because transient list return values are not supported well in the RNA and particularly the C++ API implementation.
not do correct partial updates, now it remembers if the opengl texture is a
non-color data texture or not and takes that into account for the update.
Also includes some renaming ncd => is_data for consistency with color space
terminology used elsewhere.
Ancient 2.5 UI issue:
The button views in Property Editor have an internal storage, to ensure the view
on the buttons stays same when you switch contextes or select objects.
Bug was that - in case buttons were all scrolled invisible - sometimes no slider
was drawn to indicate that.
Discussion on whether this is a good feature or not: the only improvement would
be to store such settings even per object... but that's a feature creep I think.
shows both title safe and action safe areas following more modern standards.
Patch #32822 by Harley Acheson, full description:
Our current "title safe" camera display option is anachronistic. It shows a
border of 10% on all edges, which used to be the recommended title safe area
for 4:3 content on standard definition CRT televisions. However we are very
unlikely to create new projects that output for SD TV at that aspect ratio.
This patch change the option to "safe areas" with and indicates the
"title safe" area (also known as "graphic safe") as well as the "action safe"
area. "Title Safe" is an area visible by all reasonably maintained sets, where
text was certain not to be cut off. "Action Safe" is a larger area that
represented where a "perfect" set (with high precision to allow less
overscanning) would cut the image off.
The current recommendation for Action Safe is 3.5% on all edges, which is the
maxiumum overscan for TVs now. The recommended title safe is now 5% vertically
and 10% horizontally for content that is of wider aspect ratio than 4:3. The
reason for the difference between horizontal versus vertical margin is because
wider content would be letterboxed on an older 4:3 television, giving it
additional margin.
when saving, rather we flip the compressed texture during load. The code used
here comes from the chromium O3D project:
http://src.chromium.org/chrome/trunk/o3d/core/cross/bitmap_dds.cc
Also made it only load compressed for power-of-two resolution images, it doesn't
seem to work for other resolutions, just falls back to non-compressed then.
When I added DPI support in the UI, I added code that refreshes views for 2d
regions. These refreshes also happened on screen switches or file select, causing
header views (horizontal scrolled) to clear.
Now the code less intrusive, changing header views in fewer cases.
This is a patch provided by Anthony Edlin. Thanks dude!
When playback was running fast the frame step could be 0, making playback jittery.
this commit just makes sure the frame step is at least 1, but there is still an issue with framedrop skipping too many frames (or too few) which Ill check on next.
Menu buttons: the text label in a button was clipped on right too soon, there's
more space. Noticable especially on popup buttons with labels like "X" or "Y".
* Lower the required number of vertices from four to three. The new
backend correctly outputs a triangle in this case.
* Fix the check for the number of input vertices. Before it was
counting total number of input elements including edges and faces.
* Don't mark edges as holes if they are loose.
* Don't allow duplicate faces to be created.
* If use_existing_faces isn't enabled, but a face in the convex hull
has the same vertices as an existing face in the mesh, mark it as
output geometry rather than interior geometry.
* Fixes bug [#32960] Convex hull operator crashes when 'make holes' is
selected.
projects.blender.org/tracker/?func=detail&atid=498&aid=32960&group_id=9
Patch by Yasuhiro Fujii, thanks!
Original issue was that in vases viewport's lens are different from default
value switching between perspective and orthographic projections will change
viewplane a lot, which is disorienting and annoying.
Patch by Sebastian Nell, thanks!
Still not ideal (it could some smarter selection policy in such case perhaps),
but it's less annoying than it was before.
Using "outliner data operation" on vertexgroup suggested it should work, but this is not
supported yet. Similar to all the other cases it throws a Report warning now.
You don't believe it, this bug traces back to 2002. Went by unreported for a decade.
If you link in an object, delete it, and relink again its materials are lost!
Easy fix, annoying error. :)
Problem here is that muted nodes and reroute nodes are supposed to be removed from the execution node tree during the localize function. However, this is function is apparently only used during preview renders and must be considered a hack (is there anything that is not a hack in BI?)
Now the mute/reroute check happens in the node tree exec functions still used by BI and the legacy compositor and texture nodes. It uses the same internal_connect function from nodes to assign input stack indices directly to outputs (which also avoids overhead). Localize function also still does this. Cycles/Tile should also implement muting/reroute in their intermediate node layers by using this function, then it could be removed from localize too.
