Welcome to the TWC Wiki! You are not logged in. Please log in to the Wiki to vote in polls, change skin preferences, or edit pages. See HERE for details of how to LOG IN.

Model flexi m in RTW

From TWC Wiki
Jump to navigationJump to search

The designation model_flexi_m allows RTW battle-map unit cas files to use a very limited amount of multi-weighted vertexes. Some vanilla RTW have multi-weighted sections typically on shoulder sections. The older cas loading scripts for 3dsMax do not handle these sections and simply omit them from the model. IWTE will convert this type of cas to dae and allow similar cas files to be created, however the game will only handle a very limited amount of multi-weighting so you could not import a typical M2TW mesh unit with complex weighting directly into RTW! The feature also only works properly in-game if the model is scaled 1.0, strat models that are normally scaled down x0.7 need to be reduced in size so they can be used at 1.0 scale.

The details below also apply to M2TW strat character models, but due to the small visible size and the scaling issue the feature is not useful.

Rome Remastered allows full use of vertexes weighted across two bones at lod0 level with the exception of primary/secondary weapons which can only be assigned to one bone for the entire mesh.

Creating a simple Multi-weighted Section

Contrary to popular belief RTW .cas files allow a limited amount of vertexes to be assigned with weighting to two bones per vertex, for more details about the limitation see the Cas Models page. Also contrary to popular belief bone positions can be moved as well as rotated in RTW animations, however, the multi-weighting feature and bone movement do not work well together.

The limit of 100 vertexes in a multi-weighted .cas section appears to be a hard coded limit for RTW, IWTE will currently try and split any such group into separate sections. It is highly recommended that you only attempt to have a few multi-weighted vertexes, such as having a ring of 50/50 weighted vertexes at the Upperarm/Torso junction to smooth out shoulder movement. Cas files with multi-weighting must use the model_flexi_m setting to work in-game. They should work in-game for RTW unit models and for M2TW strat models, however, the .cas models created with this are unlikely to convert/load successfully with any tool other than IWTE currently. Other existing tools do not export the multi-weighted sections from vanilla models.

As an example of how you could easily add some transitional weighting to an RTW unit model, you could add or re-weight verts between the area assigned to the pelvis and the area assigned to the abs bones. If there is already a wide gap in this area you could add more verts, as you want as few verts that need the multi-weighting as possible, first convert the mesh in that area from tri's to quads:

Mesh from tris to quads

If you then 'Bisect' this area or otherwise split the edges and then re-triangulate and view in 'Weight Paint' mode, you will see that Blender has assigned the new verts proportionately between the abs and pelvis:

Bisected area with proportional weighting

The triangles between the two arrows, the ring of verts attached wholly to the Abs bone, and the ring of verts attached wholly to the Pelvis bone will have to be included in a separate 'type 3' section within the .cas file. IWTE will do this for you. DO NOT attempt to split the area into a separate group yourself, this will only result in unnecessary seams and additional 'named' groups which cause other problems with the game limits. Also please see the section on limitation for this, the shared verts must only be between direct parent/child bones so, Pelvis/Abs works, Pelvis/Torso will not work.

Multi-weighted sections and bone movement anims

The video here shows some effects of deliberately exaggerated bone movements during animations, where the unit model also has multi-weighted sections.

Game-versus-blender-movement.jpg

In the above picture the sections of the shoulder pad that are partially weighted to Torso/Upperarm show as stretching evenly between the two bones when the Upperam bone is moved away in Blender. (similarly for the head section which has been partially weighted to the torso) In game although these sections remain at the correct angle all the vertexes with the Upperarm as child bone have moved with it in a way proportional to the original distance between the bones, and not proportional to the new extended distance. The inset in the below picture shows what is effectively happening with the sections partially weighted to the upperarm bone following it and ignoring the extended distance

Multi-weight and bone move.jpg

Multi-weighted sections do however behave as expected where the bones are rotated. This poor chap has had his chin and face partially weighted to his torso, as you can see the effect in game is the same as shown in Blender:

Game-versus-blender-rotate.jpg

YOU can help us improve this Wiki! ~ Look for ways to help and editing advice. ~ If you need further advice, please post here.