トップ > 交流 >雑談 >最新版の修正情報で気になったもの

Re: 最新版の修正情報で気になったもの

169件表示 すべてのコメント一覧へ

投稿ツリー


このトピックの投稿一覧へ

通常 Re: 最新版の修正情報で気になったもの

msg# 1.114
depth:
1
前の投稿 - 次の投稿 | 親投稿 - 子投稿なし | 投稿日時 2014/5/10 10:42
完全無欠猫  長老 居住地: 兵庫  投稿数: 750
今回もCrash要因の修正が多かったので、もし気になることがある人は最新のデイリービルドを試してみるといいかも知れません。

Crash関係:
SHA-1: d5588fd658dc0c776a33e55ccbfaed1a3974b396
* Fix T40113: Skinned meshes with non-animated shape keys crashes the BGE.

SHA-1: f622691691547bb364fe6a560124583030d55c11
* Fix access violation when painting with tiled textured brushes + airbrush + small brush size.
　Fast textured strokes meant that sometimes the update width (calculated
　from stroke distance) would be greater than the new ibuf width. This
　meant out of bounds access for the new ibuf.
　It's totally strange that I couldn't reproduce this issue on older
　versions since the logic here has not really changed much between
　versions.

SHA-1: c80e9866c8615c1742bc74506f8c8fe574552777
* Revert "Fix wrong job type used in cycles bake operator, could cause crashes."
　This reverts commit 97823f604796fb008fef03653974473ece75d18e.
　I was to push a fix based on Brecht's solution (this commit) when he did the same.
　This fix is correct, but it misses replacing WM_JOB_TYPE_OBJECT_BAKE
　with WM_JOB_OBJECT_BAKE_TEXTURE in the rest of the file, which may lead
　to problems when calling the operator in a quickly sucession -
　WM_jobs_test also tests for the same type of JOB.
　I created WM_JOB_TYPE_OBJECT_BAKE elsewhere, may as well use it. Unless we revert 20c90ea and f194da3.
　I'm fine with either way, just trying to get master to work again ;)

SHA-1: f194da34555161f5ac026c54a86861f59a0f8797
* Bake API: reports were used after being freed leading to random crashes (fix T40077)

SHA-1: 97823f604796fb008fef03653974473ece75d18e
* Fix wrong job type used in cycles bake operator, could cause crashes.
　Ref T40077.

SHA-1: 31849cafc26ad3e90ba308a14df5bd6ca66a4cbb
* Fix for random crashes when grabbing (rmb-drag) NLA strips
　Although these crashes were quite sporadic, they seemed to happen most when
　rmb-dragging strips randomly in quick succession. The most likely cause seems
　to be a null check I accidentally took out during one of my commits yesterday.

SHA-1: 1064b74196dc50bc4924e9196fdf5a872f74f6cc
* Fix for an occasional crash in Freestyle stroke rendering.
　Materials were freed before releasing meshes that may have references to the materials.

気になったもの:
SHA-1: 40520d549d50bb227b06d46b35c91887171d2767
* Freestyle: Stroke rendering optimization.
　Previously mesh objects were created for individual visible stroke segments (recalling that
　a stroke may consist of alternate visible and invisible segments). This could result in an
　excessive memory consumption in stroke rendering when strokes are composed of many
　short visible segments (for instance by means of dashed lines and/or blueprint geometry modifiers).
　Now mesh objects represent individual strokes instead of stroke segments, which tends to
　reduce the number of generated mesh objects by an order of magnitude.
投票数:0 平均点:0.00

  条件検索へ

ログイン

ユーザ名:

パスワード:



パスワード紛失

クイックリンク

2021/07/01版
●Blender.org
BlenderFoundation
- Blenderのダウンロード
- 公式チュート等
- 公式マニュアル（和訳）

●ニュース(英文)
BlenderNation

●Blenderコミュニティ
blenderartists.org

●Blender Q&A
- Blender Stack Exchange

●テストビルド
Buildbot(自動生成)


●開発関連
公式開発サイト
Blender開発blog
Blender Wiki