[Blender] Suivi des évolutions (et gratuites en plus)

EDIT : Cette discussion est maintenant dépassée :
Blender prend actuellement en compte les textures DDS des NIF... si vous avez installé le plugin le plus récent d'import export NIFtool...

Citation :

Posted By: amorilia
Date: 2007-09-02 09:40
Summary: PyFFI 0.4.4 released
In this release support for Oblivion's bhkMoppBvTreeShape has been added.
The mopp data can be parsed giving a detailed overview of the
opcodes, parameters, and jumps. Also a simple mopp for an
arbitrary mesh can be generated. Note that the generated mopps
are far from optimal: they simply traverse all triangles
within the bounding box.

Trouvé sur : sourceforge

Cela présente t-il un intérêt ?

Révolution ?

Dernière version du plugin d'import export des NIF pour Blender :

Citation :

NIF File Format Library and Tools
Posted By: amorilia
Date: 2007-09-05 06:42
Summary: Blender NIF Scripts v2.1.6 released
NIF is a popular format used by many 3d games. The Blender NIF scripts enable you to read and write files that are compatible with these games in Blender.

This release significantly improves the import of Morrowind's better bodies meshes, in particular the better bodies skeleton. On export, if the root object is called 'Bip01' then it will now also be used as root node of the nif tree. This will remove a dummy node in exported skins for Morrowind.

You can grab the latest version of the scripts here:

https://sourceforge.net/project/showfiles.php?group_id=149157&package_id=166219

For more documentation and help with the scripts, visit the wiki, or our forum:

http://niftools.sourceforge.net/wiki/Blender

Les explications ici : http://niftools.sourceforge.net/wiki/Blender

Citation :

The Blender NIF scripts enable Blender to import and export NIF files. The latest release version of the scripts require Python 2.5.1, PyFFI 0.4.4, and Blender 2.44.
• Python website where you can download Python.
• Download PyFFI
• Blender website where you can download Blender.
• Download Blender NIF Scripts
The new version of the scripts feature:
• native DDS support - no longer need to convert your textures - for this to work you need a recent svn build of Blender, for instance from http://www.graphicall.org, until this feature has been accepted for release in Blender
• a revamped GUI
• support all NIF versions that we currently know of, including Oblivion's 20.0.0.5 format
• process the xml directly; so any update to the NIF Format description can be immediately used
• built-in stripifier, tangent space calculation, and skin partition calculation
• better skinning support on import

Serait-ce la fin des pb de DDS Oblivion avec le plugin pour blender ?

Les infos sur Blender SVN ici : http://www.graphicall.org/builds/builds/showbuild.php?action=show&id=282

Citation :

Blender SVN - textures in edit mode
ZanQdo
Aug-28-07

Built with:
OpenEXR
FFMPEG
Verse
Game Engine
Yafray
Python 2.5
- CVS Logs:

Bone Heat Weighting
This is a new automatic vertex weighting method, next to the existing
envelope based method. The details are here:

http://www.blender.org/development/current-projects/changes-since-244/skinning/

This is based on section 4 of the paper:

"Automatic Rigging and Animation of 3D Characters"
Ilya Baran and Jovan Popovic, SIGGRAPH 2007
Transformation Constraint
This commit adds a new constraint to Blender: the Transformation Constraint. This constraint gives you more freedom to choose how transforms are copied from one object/bone to another object/bone.

You can assign the Loc/Rot/Scale channels of a source to the Loc/Rot/Scale channels of a destination, specifying the range of motion (per axis) from the source to consider, and the range of motion (per axis) that will be applied to the destination. Also, for each destination axis, you can choose which of the source axes to copy from.
Constraints System
After just over a week of coding, I've finished doing a major refactor/cleanup of the constraints code. In the process, quite a few old kludges and ugly hacks have been removed. Also, some new features which will greatly benefit riggers have been implemented.

