^floziKDR_11k wrote:3ds is a horrible format, even MAX users hate it because it unwelds the vertices along UV seams. Also not every 3d application handles every format well.
Upspring 1.54
Moderator: Moderators
Yes, there was a big change in 1.4x iirc that basically made everything welded.smoth wrote:Jc, I was using 1.3.. it could be possible that I missed the version that changed it.
I am about to head out for an exam but yeah... the object shows up as solid black now... no idea why. I'll look into it as soon as I can but I cannot promise it would be tonight. I am desperate need of sleep.
Small fix: There was a bug in the rotation tool to rotate object in one of the views.
http://user.supradigital.org/jcnossen/U ... r-1.51.exe
http://user.supradigital.org/jcnossen/U ... r-1.51.exe
Oh, and um... one last teeny-tiny thing. If you put a point object in and move it, UpSpring crashes, and corrupts the file, so that it's trashed forever.
Thankfully, I back everything up, but I figured you might wanna know that
Even with that little issue... meh... this RULES. Of all the things about Spring, having to either have welding or abandon it entirely has been one of my biggest pet peeves. Not to mention how object origins are all properly left tied to the root, so building rotational points, etc., is unbelievably easy, and all the other little stuff. I'm in modeling heaven!
Thankfully, I back everything up, but I figured you might wanna know that

Even with that little issue... meh... this RULES. Of all the things about Spring, having to either have welding or abandon it entirely has been one of my biggest pet peeves. Not to mention how object origins are all properly left tied to the root, so building rotational points, etc., is unbelievably easy, and all the other little stuff. I'm in modeling heaven!
That was pissin me off a lot. Good thing its fixed, or at least workin for me. 3DS has a bunch of options and stuff now, thats okay. Argh, I don't save "backups" but I do keep all of the original files, before they are modified. Example, the Wings file of a model, the 3DS file, and the s3o. Another example (saved my ass many times) was keeping the original file of the texture, without the transparency stuff.
I don't have any gripes or glitches.. Yet.
Well, have fun in Heaven, Argh. I'm expecting something groundbreaking in a year or two
edit: I forgot why I came here... Why does UpSpring render textures so ugly...?
edit2: Never mind, its still screwin up and deleting my stuff, but save as seemed to work...
Damn, damn, damn, damn! I wanted to finish the gunship tonight..
I need to work as fast as possible... 
I don't have any gripes or glitches.. Yet.
Well, have fun in Heaven, Argh. I'm expecting something groundbreaking in a year or two

edit: I forgot why I came here... Why does UpSpring render textures so ugly...?
edit2: Never mind, its still screwin up and deleting my stuff, but save as seemed to work...

Damn, damn, damn, damn! I wanted to finish the gunship tonight..


I really haven't had any problems exporting 3DS from Rhino, I don't see problems with my smoothing groups at all.
Are you using 3DS itself? Or just Wings? If just Wings... I'd export as OBJ, import into UVMapper Pro, correctly set up the splits and welds, and then export back to Wings, finally exporting as 3DS. I use a somewhat similar workflow with Rhino, and that works great.
Are you using 3DS itself? Or just Wings? If just Wings... I'd export as OBJ, import into UVMapper Pro, correctly set up the splits and welds, and then export back to Wings, finally exporting as 3DS. I use a somewhat similar workflow with Rhino, and that works great.
or the obj could just be fixed and I can continue my work.
3ds does weird things to models. I used 3dsmax once to see if it was just wings. 3ds breaks my weilds I do not wish to use uvmapper pro, I hate the program and it adds another step into my work. Seriously, I understand you are fine with 3ds but I do not like what that format does to my models.
OBJ import is broken, don't dismiss my statement as legitimate because you are fine with 3ds files. I AM NOT. I did not do any modeling tonight and I am waiting on a fix so I can go back to work.
3ds does weird things to models. I used 3dsmax once to see if it was just wings. 3ds breaks my weilds I do not wish to use uvmapper pro, I hate the program and it adds another step into my work. Seriously, I understand you are fine with 3ds but I do not like what that format does to my models.
OBJ import is broken, don't dismiss my statement as legitimate because you are fine with 3ds files. I AM NOT. I did not do any modeling tonight and I am waiting on a fix so I can go back to work.
That is why I had to clone base (or any other empty object) when setting firepoints up on that peewee remake. Doesn't crash then.Argh wrote:Oh, and um... one last teeny-tiny thing. If you put a point object in and move it, UpSpring crashes, and corrupts the file, so that it's trashed forever.
That is why I tried to use 3ds which apparently randomly breaks smoothing groups.smoth wrote:Jc, I was using 1.3.. it could be possible that I missed the version that changed it.
I am about to head out for an exam but yeah... the object shows up as solid black now... no idea why. I'll look into it as soon as I can but I cannot promise it would be tonight. I am desperate need of sleep.
It's all black when lightning is turned on in upspring and I can only assume that it behaves the same in spring. Also, smoothing groups are ignored as it seems for the OBJ format in general. So a fix would be handy.
It only crashes for me with origin-move on an empty object. Anyway I rechecked my code to handle objects without geometry and hopefully it works out correctly now.Oh, and um... one last teeny-tiny thing. If you put a point object in and move it, UpSpring crashes, and corrupts the file, so that it's trashed forever.
Also fixed OBJ loading
http://user.supradigital.org/jcnossen/U ... r-1.52.exe
Hmm I didn't know that. Yes I already noticed that optimize pushes the filesize down by >50% but didn't exactly know what happened. Good work anyway.It is tesselating though, the 3DS format can only store triangles
Never really realized that using 3ds can speed things up a lot, no more exporting as obj and importing/naming them in upspring one by one.
edit:
There are issues with the *lighting (yes lighting!) now.
The model was only fully lit when it's tiny, after scaling it up it became bady lit. Also when I hide the grid, the model becomes entirely black, unless *lighting is disabled.
Last edited by rattle on 20 Mar 2007, 17:13, edited 1 time in total.
You mean "lighting", not "lightning", yes? And is this true if you back away with the camera (i.e., zoom out) or only when you remain at default zoom? This is probably a very simple issue about how far away the lightsource that is tied to the camera is- it's probably too close to the camera right now.
Jc, how hard would it be to do these two things:
1. add an option in Upswing to unwravel a texturemap from the model - if one doesn't already exist? Even if it just makes a grid and maps each zone to a model face would simplify things.
2. paint texturemaps with images from external sources in a straightforward procedure? Like how we used to do textured faces in 3dobuilder perhaps, only it takes the pic and stretches/shrinks it to fit the mapped area. Heck, with a framework like that it probably would be easy to convert old 3do files to the s3o format.
These two things would surely save alot of time.
1. add an option in Upswing to unwravel a texturemap from the model - if one doesn't already exist? Even if it just makes a grid and maps each zone to a model face would simplify things.
2. paint texturemaps with images from external sources in a straightforward procedure? Like how we used to do textured faces in 3dobuilder perhaps, only it takes the pic and stretches/shrinks it to fit the mapped area. Heck, with a framework like that it probably would be easy to convert old 3do files to the s3o format.
These two things would surely save alot of time.
Last edited by MadRat on 20 Mar 2007, 13:28, edited 1 time in total.