Command line tool for 3do->s3o
Moderators: MR.D, Moderators
Command line tool for 3do->s3o
Does such a tool exist?
If so, what info is required by s3o that isnt in 3do? (like height, radius, etc)
If so, what info is required by s3o that isnt in 3do? (like height, radius, etc)
Re: Command line tool for 3do->s3o
The biggest difference is that s3o requires a uv map and a single texture.
Re: Command line tool for 3do->s3o
Dont forget to mention reflectivness
Mostly the diferences are UVmap, single texture and reflectivness, the rest is prety mutch the same, iirc.

Mostly the diferences are UVmap, single texture and reflectivness, the rest is prety mutch the same, iirc.
Re: Command line tool for 3do->s3o
texture2 can be omitted, if you're auto-converting a bunch of 3do you probably don't want one anyway?
Re: Command line tool for 3do->s3o
I know I need an UV map and a texture, and am prepared for it. But I still need to know if such a tool exists :D
I haz planses.
I haz planses.
Re: Command line tool for 3do->s3o
afaik, the only 3do -> s3o tool is Upspring.
Re: Command line tool for 3do->s3o
Can it be driven through the command line?
Re: Command line tool for 3do->s3o
nope but the source is available so you could grab the responsible code and turn it into a command line utility...
-
- Posts: 823
- Joined: 21 Oct 2008, 02:54
Re: Command line tool for 3do->s3o
If you did convert upspring into a command line. Please upload it for me!
Re: Command line tool for 3do->s3o
UpSpring can in fact be driven from the commandline via Lua.
The problem is it's undocumented. The syntax is:
upspring -run file.lua
Which brings up the next issue, what goes IN file.lua to perform a conversion? I don't know exactly but the lua functions are defined in the SWIG wrapper (swig/upspring_wrapper.cxx) so you could try:
-- load the model
model = Load3DO("path/to/model.3do")
-- convert from 3DO texture atlas
ConvertToS3O(model, "path/to/3DO_texture.bmp", texW, texH)
-- save the S3O version
success = SaveS3O(model, "path/to/model.s3o")
I don't think you can pass commandline options for the script so you may need an external script to modify the lua script for each of your models.
To pull this off you'll really need a copy of the UpSpring source code and a lot of patience but in theory it should be possible.
The problem is it's undocumented. The syntax is:
upspring -run file.lua
Which brings up the next issue, what goes IN file.lua to perform a conversion? I don't know exactly but the lua functions are defined in the SWIG wrapper (swig/upspring_wrapper.cxx) so you could try:
-- load the model
model = Load3DO("path/to/model.3do")
-- convert from 3DO texture atlas
ConvertToS3O(model, "path/to/3DO_texture.bmp", texW, texH)
-- save the S3O version
success = SaveS3O(model, "path/to/model.s3o")
I don't think you can pass commandline options for the script so you may need an external script to modify the lua script for each of your models.
To pull this off you'll really need a copy of the UpSpring source code and a lot of patience but in theory it should be possible.
Re: Command line tool for 3do->s3o
Thanks spliff! Thats exactly what I needed.
Igor! Hit the switch!
Igor! Hit the switch!
Re: Command line tool for 3do->s3o
What are you doing?
Re: Command line tool for 3do->s3o
Waking Spring up for the first time, obviously.
Re: Command line tool for 3do->s3o
I bet he is making one giant texture that has all the ota textures in it and then he converts all 3do to s3o's and uses that giant texture for all of the units :)
Then we can get rid of 3do forever! I had this idea once.
Then we can get rid of 3do forever! I had this idea once.
Last edited by Masse on 03 Sep 2010, 12:52, edited 1 time in total.
Re: Command line tool for 3do->s3o
Close, but no cookie. Its gonna be way better than that.
Re: Command line tool for 3do->s3o
You also improve the textures?Beherith wrote:Close, but no cookie. Its gonna be way better than that.