What's New
* The long-awaited ``ChildOf Constraint'':
This allows you to animate parent influences, and choose which transformation channels the parent affects the child on (i.e. no translation/rotation/scaling). It should be noted that disabling some combinations may not totally work as expected. Also, the 'Set Inverse' and 'Clear Inverse' buttons at the bottom of this constraint's panel set/clear the inverse correction for the parent's effects. Use these to make the owner not stick/be glued to the parent.
* Constraint/Target Evaluation Spaces:
In some constraints, there are now 1-2 combo boxes at the bottom of their panel, which allows you to pick which `co-ordinate space' they are evaluated in. This is much more flexible than the old 'local' options for bones only were.
* Action Constraint - Loc/Rot/Size Inputs
The Action Constraint can finally use the target's location/rotation/scaling transforms as input, to control the owner of the constraint. This should work much more reliably than it used to. The target evaluation should now also be more accurate due to the new space conversion stuff.
* Transform - No longer in Crazy Space (TM)
Transforming objects/bones with constraints applied should no longer occur in Crazy Space. They are now correctly inverse-corrected. This also applies to old-style object tracking.

Suite Blender SVN...

Citation :

=== General Code Changes ===
* solve_constraints is now in constraints.c. I've removed the old `blend consecutive constraints of same type' junk, which made the code more complex than it needed to be.
* evaluate_constraint is now only passed the constraint, and two matrices. A few unused variables have been removed from here.
* A tempolary struct, bConstraintOb, is now passed to solve_constraints instead of relying on an ugly, static workobject in some cases. This works much better.
* Made the formatting of constraint code consistent
* There's a version patch for older files so that constraint settings are correctly converted to the new system. This is currently done for MajorVersion <= 244, and SubVersion < 3. I've bumped up the subversion to 3 for this purpose. However, with the imminent 2.45 release, this may need to be adjusted accordingly.
* LocEulSizeToMat4 and LocQuatSizeToMat4 now work in the order Size, Rot, Location. I've also added a few other math functions.
* Mat4BlendMat4 is now in arithb. I've modified it's method slightly, to use other arithb functions, instead of its crazy blending scheme.
* Moved some of the RigidBodyJoint constraint's code out of blenkernel, and into src. It shouldn't be setting its target in its data initialisation function based + accessing scene stuff where it was doing so.

Future Work
* Geometry to act as targets for constraints. A space has been reserved for this already.
* Tidy up UI buttons of constraints
Added the invisible 'Bone envelopes to vertex groups' command to the 3D View Weight Paint -> Paint menu
Adds the following selection methods to the Sequence Editor:

Ctrl-RMB and Alt-RMB now call for different selection methods that are helpful when working within a single channel that holds several strips. The Ctrl modifier signals "Right" and the Alt modifier signals "Left".

Ctrl-RMB clicking a strip will select that strips left handle and the adjacent handle of any strip that abuts it on the left, allowing you to move the boundary between the strips without changing their outer endpoints. Ctrl-RMB clicking again on that strip will add to the selection all strips to the left of it, allowing you to slide the entire set of strips out of the way for a new one.

Alt-RMB works the same, but to the right.

