Shadowspawn on 27/4/2005 at 16:39
I've finally got a version of a TIM to .E format converter working well enough to let you folks play with it. You can find it on my web site (see sig) under the Tools page.
It's a command line tool, so you need to run it in a command prompt window. I'm working on a nice GUI version, but GUIs take more time to build. The ZIP file is just the executable and a little Readme file.
NOTE: I convert the objects using the existing scaling, so in most 3D editors, the objects will be HUGE. You'll need to scale them appropriately.
I don't do anything with converting textures, so you'll have to dig them out yourself and convert them into something compatible with your 3D editor. When I release the GUI version, it will automatically (if you want) extract the textures and convert them to a selected format.
I'm working on the reverse translation, from 3DS into TIM format, but it'll take more time.
If you guys run into bugs, problems, things that won't convert properly, etc - post the problem here or email me. Let me know the object that's giving you trouble and I'll dig into it and find out what's wrong.
Dark Arrow on 27/4/2005 at 18:00
ALL HAIL THE GREAT SHADOWSPAWN!!! :D
More praise when you do 3dstoTim...
Renzatic on 27/4/2005 at 18:02
Excellent! :D
bukary on 27/4/2005 at 18:47
Great! I'll try it tomorrow... :thumb:
bukary on 27/4/2005 at 19:21
I converted .tim file to .e, then I converted .e to .3ds. But when I try to import this file (.3ds), max gives me message: "Improper File Format". :confused:
BTW, I tried this with 3 different .tim files... Does this converter work for everyone?
I wonder what I am doing wrong...
Shadowspawn on 27/4/2005 at 20:28
In the past, I've had problems importing my 3DS files into MAX. I've never been able to figure out why, but I guess I'll need to figure it out before the nice GUI version comes out.
A friend of mine has 3DS Max, so I'll try it out on his computer and I'll see why it complains.
OK, it fails on his machine also, but after converting it through Accutrans or Deep Exploration, it works.
OK, I've got both versions of the 3DS file, mine and the converted one. I'll dump them and find out what's wrong with mine. Look for an update in a few days.
In the meantime, use a converter from my 3DS file to another one and try to import it.
nomad of the pacific on 27/4/2005 at 21:32
Got happy feet! Gotta do my Snoopy dance! :cheeky:
Thanks Shadowspawn! :thumb:
ascottk on 28/4/2005 at 03:18
TimtoE & Eto3DS works well with Blender (along with the import-3ds python script). Now if I only knew how to use Blender . . . sidenote: does anyone know any utilities (aside from the expensive ones like Maya or ActorX) that works with UnrealEd skeletal meshes?
Shadowspawn on 28/4/2005 at 03:41
I think we'll eventually get MilkShape working with them, but it'll be a few more months.
I'm willing to eventually build plug-ins to any 3D editor, provided I can get a copy to test with, and get whatever developer stuff I need (SDK) without spending much money.
Durinda D'Bry on 28/4/2005 at 07:22
Shadowspawn :thumb:
