|
| Author |
Message |
|
rickyparkar
|
Posted: Tue Oct 26, 2010 3:14 am |
|
| Gamer Lv:0 Exp:0% |
 |
Joined: Tue Oct 26, 2010 2:16 am Posts: 3
|
|
|
|
btw, thanks for answerin' Mah question TP! I appreciate it!
Now to go about editing a model, see if I can't make my own pretty Orcs.
|
|
| Top |
|
 |
|
Happy Monster's News
|
|
|
|
|
|
|
|
 |
|
paul_steele
|
Posted: Tue Oct 26, 2010 4:56 am |
|
| Gamer Lv:0 Exp:5% |
 |
Joined: Tue Oct 26, 2010 3:59 am Posts: 5
|
|
|
|
Can't that be done already? What I do is use the Layers window to hide everything but the body, and that's pretty much it.
Hum. Well. Ok. That pretty much solves everything, didn't think Using the Edit mesh on two groups would work for some reason, so I didn't even try. I was indeed missing something huge. Thanks, the programme is now complete to my taste, I really can't think of anything else to inquire on.
Although I know now my questions and suggestions were a bit off, thanks for detailing all the geoset management,I learned some stuff.
Cheers.
|
|
| Top |
|
 |
|
lewistalbert5
|
Posted: Tue Oct 26, 2010 8:05 am |
|
| Gamer Lv:0 Exp:0% |
 |
Joined: Fri Oct 22, 2010 12:40 pm Posts: 3
|
|
|
|
A note about seams:
Seams occur at the junction between two geosets when they have different numbers of vertices. For example, if you only subdivide geoset 0 you'll get a seam on the back (that's 1501), forearms (401), and legs (1301), and maybe boots too (501). I might eventually be able to fix that, but there is also currently a workaround. What I recommend is to leave as many geosets on as possible (you can even use the bIncreaseAllGeosets = true option to hit them all), but then restrict the range as much as possible using xmin, etc. If for example you are just doing breasts, it won't hurt at all to hit effect geosets if you make your range just fit the breasts exactly, and you will be pretty much guaranteed not to get any seams. _________________ Skins: Links:
|
|
| Top |
|
 |
|
krdzali
|
Posted: Tue Oct 26, 2010 8:55 am |
|
| Gamer Lv:0 Exp:0% |
 |
Joined: Tue Oct 26, 2010 7:58 am Posts: 4
|
|
|
|
Hello again, I spent some time on the new version and a couple of things really stand out, first the texture option which is very nice, the normals (I don't touch this but I can see how it can be useful) and the grouping. The grouping is really great it makes it really easier to juggle with layers and display of different parts of the model.
However, there is a problem there, for me, compared to the previous version, and it somewhat connects with this concern ;
Yeah, this thing gets everyone. I think I just need to make the tool not subdivide the edges of geosets. Unfortunately that won't be able to fix the seams of existing models, but it should make new edits in the future easier.
It involves intersections. The problem I described here is avoidable if it is possible to increase the polycount of the concerned parts (robe, capes), I guess it is, by allowing them to be enhanced using geosetIDs in the .ini. An option that would prevent edges from being subdivided would help, but in my case I like to make changes that smooth the mesh in between linked geosets (like I did for my troll), I'd rather fix that by enhancing the clothes so they fit the body well. I was just seeking confirmation that it is possible to increase the polycount of cape and robe geosets given that you know the ID.
Now for this version, the grouping is nice as I said, no more 5 minute long element hiding, but it causes other problems. For instance the different body parts belong to different groups, so if you want to modify an entire arm smoothly there is going to be trouble, as you won't be able to move juxtaposed vertices on the edges to maintain coherence, and jumping from a mesh to another won't be very fun. I haven't found anyway of compensating this in max, attaching/detaching renders the reinjection of the .obj impossible (I restaured the original groups before exporting ofc, with the same names, it didn't work either with previous procedures)
The only solution would be, if it's even possible, to have an command that allows you to "merge" specified geosets during the extraction so they end up in the same group, for example a "body" geoset that would include all skin sections. Now I don't know how much work that involves, and if it only concerns me it's not worth it, but if there is really no workaround possible (maybe I'm missing something huge) and it's not a pain in the arse to implement I reckon it'd be a nice option as it would make the whole remodeling interface near perfect. I don't want to seem ungrateful of course, I made it clear that I thought this programme was truly awesome and the .ini commands I settle with swiftly.
This is all I can think of, I hope it's somewhat constructive.
And just a little question, is there a simple way to get all geosetIDs on a model?
|
|
| Top |
|
 |
