[Edit] Open-BRF editor (v0.0.81b)

Почему опен не всегда корректно импортирует жесткие грани?Обычный брф всегда это делает правильно ,а вот опен грешит.
Я  использовал бы для импорта  обычный,но тут есть некоторые не точности.Опен и обычный видять модели в разных осях.
Может есть решение как заставить опен правильно воспринимать жесткие грани?

В настройках импорта поставь галочку напротив "ничего не делать" (Settings->On import meshes->do nothing). Если не помогает, то используй старый брф-редактор, при развороте в нужную сторону модель занимает точные координаты.

PS
С некоторыми вещами BRFEdit справляется лучше.

Spak, помогло =D
 
Добавлено: 24 Октября, 2011, 11:19

только на фрамы для вертексной не работает ,импорт статика отличный,а при добавлении фрама первый и последующие меши вообще без жестких граней =(
 
Добавлено: 24 Октября, 2011, 11:52

ну да ладно ,благо есть брфЭдит ,и чудная функция  mirror в опене

 Скачал Open-BRF editor (v0.0.67b), распаковал, нажал ехе - не запускается. У меня ХР SP3, M&B Wb v1.143  кто нибудь подскажет в чем проблема?   

v0.0.68 - http://www.mbrepository.com/file.php?id=1466

ver 0.0.68b (22 Nov 2011)

1- Added a "paste vertex colors" tool  (under "edit") to transfer vertex colors from a mesh to another.

2-  Added a "paste vertex animations" tool  (under "edit") to transfer vertex animations from a mesh to another.
    Don't expect miracles, it is very crude.
    It is based on similarity of UV coords between the mesh you copy from and the mesh you paste to.
    It works decently with some face morphs, if UV coords are coherent. Might work for other things too.

3- Added a pair of tools to make rigging "smoother", or "stiffer".
    Can be used to tune rigging a bit, especially after transferring rigging from another mesh.
     Again, use at own risk (save first, and keep result only if you like it).

4- Now the roto-translate-rotate tool can be optionally set to affect only the last selected object in a sequence of objects.
    Other objects are visible but stay fixed. Useful to align objects to each other
    (make sure to select the one which should be moving as last).

5- flags meanings added for the shaders and their requirements (thanks to [cmpxchg8b] again).

6- group export of collision body (multiple-select, right click).

7- various fixes

Additional notes:

2: An interesting experiment about this: in native, you can throw away the female face morphs (rigth-click=>discard=>vertex animation), and then copy male face morph over the now-single-frame female face. The results is more or less what native uses for females.
Be aware, when you use this tool, that timings have to be pasted separatedly, and normals (and tangent dirs) have to be recomputed.

3: "stiffer" rigging means each part of the mesh more attached to a single bone. The result is that, for example, knees become more pointy when bent. "Smoother" rigging means to smooth out weights. The results is that, for example, knees becomes more curved when bent. Works best with Hi-res meshes. Useful, for example, if you transferred rigging from a low res mesh to an higher res mesh (but in many other cases as well).

Both "make-stiffer" and "make-smoother" are very subtle, especially with hi-res meshes, and can be used multiple times in succession. Remember that with Ctrl+R you are "repeating last command". With these two tools, you might want to keep it pressed for a while sometimes.

4 is so useful when you have to combine two or more pieces together.

6 is from a request.

Пока интерес чисто академический, но со временем может стать практическим: как openbrf справляется с созданием лодов? Его можно использовать для этого, если нет возможности делать их вручную?

JoG, использовать то можно, но лучше вручную

При создании вартексной анимации получается такая вот фигня http://iscr.ru/1324666849/
кто знает что с этим делать?

При создании вартексной анимации получается такая вот фигня http://iscr.ru/1324666849/
кто знает что с этим делать?

Серёга , где то косяк с вертексами , ищи в них причину .

v0.0.69b - http://www.mbrepository.com/file.php?id=1466

ver 0.0.69b -- "many suggestions" release (3 Jan 2012)
(b is a hot-fix)
1- You can now ask for the bounding box of currently selected mesh(es)
2- Minor: mesh resizing can now take non integer percentages
3- Fix in LODding: occasional unused vertices are now automatically removed
4- "Unify vertices" now become "Clean redundant vert/pos", which also removes unused vertices
5- "Discard->Normal" tool, to merge more vertex disregarding differences in normals (for when you don't need them)
6- Custom User-defined shader can now be used (see thread)
7- [invert selection] command, under [tools] (or Ctrl+I)  <== forgot to report this one at first

v0.0.70 - http://www.mbrepository.com/file.php?id=1466

ver 0.0.70 --  (10 Jan 2012)   
1- now armor-feminizer freely customizable by users. See under [Settings]=>[On armour autofeminization] (and see notes)
2- now remembers recently opened modules (see under [Module])
3- ctrl+left and ctrl+right opens next/prev brf file in module
4- module un-referenced textures can now be moved in "_unused" folder, see [Module]=>[Show unreferenced texture files]
5- GUI: added [selected] menu, it replcates the context-menu accessible by right clicking on selected objects
6- fixes

напишите кто то mtarini что бы просмотр   в окне сделал человеческий ,а то совсем ниразу неудобно .Смотреть можно только со с центра ,когда приближаешь тогда еще страшней становится,нельзя даже модель поднять опустить . Что пкм ,что лкм ,да и зажатое колесо только  крутят модель ,а не перемещают .

Смотреть можно только со с центра ,когда приближаешь тогда еще страшней становится,нельзя даже модель поднять опустить

Есть режим "scene" (WASD+колёсико мыши вверх/вниз)

Какое то управление "не о чем"  ,это скорей для именно сцен ,что бы летать смотреть.Лучше бы сделал как во всех нормальных редакторах.
зы.конечно никто никому ,ничего не напишет ,я уверен,всех все устраивает .

Подобные замечания уже делались непосредственно автору программы, т.е. энтузиазма дублировать чужие реквесты наверное ни у кого нет. Я дискомфорта с обзором моделей не испытываю, но если это столь актуально, то готов посодействовать. Единственное, наверное стоит подождать с вопросом, т.к. подобное спрашивали буквально на днях.

v0.0.71b - http://www.mbrepository.com/file.php?id=1466

ver 0.0.71 --  (19 Jan 2012)   
1- hitboxes (linked to skeletons) extracted from data/skeletion_bodies.xml and visualized on request.
    (doens't show them? see notes!)
2- visualization of texture animations (when looking at textures objects, NOT materials objects)
3- interface polishing (mainly, added dots "..." where they belonged).

v0.0.72 - http://www.mbrepository.com/file.php?id=1466

ver 0.0.72b --   "hitbox galore" release (25 Jan 2012)
1- Lotsa new tools to ease manipulation of hitboxes -- see[tutorial]
  1.a Copy/Paste of hit-boxes (from/to Skeletons -- but also from/to Collision-Bodies)
  1.b Built-in direct editor of hit-boxes
  1.c Saving of hitboxes in .xml file
  1.d Stripping of hitboxes from a skeleton, and more
2- "Roto-translate-scale" tool can now be used to also auto-center/align meshes
3- When visualizing collision-mesh for an object X, can now overlay object X
4- Now lists bone names in skeleton Data box
5- Option to [Open Module folder], under [Module]
6- Fixes

version 0.0.72b hotfixes and retouces:
status-tooltips on direct hitbox control added, fixed layout of "material" rgb colors, a bit cleaner skeleton_data.xml produced (still sub-optimal for manual editing).

Мини-туториал по хитбоксам:

Background


What are Hit-boxes?
Hit-boxes in M&B are little balloons around each bone of a moving character used by the game to understand if something hit that part of the body, and, by extension, that character. A character, independently by the way it looks, is hit just if the ballon is. The reason is that it is much easier to check the "ballon" for collision. It is similar to the Collision Objects (which are for static meshes, however, and can be any shape).

Another use of hitboxes is in ragdolling, to avoid that, say, an arm pass though the chest when the guy is dead and is falling like a huge bag of potatoes.

Hitboxes for human and horses in vanilla Warband, visualized with OpenBRF

Why you want to edit them? Simply put, if you make a new skeleton or customize an old one, you want to make a new hitbox for it, for a more realistic fighting experience in the game.


Hit-boxes in M&B / WB

The game keeps, for each different skeleton, a set of hit-boxes (with at most one hit-box per bone). Some bone, usually smaller ones like "hands", have none, at least in vanilla. Every hitbox is shaped as a "capsule", the geometric shape you get if you cut a sphere in half and cram a cylinder of the same radius in the middle.

Now the ugly catch: Hit-boxes for skeletons, unlike basically all other content of the game (e.g. meshes, animations, materials, collision objects...), are not stored in any BRF file!

Instead, the game keeps them in a separate file, "skeleton_bodies.xml", which holds all hitboxes for all skeletons used in a module, plus a few other metadata also associated to skeleton (used for regdolling). That file is kept in "your_module/data" folder, but, if not there, the default copy is used in game "data" folder.

That's a bit of a problem for OpenBRF: hit-boxes are tightly linked to skeletons, they cannot even be visualized without one, and yet if they are edited the not the BRF file with the skeleton but this global .xml file has to be saved. That will cause some confusion, I'm sure. Important: the link between "hitboxes" (in the XML data) and skeletons (anywhere in BRF files) is by name: a hitbox will be associated with a skeleton with the same name.




How's to in OpenBRF

Visualize hitboxes

Just select the corresponding skeleton. You'll see, in the databox, a check-button called "has hit-boxes", in the "data" box, which tells you whether that skeleton has an associated set of hitboxes. If it does, you can visualize the set of hit-boxes by selecting the option inside the "view" box.

Hitboxes can be seen during animations just as well (to see how they behave during an animation).  In all cases, they can be visualized together with a "skin" (the skin can be quickly toggled on/off with space: it helps to perceive how much the hitbox fits an actual character)

When you change the current module (and at start-up), OpenBRF scans the file "skeleton_bodies.xml" and remembers all the hitboxes found there: it will use them for skeletons with the same name. OpenBRF refreshes that file with F5 (with many other things).

Remember the association is done by name: for example, if you rename a skeleton, it can lose (or gain) a hitbox set.


Edit all hitboxes manually

Anything you need to do with hitboxes of your mod, you can do it manually, by opening the file "skeleton_bodies.xml" in a text editor (copy the one from <game>/data folder into your <module>/data folder to start with). The file is a XML so it's should not be too difficult to figure out and edit.

To visualize that what you did made sense, you can keep OpenBRF open: just save the XML file and refresh OpenBRF with F5: the hitboxes will be updated.

This is the "slow but sure" way: you can add, delete, edit any hitbox assocaited to any skeleton. It is just not very intuitive to do. That's the emergency way to do anything (without OpenBRF).


WYSIWYG editing hit-boxes within OpenBRF

- Select the skeleton with the same name as the hitbox.
- Click on any bone on the list.
- You can now use the controls to thicken, elongate, move, rotate the hitbox for that bone. You can also activate/deactivate that hitbox (not all bones have one). You can make the hitbox symmetric (e.g. you edit the left leg, and use that to update the right leg so to match). And so on: experiment with the controls, they should be  easy to understand with very little tries.
- Hint: while you edit, it helps to turn the skin on and off (keyboard shortcut is space) to see that your hitbox is right.


Save a modified hit-box

Now the tricky part: when you edited a hitbox from OpenBRF, a "(**)" -- double * -- will appear in the OpenBRF windows title: this tells you that you have unsaved changes in the skeleton metadata. It's of no use to just "save": that saves the BRF file with the skeleton and hitboxes are not kept there. Instead, you need the command, in "Module" menu, to "Save module Hit-Boxes for all skeletons".

Don't worry: you will be prompted that you must save your changes, and offered to do so, whenever you are about to lose them (e.g. you try to quit OpenBRF, or open another module, etc).

(hint: a quick way to discard your edits, if you need to do so, is to refresh the module with F5: that reloads the current "skeleton_bodies.xml")

Remeber you never save just a single hitbox: you save either all hit-boxes of a module or none.

Caveat: when OpenBRF saves the hitboxes, it saves a "skeleton_bodies.xml" which is looks very different from the one found in native (a backup is done). This is because XML files can assume many different form (indentation etc). In particular, OpenBRF unfortunately scrables the order of "attributes" inside nodes. The game does not care at all, and works correctly. But manual edit of that file get be more difficult, I'm afraid.


Add a hit-box set to a new skeleton

When you create a new skeleton (e.g. copy, paste and rename an existing skeleton, or import it), it will have no associated hitbox. Unfortunately, you cannot just add hitboxes to its bones, one by one, because there is no way OpenBRF would no the rest of the metadata necessary to be saved together with the hitbox.

Instead, you have to transfer an existing hitBox-set from another skeleton.

How to do that:
1) select origin (a skeleton with hitbox), [edit]->[copy hitbox]
2) select destination, [edit]->[paste hitbox].

The two skeletons must share the same number of bones.


More on copying and pasting hitboxes

After you copied a hitbox (step 1 above), you can just paste it (ctrl+C) (instead of pasting an hitbox over the skeleton).

That creates a static collision object instead, made of capsules (plus "placeholders" for bones without hitboxes).

That "collision object" can in turn be copied and pasted "as a hitbox" over a skeleton (again, select it, [edit]=>[copy hitbox]).

Naturally, before you do that, you can also edit the "collision object" as normal, e.g. enlarge it, or manually edit its many numbers, or export it and reimport it, etc.

The two ways to transfer a hitbox from a skeleton to another are a bit different. If you go though the static collision, the position if space are fixed, indendent of the bone positions of the destination skeleton.  There are cases when either of the two things is useful, so I kept both ways. Can you see why?



Minor: remove a hitbox from the module

I.e. remove it from skeleton-bodies.xml

You can select the skeleton with the same name, right click, [Remove hitboxes]. Remember you are not actually doing anything to the skeleton. The association is done by name: if you remove the hitbox from a skeleton called "skel_giant", you are just deleting the hitbox called "skel_giant" (e.g. another "skel_giant" sitting in another unrelated BRF file will now be without hitbox).

When you save hitboxes, OpenBrf tells you all the ones he is going to save.

Small detail: if you want to remove one, but have no skeleton named that way, you can create a skeleton with that name just to delete it.

v0.0.73 - http://www.mbrepository.com/file.php?id=1466

ver 0.0.73 --   (27 Jan 2012)   
1- New [Paste in mesh] command (matching LODs) under [edit]
2- Now displays/edits "for_ragdolls_only" flag in hit-boxes
3- Can now "Copy rigging" into a mesh from a skeleton too (not only from a rigged mesh).
4- Minor upgrades and fixes.

ver 0.0.73c --   (27 Jan 2012)    [additional notes]
+b and +c versions: hot-fixes.

Хлопцы ,хто там в теме ,автор будет  фиксить импорт с жесткими ребрами ? А то  жуть как надо ,иногда такой бардак с жёсткостью  выходит ,что мама не горюй.Обычный брф для этого использовать ну очень не с руки .Может подскажет  кто автору пускай уделит этому внимание.
 
Добавлено: 29 Января, 2012, 16:54

о ,кажись понял как с этим бороцо ,да и припоминаю  кажись , раньше это советовал Спак .В настройках-импорта меша  галку поставить без изменения ( ну или как то так) .Интересно то что раньше это не работало у меня ,сейчас напротив.В общем поглядим дальше ,сможет он импортировать другие модели.

ver 0.0.74 --   (2 Feb 2012)
1- A [reskeletonize] tool, to adapt animations to skeletons with a different number (or scrambled) bones
2- A [Transform UV] tool, to scale/translate all UV coordrinates. Useful for when you unify textures in one sheet
3- New mechanism: now OpenBRF will optionally use Module-specific reference file. See info

Помогите!
Попытался через brf перегнать текстурку головы из .brf в .obj.
Но прога не сохраняет текстуру в нужном формате.
Кто нибудь напишите нубу как через BRF editor перегнать в .obj

никак ,потому что брф это не ддс ,а ддс не брф

смертник, О

Мм...  Я перепутал - нужна не текстурка, а модель головы (извиняюсь )
Распишусь детальнее.
Для работы на Wings (а именно создания оружки и доспехов, в моем случае шлема) на форуме увидел, что нужна модель головы (meshes_face_gen.brf). Для перекачки из .brf в .obj в том же топике увидел, что нужно скачать BRF editor.
И сама собственно проблема описана выше.

Вигго, ну вот там и спроси,к стати ответы на твои вопросы есть в темах с вингсом и работай с 3D