man you have way too many polies there. 58k is way too much, even for sc2, the limit is 8k (based on thor) you should try reducing some. You should try a cap of 20k atleast since you want to cover the screen.
How did you go about importing and exporting those Warcraft III models into Starcraft II cleanly, if I might ask? (The ones in the video in the news post.) Don't let my question delay your update, that update sounds amazing, just curious. :3
he used profet's blizzimporter and reskinned the models.
In my opinion, modeling wise glitching's Vivi is better than kanaru's. It has better proportions and has better use of polies. However, Kanaru's has better textures and a better render. Also, kanaru had some advantage in the contest as his model was shown in the news before.
the thing is that the net traffic is not only recieving the WASD events, but also the local camera yaw(angle). This makes the traffic become quite heavy.
Some solutions are: play all games in normal speed instead of fast or faster, reduce the number of hotkeys used for the GUI and system, etc.
It only supports FK animations at the moment. Upon reading the Warcraft III Art Tools documentation, it appears you need to have rotations every 90 degrees or less of rotation. This could be the problem encountered by most models that don't animate properly. I believe BlinkBoy from THW has figured out a solution to this problem so you don't need rotations every 90 degrees (think it introduces more keyframes between rotations if it detects some keyframes are more than 90 degrees) but for now the exporter requires rotations every 90 degrees or less. As far as I know there are no problems with simple scalings/translations. Just remember the rotation rule. Hopefully in future updates I can use BlinkBoy's solution so those kind of rotation restrictions aren't mandatory, although I think it's good animating practice to include those extra rotation keyframes anyway.
wait a sec, if you refere to TCB rotations having troubles after 90º. That's not really the problem you think, the problem actually is if the z axi passes 90º or x and y axis pass 180º. This problem has nothing to do with gimbal-lock but with the smooth-quaternion-interpolation function (squad) used by the game. To fix the problem, you must add extra keys whenever you find it happening between 2 quaternions.
By the way, about importing TCB. I found a trick to restore a case
1º if the in and out tangents are near the same as the key, it means the continuity is about 0.0
with this you'll restore 90% of the keys with near exact accurity, since blizzard models only have modifications in continuity, very few have keys with bias and tension different than 25.0
by the way the function I sent you uses Non-Max TCB. You must convert MAX TCB into Normal TCB by resting 25.0 and dividing by 25 after. Example NormalTension = (MaxTension-25.0)/25.0
Blizzard has always used 1000 FPS in their model files, from MDX's to M2's and now with M3's. You don't have to use 1000 FPS, you can import and export at different FPS's. The option is there. .
as I said, the .max scenes (Art Tool's samples) were in 30 fps, but the art tools exported them as 1000.
The reason why there are so many frames is likely due to how the .m3 exporter works on Blizzard's side. It might be converting a standard 30fps animation into 1000fps, perhaps to allow slowing down/ speeding up of animations using the editor without getting choppiness. I can't say if they're actually animating at 1000fps in their source files, but that's what we'll have to deal with for now.
yeah same deal with wc3, if you look at their wc3 scenes in the Art Tools sample, they were in 30 fps. I also think, the Star Tools take care of the rescaling as well as conversion of IK to FK.
0
if you do a simple bunker rush, they'll keep suiciding their units into them.
0
milkshape does not have what it takes for modeling in sc2. Blender looks to be a better option.
0
well, i'm willing to do so ;).
0
Teh answer: MODS. You could make a wc3 models mod and people would justimplement the mod in their maps.
0
decals are supported by the exporter already. Same with team color
0
man you have way too many polies there. 58k is way too much, even for sc2, the limit is 8k (based on thor) you should try reducing some. You should try a cap of 20k atleast since you want to cover the screen.
0
he used profet's blizzimporter and reskinned the models.
0
In my opinion, modeling wise glitching's Vivi is better than kanaru's. It has better proportions and has better use of polies. However, Kanaru's has better textures and a better render. Also, kanaru had some advantage in the contest as his model was shown in the news before.
0
the thing is that the net traffic is not only recieving the WASD events, but also the local camera yaw(angle). This makes the traffic become quite heavy.
Some solutions are: play all games in normal speed instead of fast or faster, reduce the number of hotkeys used for the GUI and system, etc.
0
wait a sec, if you refere to TCB rotations having troubles after 90º. That's not really the problem you think, the problem actually is if the z axi passes 90º or x and y axis pass 180º. This problem has nothing to do with gimbal-lock but with the smooth-quaternion-interpolation function (squad) used by the game. To fix the problem, you must add extra keys whenever you find it happening between 2 quaternions.
By the way, about importing TCB. I found a trick to restore a case
1º if the in and out tangents are near the same as the key, it means the continuity is about 0.0
with this you'll restore 90% of the keys with near exact accurity, since blizzard models only have modifications in continuity, very few have keys with bias and tension different than 25.0
by the way the function I sent you uses Non-Max TCB. You must convert MAX TCB into Normal TCB by resting 25.0 and dividing by 25 after. Example NormalTension = (MaxTension-25.0)/25.0
0
as I said, the .max scenes (Art Tool's samples) were in 30 fps, but the art tools exported them as 1000.
0
yeah same deal with wc3, if you look at their wc3 scenes in the Art Tools sample, they were in 30 fps. I also think, the Star Tools take care of the rescaling as well as conversion of IK to FK.
0
well do the process that the IK snapper does manually, which is snap IK poses for some frames, then erase the IK Solvers.
The option can be found in the motion panel, select a solver and click IK/FK Snap.
0
explain? I have animated many wc3 models that way
0
well IK can be converted to FK easilly. Use the NeoDex tool: IK Snapper for bone chains or 3dmaxy's IK2FK converter in wc3campaigns.