|
baishacodu
|
Posted: Tue Oct 26, 2010 10:05 am |
|
 |
| Gamer Lv:0 Exp:0% |
 |
Joined: Tue Oct 26, 2010 9:07 am Posts: 3
|
|
|
|
| Top |
|
 |
|
Happy Monster's News
|
|
|
|
|
|
|
|
 |
|
qmqueenmail
|
Posted: Tue Oct 26, 2010 10:55 am |
|
| Gamer Lv:0 Exp:5% |
 |
Joined: Tue Oct 26, 2010 9:58 am Posts: 7
|
|
|
|
Oh wait, a black screen when you load the game? That's a common error, and I don't know the cause. There is no ETA on a fix, sorry. _________________ Skins: Links:
|
|
| Top |
|
 |
|
michaelstorch
|
Posted: Tue Oct 26, 2010 11:13 am |
|
| Gamer Lv:0 Exp:0% |
 |
Joined: Tue Oct 26, 2010 10:16 am Posts: 3
|
|
|
|
forra wrote: I did a test run on the alpha thingie with human female and the OBJ output was fine, but the M2 output is missing the lower jaw. It's just plain gone and looks like that undead male face, and it is creeping me the fuck out. Is this a bug or did I miss something?!
If you are talking about viewing human females in WMV, that is a WMV bug that happens even on unedited models. _________________ Skins: Links:
|
|
| Top |
|
 |
|
austinecommerceconversionrate
|
Posted: Tue Oct 26, 2010 11:47 am |
|
 |
| Gamer Lv:0 Exp:5% |
 |
Joined: Tue Oct 19, 2010 12:08 am Posts: 6
|
|
|
|
Trollpaxton wrote: Yup. Were you able to use Densetsu's model edits prior to 302?
Yeah.
|
|
| Top |
|
 |
|
tamimsaif
|
Posted: Tue Oct 26, 2010 2:04 pm |
|
| Gamer Lv:0 Exp:0% |
 |
Joined: Wed Oct 20, 2010 4:23 am Posts: 3
|
|
|
|
tancients wrote: With the anim files finally seperate, maybe there is the possibility that one can swap them around or edit them (if we find an application/converter for them) as fit as well. So despite the change causing a hitch and model overhaul, I think it might come out to be a good one in the long run.
I'm pulling my hair out over these files. It seems that the files aren't self contained animations, but rather just blocks of animation data. The M2 files still contain the animation headers. So for example, lets say a dance animation's data has been exported to an .anim file. The M2 file still has the animation's header internally, and will expect the length of the .anim file to exactly match what it thinks it's length is. If it isn't you're likely to crash. So, I doubt you'll be able to swap animations that way.
snaketrap wrote: I've never been able to get any of the Hi-res stuff to work. As I've reported in the past, I've always just gotten the black screen. I tested this new patch and it seems to work. My NE Warrior is visible and playable,a nd I can't find any glitches or errors.
That helps a lot, and is very interesting. Thanks! _________________ Skins: Links:
|
|
| Top |
|
 |
|
onlineslotmachines
|
Posted: Tue Oct 26, 2010 11:47 pm |
|
| Gamer Lv:0 Exp:0% |
 |
Joined: Tue Oct 26, 2010 10:49 pm Posts: 3
|
|
|
yeah please post this tool... very interested in making some mods if at all possible thanks in advance 
|
|
| Top |
|
 |
|
|