Spring RTS Engine

FLOZi, you most certainly are smoothing based on vertex normal angles, if you're using tools like the ones I do. I am using UVMapper Pro, which is adjusting smoothing by vertex angles when I have translated the file to OBJ prior to final export from Rhino as 3DS. My workflow's a little bit different than yours, is all. Don't assume that just because I'm using 3DS as the final file format, that I'm using 3DS smoothing groups, because I don't. Now, that said, when everything's gone through the hoops, I tend to lose smoothing if I am not really very anal about keeping pieces separated first, so I've just gotten to the point where I expect to do do final smoothing in UpSpring anyhow, frankly.

At any rate, I have not seen any problems like this, Smoth, if I scale, then immediately save and re-open the file (er, I always do that because of the way UpSpring handles scaling) and then re-apply vertex smoothing. Tell ya what, send me the file and I'll take a look...

You shouldnt have todo that just to scale it correctly in upspring.

"Shouldn't have to" and "should do, if you want correct results" aren't the same thing here. Look, I never have any serious problems getting the results I want, and these are the methods I use.

Argh is right, upspring scaling is downright weird.

the last step before my model is put into my objects3d folder is to do the vertex nomalising.

Argh wrote:"Shouldn't have to" and "should do, if you want correct results" aren't the same thing here. Look, I never have any serious problems getting the results I want, and these are the methods I use.

Imagine fi in photoshop whenever you scaled a selection you had togo into a menu and select some option or itd mess up the colours. Imagine the controversy.

I'd consider this a bug in upspring, not a UI quirk of upspring.

*sighs* You can't pre-pose, you can't scale stuff... Were it not the only application capable of putting an s3o together, I would kill it. With fire.

interesting, ok, so if you PRESCALE your parts you are fine but scaling changes things...

the hips down are prescaled the torso, arms, head, sheild and gun are scaled in upspring... notice the difference:

Did you hit Apply transform after scaling?

Argh wrote:FLOZi, you most certainly are smoothing based on vertex normal angles, if you're using tools like the ones I do. I am using UVMapper Pro, which is adjusting smoothing by vertex angles when I have translated the file to OBJ prior to final export from Rhino as 3DS. My workflow's a little bit different than yours, is all. Don't assume that just because I'm using 3DS as the final file format, that I'm using 3DS smoothing groups, because I don't. Now, that said, when everything's gone through the hoops, I tend to lose smoothing if I am not really very anal about keeping pieces separated first, so I've just gotten to the point where I expect to do do final smoothing in UpSpring anyhow, frankly.

At any rate, I have not seen any problems like this, Smoth, if I scale, then immediately save and re-open the file (er, I always do that because of the way UpSpring handles scaling) and then re-apply vertex smoothing. Tell ya what, send me the file and I'll take a look...

I'm not using tools like you are.

argh the problem is that the way it recalculates the normals is funky and yeilds undesired results. By having the peices in the proper size and avoiding scaling I avoid the normals thing altogether. However, I shouldn't have to hit that button after I scale. My problem is simply that. It is a bug.

Yeah, I can see uses for that recalculate normals button but it yeilds undesired results when you have mixed geomitry.

what's that? without scaling the model all is well?!??!


(click for larger image)

OH LOOK AT THAT THE MODEL IS FINE! again, scaling is broken.

I've added a request for a renormalize normals function to the Upspring thread, I figure that's the issue here.