KeyShot Forum

Technical discussions => Data Import => Topic started by: JAKiii on June 22, 2010, 10:40:49 am

Title: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: JAKiii on June 22, 2010, 10:40:49 am
10. OBJ files from Alias don't group correctly.
9. STEP files from Alias don't group correctly.
8. IGES files from Alias require layer separation of material in Alias, an undesirable workflow.
7. All other file types fail for one reason or another.
6. Car designers use Alias.
5. It's easier.
4. It's easier.
3. It's easier.
2. It's easier.
1. Hypershot 1.x had an Alias translator (beta) that worked great.
Title: Re: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: guest84672 on June 22, 2010, 12:38:34 pm
It is on our list of things to do.
Title: Re: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: JAKiii on July 08, 2010, 10:58:17 am
Seriously, I really need this.
Title: Re: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: joejoearmani on July 18, 2010, 11:16:54 pm
yup, I am an Alias user too and I totally agree! Hope to see an Alias translator some time soon.
Title: Re: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: tamm0rine on July 20, 2010, 10:54:23 am
+1 :)
Title: Re: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: ptbd on July 21, 2010, 09:04:42 am
Alias 2011 .iges translator has a bug relating to layers.
It also has a major bug that makes HUGE .iges files. If you are using any imported .iges data, then export as .iges, the file size will grow like 10 times. So, if you have a part that is made into a solid in another software, then reimported into alias, it pretty much becomes a huge pain.
Title: Re: Alias Translator - 10 Reasons KeyShot Needs One!
Post by: Filenty on July 24, 2010, 03:38:26 pm
+1