Ctrl-Alt-RMB on a strip selects the surrounding handles only, allowing you to move the targeted strip and have the surrounding two strips adjust to follow.
Option when creating a new "screen" to create an empty one
(one with one window) While its one more click, I think this is pretty dang useful.
Sequence Editor: SHIFT+R, Remap Paths (also in pull down menu) This allows to remap the root of a path to another directory. Works on all selected Image strips. That way you can make absolute paths relative, for example. Example: original path: /mnt/orange/finals/06_which_way/06_03b/ to be remapped: /mnt/orange/finals/ remap to: // new path: //06_which_way/06_03b/
Sculpt Mode Added a new input control that smooths the brush stroke. This option controlled by the menu item Sculpt>Input Control>Smooth Stroke. When enabled, the brush has a delayed effect on the model; a green line is drawn to indicate the smoothed path of the stroke. After ~200 pixels, the first half of the stroke will be applied to the model; the process then repeats, with a new segment of the stroke being applied to the model after every 200 pixels. On mouse up, any remaining portion of the stroke will be applied
PyConstraints At last!
The ability to code constraints in Python. This opens up many interesting rigging possibilities, as well as making prototyping constraints easier. - A PyConstraint script must begin with the line #BPYCONSTRAINT - It must also define a doConstraint function, which performs the core actions of the constraint. - PyConstraints use IDProperties to store custom properties for each PyConstraint instance. The scripter can choose which of these ID-Properties to expose to a user to control the behaviour of the constraint. This must be done using the Draw.PupBlock method. Credits to Joe Eager (joeedh) for coding the original patch on which this is based. I've made heavy revisions to large parts of the patch. For more detailed information, and some demo scripts, see the following page: http://aligorith.googlepages.com/pyconstraints2
Curve Selection Tool Refactor
This commit refactors curve selection system to use certain curve selections functions that encapsulate setting of selection flags. New function to select adjacent control points was introduced too. Refactoring made it possible to simplify certain existing selection functions quite a bit. New functionality was delivered as well. Select more/less works now with NURBS as expected. Also two new curve selection functions were added: Select Every Nth and Select Random See http://wiki.blender.org/index.php/BlenderDev/Curve_Selection_Tools for further information
Armature - Duplicating Bones Duplicating bones now also duplicates the Transform Locks, and IK DOF settings, along with constraints
Interfase Ortho/Persp reporting in the View names Added groups to the oops view
Meta Elements Added inverse and random select for metaelems
UVs Select Inverse function in the UV editor, by Juho Vepsalainen
Mesh -> Custom Properties for Mesh entities In order to give import/export script authors the ability to add properties to inidividual faces, vertices and edges in the same manner as they are able to do with ID structures three new custom data types have been added to blender for floats, integers and strings. Things to note: -Since property Layers are custom data, they are added to all verts, edges or faces at once. -Only one property layer for each unique property name may exist. In other words, you cannot have a float layer as well as an integer layer both with the same name. -No user interface for this exists at the moment. The following methods and attributes have been added to the Blender.Mesh Python module and it's object types: ->MVert/Edge/FaceSeq: addPropertyLayer(name, type) removePropertyLayer(name) renamePropertyLayer(original name, new name) properties(readonly list.) ->MVert/Edge/Face getProperty(name) setProperty(name, value) ->Mesh module PropertyTypes (readonly dictionary)
Multires
When loading multires files, clear the temporary connectivity data In add_levels, moved the call to update_levels to the beginning rather than the end. This is slightly faster, as there's one less level to update. Also fixes a bug (introduced in rev. 10836?) that made multires's add_level differ slightly from the subdivide modifier Removed two unused structs from multires Replaced one-line get_float function with a macro During add_level, move the freeing of temp data to after the update_level, so that this data isn't calculated twice Small optimization to multires based on profiling data; calculation of edge boudndaries is now cached along with multires mapping data to improve the performance of the catmull-clark code Removed an unneeded call to create the temporary data when loading files Removed an unused integer from MultiresFace Modified the vert_edge_map and vert_face_map arrays in MultiresLevel so that the data is stored only for as long as it is needed -- for adding levels and updating levels. Once the modifications are complete, the mapping data is deleted, which provides a large reduction in memory usage for a minor increase in processing time for updating levels Moved the multires vertex data from struct MultiresLevel to struct Multires. There's no longer any reason to store data seperately for each level; it was just taking up extra memory Refactored the multires update process (which handles propagating changes to other levels)
NLA Editor Snap tool in the NLA Editor, now works for the keyframes displayed for each object too. There's one case I've to check up on later, as there might be interesting conflicts
Action Editor
Snap and Mirror tools for the Action Editor, now respect NLA scaling again. I accidentally omitted the relevant code when recoding Small Action Editor feature to hopefully make keyframing quicker. Just press the IKEY in the Action Editor. Feedback on the (annoyance factor of the) popups welcome Hiding bones in the 3d-view with the (HKEY) now hides the corresponding Action Channels too I've just spent two days rewriting the Action Editor to unify its code and bring it under control again (it was 107kb, now it is around 73 kb) * This means that there are no longer separate functions for each tool for Actions and Shapekeys in the Action Editor, and also no more missing tools for either * Also, I've gotten rid of the need for those complicated, hierarchial loops used for action channels, as they were a pain to keep consistent with each other * Baking functions have been removed. See user-level-changes for more details * Reorganised and completely rewrote code in editaction.c, thus the lengthy diff User Level Changes: * For the meantime, border-selecting Action Channels has been disabled * Baking functions have been removed. As far as I have been able to find out, these were really non-functional anyway. Besides, I don't think they really belonged in editaction.c * Editing Shapekey keyframes now yields the same feature set as for those in Action Channels * There shouldn't be any major bugs left, but I might have missed something
Shader nodes Geometry node:
Front/back output This is used as a mask for determining whether you're looking at the front side or back side of a mesh, useful for blending materials, my practical need was giving different materials to the pages of a magazine: http://mke3.net/blender/etc/frontback-h264.mov Give 1.0 if it's the front side, and 0.0 if it's the back side Extended material node This is the same as the material node, but gives more available inputs and outputs, (basically just connecting up more of ShadeInput and ShadeResult to the node). I didn't want to add it to the normal simple Material node since you don't always need all that stuff, and it would make the node huge, but when you do need it, it's nice to have it
Comp nodes Invert node Inverting is something that happens all the time in a node setup, and this makes it easier. It's been possible to invert previously by adding a mix node and subtracting the input from 1.0, but it's not the best way of doing it. This node: - makes it a lot faster to set up, rather than all the clicking required with the mix node - is a lot more usable amidst a complex comp setup, when you're looking at a node tree, it's very helpful to be able to see at a glance what's going on. Using subtract for inverting is easily mixed up with other nodes in which you are actually subtracting, not inverting, and looks very similar to all the other mix nodes that usually litter a comp tree. - has options to invert the RGB channels, the Alpha channel, or both. This saves adding lots of extra nodes (separate RGBA, subtract, set alpha) when you want to do something simple like invert an alpha channel. I'd like to add this option to other nodes too. There's also a shader node version too
This speeds up the vertex group editing workflow a bit. The hotkey Ctrl-G in EditMode for Meshes and Lattices, brings up a menu giving the user options to assign/remove selected vertices to a new/the active Vertex Group. The hotkey Ctrl-Shift-G in EditMode for Meshes and Lattices, brings up a menu giving the user options to change the active Vertex Group and delete the current Vertex Group.

