https://wiki.blender.jp/index.php?action=history&feed=atom&title=Dev%3ARef%2FRelease_Notes%2F2.40%2FModelling%2FModifiers 2026-07-27T14:03:07Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=Dev:Ref/Release_Notes/2.40/Modelling/Modifiers&diff=151555&oldid=prev 2018-06-28T21:17:11Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 21:17時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=Dev:Ref/Release_Notes/2.40/Modelling/Modifiers&diff=151554&oldid=prev 2016-05-12T15:25:08Z

<p>Created page with &quot;==Modifier stack== New feature: Modifier stack - add modifier stack UI code (lives in object panel) ==Mirror Modifer== ==TexMesh works with subsurf== New feature: TexMes...&quot;</p> <p><b>新規ページ</b></p><div>==Modifier stack==<br /> New feature: Modifier stack<br /> - add modifier stack UI code (lives in object panel)<br /> <br /> ==Mirror Modifer==<br /> <br /> ==TexMesh works with subsurf==<br /> New feature: TexMesh (texcomesh) works with subsurf now<br /> <br /> <br /> ==Incremental Subsurf in Object Mode==<br /> <br /> The previous release introduced incremental subsurf calculation during<br /> editmode but it was not turned on during object mode. In general it<br /> does not make sense to have it always enabled during object mode because<br /> it requires caching a fair amount of information about the mesh which<br /> is a waste of memory unless the mesh is often recalculated.<br /> <br /> However, for mesh's that have subsurfed armatures for example, or that<br /> have other modifiers so that the mesh is essentially changing on every<br /> frame, it makes a lot of sense to keep the subsurf'd object around and<br /> that is what the new incremental subsurf modifier toggle is for. The<br /> intent is that the user will enable this option for (a) a mesh that is<br /> currently under active editing or (b) a mesh that is heavily updated<br /> in the scene, such as a character.<br /> <br /> I will try to write more about this feature for release, because it<br /> has advantages and disadvantages that are not immediately obvious (the<br /> first user reaction will be to turn it on for ever object, which is<br /> probably not correct).<br /> <br /> So, modifiers in editmode are back (which means auto-mirror<br /> in edit mode works now) although still not finished. Currently<br /> no cage is computed, the cage is always the base mesh (in<br /> other words, Optimal edge style editing is off), and the final<br /> mesh currently includes all modifiers that work in edit mode<br /> (including lattice and curve). At some point there will be toggles<br /> for which modifiers affect the final/cage editmode derivedmesh's.<br /> <br /> Also, very nice new feature is that incremental subsurf in object<br /> mode returns a ccgderivedmesh object instead of copying to a new<br /> displistmesh. This can make a *huge* speed difference, and is very<br /> nice for working with deformed armatures (esp. with only small<br /> per frame changes).<br /> <br /> ==Wave modifier==<br /> - added wave modifier &amp; removed old wave effect<br /> <br /> ==decimate modifier==<br /> - added decimate modifier &amp; removed old decimate interface<br /> <br /> ==modifier panel==<br /> - modifier UI update (aka, find the modifier buttons!!)<br /> - moved back to editing buttons, where life is now cramped... switched<br /> to constraint style foldout panes, still a WIP. In particular not<br /> sure what buttons should be in header (and if current toggles stay<br /> in header if they should also be in an expanded pane). Also need<br /> new icons for move up/move down (and drag and drop would of course<br /> be nice). Finally current plane is to make it so modifiers will<br /> expand out in modifier pane for horizontal orientations instead of<br /> just going down down down to goblin town.<br /> <br /> - added support for vector icons, from user API side is just like using<br /> a regular icon... on icon side is defined by a function in resources.c<br /> instead of using the blenderbuttons png file. vector icons are much<br /> easier to add and scale properly. intent is that vector icons would<br /> be drawn in window coordinates which lets icon developers make the<br /> most beautiful icons, but this requires some tweaking of the interface<br /> drawing that I am not going to do atm.<br /> <br /> ==acopy button==<br /> added copy button to modifier stack UI<br /> <br /> ==subsurf and mirror as cage==<br /> It is now possible to have a mesh with mirror/subsurf modifiers where you<br /> can edit with both as cage. Selecting the mirror'd part works, but of course<br /> transform is flipped so it is a bit weird. Not the cleanest code in the<br /> world and I can't say I am really happy with the architecture but it works for<br /> now and supports the existing feature set.<br /> <br /> ==added modifiers to outliner==<br /> modifiers added to outliner<br /> needs icon<br /> <br /> ==added armature hook and softbody modifiers==<br /> - added armature, hook, and softbody modifiers,<br /> added conversion of old hooks to modifiers.<br /> <br /> Old hooks used a quirky weighting system during<br /> deformation which can't be extended to modifiers. On the upside,<br /> I doubt anyone relied on the old quirky system and the new system<br /> makes much more sense. (Although the way falloff works is still<br /> quite stupid I think).<br /> <br /> - switch to using softbody modifier, controls enabling but does not have<br /> variables, these are still in same place. enable button automatically<br /> makes/enables modifier.<br /> - update modifier interface to enforce modifiers with the require-original-<br /> data flag to not move beyond deforming modifiers.<br /> - enforce only one softbody modifier allowed<br /> <br /> NOTE: Once again, no modifier stack for lattice yet means softbody for<br /> lattice does not work atm.<br /> <br /> - added interface option to convert a virtual modifier into a real modifier<br /> - added option to parent to lattice object or lattice with deform<br /> <br /> - added recalc ob, recalc data options to ctrl-alt-shift-t timer<br /> <br /> - changed modifier panel to not allow manual addition of hook or<br /> softbody modifiers<br /> - changed apply modifier to apply to existing mesh (fixes bug with<br /> materials) and to warn about loss of tface/mcol/keys/dvert/sticky<br /> for all modifier types<br /> - changed modifier UI to not display disclosure triangle for virtual<br /> modifiers<br /> - changed softbody ui to allow enable/disable<br /> <br /> - readded Subsurf &quot;optimal&quot; edge drawing/rendering<br /> <br /> <br /> - added hook &quot;cursor center&quot; feature (sets hook center to cursor position),<br /> gives better control over falloff<br /> - added modifier UI access to hook &quot;select&quot; and &quot;reassign&quot; features<br /> <br /> - enable modifiers for curve/font/surf types... a little hacked in<br /> but should work ok. Means new features! Wave effect for curve/font/surf<br /> and armature deform as well.<br /> - new feature, added circle select support for FACESELECT<br /> <br /> ==boolean mesh modifier==<br /> doesn't work with layered modifiers yet (just uses base mesh), although may<br /> god have mercy on your soul if you want to run boolean on a<br /> subsurf anyway<br /> <br /> ==TODO==<br /> todo: add drawFacesTex for ccgderivedmesh<br /> <br /> <br /> There is a display bug that already existed but is more obvious with<br /> new modifiers where parts of the pane get drawn in a different area<br /> after toggling editmode. It has to do with drawing parts of the interface<br /> using GL instead of 100% buttons. I try to keep my grubby little toes<br /> out of the interface code so this can wait for Ton to return.<br /> <br /> After the window coordinate stuff is sorted out with vector icons<br /> it probably makes sense to move all non-photorealistic icons in blenderbuttons<br /> to vector form just so scaling goes better.<br /> <br /> Deform weights are still stored in a pretty expensive and unnecessary<br /> way, probably use about twice as much memory as needed, and do<br /> way too many memory allocs.<br /> <br /> There is a still a bug in that selection is using the wrong<br /> mesh to draw.<br /> <br /> NOTE: Although you can turn SB on for curve/font objects at the<br /> moment it doesn't really work because they call deform in<br /> multiple steps and this confuses SB. Not sure how to deal with<br /> atm.<br /> <br /> Still todo: TFace edge drawing is still not always correct in face<br /> mode, in particular with a mirror modifier when mesh has edges (and<br /> no preceeding subsurf). Have not yet decided how to deal with this.<br /> Best solution is probably to do switch to meshes all having MEdge's,<br /> in which case I can get rid of TFace edge flags (and need to recalc<br /> modifiers on tface selection change).<br /> <br /> Still are some inconsistencies in FACESELECT mode edge drawing to<br /> be ironed out.<br /> <br /> - disabled incremental subsurf support (during object mode) for the<br /> time being, misses features for texture/color drawing and I don't<br /> have time to finish at the moment. can return once UV/colors are<br /> incorporated into subdivision.<br /> <br /> This exposes a bug in boolean, apparently the output is somehow<br /> random (hash on alloc'd pointer value perhaps) which is sortof<br /> lame.<br /> <br /> It also makes more apparent the desire for some level of control<br /> over dep graph evaluation during editmode (at the moment dep<br /> graph is reevaluated for a mesh object in editmode, but since<br /> mesh changes are on editmesh other objects don't really see<br /> any change, so it is a wasted recalc).<br /> <br /> Also by the way I wrote down some notes on how curve code<br /> works, nothing spiffy but it is at:<br /> <br /> http://wiki.blender.org/bin/view.pl/Blenderdev/CurveNotes<br /> <br /> ==bug fixes==<br /> - more nurbs fixes... as it turns out, rendering of cyclic UV didn't<br /> really work at all. Fortunately no one actually *USES* nurbs so<br /> no one noticed. This is bug from NaN days (strubi, I am looking at<br /> you here) which I guess says a lot (or a little) about NURBS usage.<br /> And as usual, the correct code is shorter.<br /> <br /> ==other==</div>

wiki>Blendify