First I want to start with an ingame screenshot. You can see tht the weapon isn't being hold correctly. There are 2 reasons why it is like that: 1. Player model is very, very low poly and second, no bones for the player model part. (Ca3DE uses HL system, a weapon for players, a first person view model and one thats lying on he ground)
Ok, now theres a problem and I cant do anything against it... Look at the bones for the player model...
So theres no possibility for changing the way the weapon is being grabbed. next big problem: No good animations possible.... And if there were real bones for hands, you would have to do every animation 2 times because the player model uses another bone structure than the first person model.
OK, now to the first person view model... This one looks ok, only thing that could be easier is are the names of the bones of the weapons. It seems to me like their functions are hard-coded... Maybe global same names like "tag_weapon","tag_flash" and "tag_magazine" would make it easier. (but thats not really important, just a question of making everything easier).
And here the names of the weapon bones
Another rather funny thing is the bones structure of player models, have a look at the hands! I cant understand the functions of this bone structure while shooting etc... If it is just for animations like hand signs etc then its quite *****
And what does this tell us?
Ca3DE uses outdated bone structures for the player models (weapons) and the player models (the figures).
My personal suggestions/comment:
1. Implent a new bone structure for player models, like
(Problem: I think all player anims would have to be redone )
2. Get rid of this ancient model system. Its complicated and not quite useful. You dont really save much fps with it, its not worth the effort. 3 different views with 3 different types of collections of aniamtions...
Personally, I worked with the system that Quake 3 uses... 1 model thats lying on the ground and is displayed at the player and another model, the first person view model. Both models have got the same core bones and the first person view aniamtions are automatically seen in 3rd person view too. Thats much less work and makes everything as simple as possible.
Modern player model...
3. Ca3DE needs new player models so the new bone system makes sense... New hands are on the way (thx Kai)
But... That's just my personal opinion. I believe that there will be a lot of people who dont like my suggestions.... Maybe I just didnt understand the Ca3DE bones system and this thread it worthless... Let's talk about it!
Well, you're right, the current bone system etc. is complicated.
With regards to combining the player model with the _p model of a new weapon, I'd suggest to look at the existing player skeletons and _p weapon skeletons for learning how they "overlap" each other to get the desired effect:
Both the player and _p models have the same "root" skeleton (the names of the bones must match!), and the _p weapon model can then extend its duplicated/overlapping skeleton to account for bones that are specific to the weapon.
Personally, I'd be happy to introduce another or new model system to Ca3DE (one that can also deal with animations like the current) rather sooner than later.
However, I've not yet found an adequate replacement for animated mdls so far.
Any suggestions and insights are highly welcome.
I dont really know any normal format that saves model&animation, just one but its a normal format for a specific modelling prog... The prob really is the file containing the animations...
@ Weapons system...
The whole structure isnt that good because of the reason that all the animations have to be created 3 times...
Call of Duty (Quake 3) uses just 2 files.
First, like I already explained earlier,a world model that lies on the ground and is seen in 3rd person view etc
Then the 2. file is the first person model and all the animations created there can be seen in 1rst person AND 3rd Person view!
The would be the solution for weapons I like.
@Player Models... I think we should try to get a high poly (< 1000 ) model and then we should use the ca3de structure but combined with good bones for hands... Hm...
Very good question indeed.Stormtrooper wrote:Why not using the smd files as they are? Is it possible?
I was wondering for a while about that too, and have not yet found an answer. Maybe it's just for "convenience stuff", like having the bones matched when a player and a _p weapon model are combined. (Note that this is an example for a very powerful concept that is not covered by bare smd files alone.) If however that was all that mdl files have over smds, it would be reasonably easy and straightforward to either use smd directly, or develop an own format from it.
My intention is to look closely at the new HL2 models as soon as I find some time, and if they can be used directly in their "source" form (xsi, smd, etc.). That would be a great step.
As always, any input and suggestions are welcome.
https://sourceforge.net/projects/dotxsi4max/ in fact heres the link to an open source version for max
http://www.xsibase.com/tools/plugins.php?detail=418 heres a maya5 one
and I just read on a lightwave forum that someone is working on a plugin.
Oh yeah one tip I have is to make it so we dont have compile the model and then the animation files into one file. Its more convenient if you change your anims to not have to recompile every time, just delete the old anim file and drop in the new one.
Users browsing this forum: Bing [Bot] and 3 guests