Okay, it's really interesting for every modders. But, I can't believe our community is about to read this text, because the hardships for the english language, above all informatic text, are surmountable with difficulty. But, enjoy it !

Sir Arthorus a écrit:

Okay, it's really interesting for every modders. But, I can't believe our community is about to read this text, because the hardships for the english language, above all informatic text, are surmountable with difficulty. But, enjoy it !

J'ai eu la flemme de traduire, sachant que c'est bourré de termes techniques qui en français n'ont aucun sens pour les noob... et dont la traduction pour les initiés est superflue.

En fait, ce sont 3 MP pour Mohawk, Blendérien notoire, et qui n'a pas besoin de traduction.
La plupart des autres 3Distes sont des Trois-Déesses-Maxistes...

Donc c'est surtout l'avis de Mohawk que j'espère. Enfin, j'ai tout installé et commence les tests pour vérifier si ce que j'ai compris est bien ce que j'espère... une future simplification des tutos et manips de DDS avec Blender.

Mike89 a écrit:

Cela présente t-il un intérêt ?

Oui, car ceci réduit le "poids" des collisions pour les formes exotiques, mais lorsque cette fonction sera optimisée, ce sera nettement mieux encore. J'ai effectué quelques tests rapides permettant en quelques minutes d'obtenir des collisions impeccables avec un modèle de Beth, pour un poids total moindre que demander de mieux

Oui, en effet Blender est en perpétuelle révolution, la version actuelle (officielle j'entend) ne permet pas encore la lecture des .dds (mais il est en effet probable que ce point sera inclus dans la prochaine version, ce qui évitera l'usage d'une version intermédiaire pouvant être parfois instable).

En ce qui concerne le plug-in de Niftools il est pour sa part en perpétuelle évolution ce qui simplifie en effet énormément les manipulations sous nifskope (en réalité il ne reste plus que quelques détails qui n'intéressent plus que des allumés comme moi) puisqu'un fichier nif exporté sous Blender peut être utilisable pratiquement tout le temps directement dans le CS. De plus dans de nombreux domaines, il est même nettement plus performant que 3DS (c'est par exemple le cas de collision bien plus légère et efficace). Le seul point légèrement à la traine semble être l'exportation des animations ainsi que le rigging qui semblent parfois poser des problèmes sur certains modèles. Mais en effet l'on peut de fait considérer que les manipulations sont maintenant nettement simplifiée, puisqu'il suffit de savoir utiliser Blender et de connaître quelques petites spécificités pour ne plus rencontrer le moindre problème.

Il est exact qu'il me faudrait remettre à jour les tutos et conseils puisque l'ensemble doit maintenant pouvoir tenir dans un simple message. Par contre je reconnais ne pas vraiment avoir eu le loisir de l'expérimenter beaucoup ces derniers temps, mais je suis les news de Niftools très régulièrement vu la vitesse à laquelle sorte les plug-ins c'est préférable

Mohawk a écrit:

Oui, en effet Blender est en perpétuelle révolution, la version actuelle (officielle j'entend) ne permet pas encore la lecture des .dds (mais il est en effet probable que ce point sera inclus dans la prochaine version, ce qui évitera l'usage d'une version intermédiaire pouvant être parfois instable).

J'ai testé la version non officielle : svn build of Blender, http://www.graphicall.org

Les textures DDS apparaissent à l'importation dans Blender..
Et à l'exportation, les DDS sont dans Nifskope... à condition qu'elles soient dans data/textures, bien sûr !
Pas mal pour un logiciel gratuit... et légalement en plus !





Demain soir, je commence... quelques essais de bâtiments. Empiler des cubes...

Je demande humblement de l'aide pour installer se plugin.
Quand je veux installer le plugin un message d'erreur apparaît.

Je ne sais que faire.(J'ai le dernière version de Blender et de Nifscope)
Merci de m'indiquer la manipulation à faire si vous la connaissez.

Comme indiqué, il suffit de télécharger PyFFI :

http://sourceforge.net/project/showfiles.php?group_id=199269

Il est vrai que ce n'est plus automatiquement précisé mais le lien se trouve avec les autres plug-in de Niftoools.

EDIT Mike (pour gagner de la place) :
C'est expliqué en anglais... j'ai eu la flemme de traduire dans le deuxième post de ce sujet :

Les explications ici : http://niftools.sourceforge.net/wiki/Blender

Oups un edit à la bourre, voici un lien vers une version 2.45 de Blender (pas la version classique) permettant à nouveau de visualiser directement vos textures dds (c'est quand même plus pratique) :

http://www.graphicall.org/builds/builds/showbuild.php?action=show&id=515

Je vous passe la dernière version du Plug-In de Niftools et le PyFFIqui va avec pour les retardataires. http://niftools.sourceforge.net/wiki/NifTools

PS. J'ai constaté que les dernières versions du plug-in améliorent très nettement la qualité des nif, puisqu'un fichiers d'origine de Beth, importé et exporté en ressort amaigri et tout aussi fonctionnel essayez vous m'en direz des nouvelles.

Mohawk a écrit:

Oups un edit à la bourre, voici un lien vers une version 2.45 de Blender (pas la version classique) permettant à nouveau de visualiser directement vos textures dds (c'est quand même plus pratique) :

http://www.graphicall.org/builds/builds/showbuild.php?action=show&id=515

Je vous passe la dernière version du Plug-In de Niftools et le PyFFIqui va avec pour les retardataires. http://niftools.sourceforge.net/wiki/NifTools

PS. J'ai constaté que les dernières versions du plug-in améliorent très nettement la qualité des nif, puisqu'un fichiers d'origine de Beth, importé et exporté en ressort amaigri et tout aussi fonctionnel essayez vous m'en direz des nouvelles.

Bonne nouvelle ! Je vois çà pour faire maigrir mes travaux...