5,389
edits
User talk:Iritscen: Difference between revisions
→Importing from Blender: Wait, that one wasn't an interjection
(→Importing from Blender: making my (lack of) bold italics consistent, bringing back "interjection italics", replying) |
(→Importing from Blender: Wait, that one wasn't an interjection) |
||
| Line 152: | Line 152: | ||
::Here's the link to Iritscen's Griffin: http://www.sendspace.com/file/rl6zre Also, you can find my version of Griffin here: http://drop.io/EdT_OniFIles | ::Here's the link to Iritscen's Griffin: http://www.sendspace.com/file/rl6zre Also, you can find my version of Griffin here: http://drop.io/EdT_OniFIles | ||
::[[User:EdT|EdT]] 20:51, 2 June 2008 (CEST) | ::[[User:EdT|EdT]] 20:51, 2 June 2008 (CEST) | ||
::: | :::Thanks, Ed. Your TRBS is OK, I guess (as for the head mesh, that's a completely different story). The problematic .dae has been an opportunity to check out just what tool Iritscen is "forced" to work with. I'm definitely appalled at how much Blender sucks, from the confusing/confused design/philosophy to the online manual. In particular when it comes to coordinate systems and transformations, it's ''unspeakably'' clumsy. Of course, there are some decent workarounds (see 5-step instructions for fixing Griffin's head above), but that doesn't cover every real-world situation, and every such "exception" will be a little big nightmare. Maybe for HD modding or bastardizing the workflow won't be ''too'' lousy, but it will never ''soar'', that much is certain. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST) | ||
::::Yes, the design is crappy (but don't tell them that, they have blinders on and can't see the appalling stupidity of things like no copy/paste command). Yes, the wiki-manual is crappy. But I think that we are actually close to a perfectly serviceable workflow. I used AETools this morning to export Griffin from the .oni file that Ed has up on his drop.io page, and it looks correct in Blender. I still have to test what happens when I edit the file (thus saving it in the .blend format), then export it to .dae from Blender, then import it into a .oni using AETools. It may very well work. Don't nay-say so much, geyser. Griffin in specific has had issues that will not ever come up again in the future. I still have to discuss him here because I need to fix the model for further work going forward, but our discussion here about workflow is somewhat a separate topic because it assumes that the OniSplit export is not buggy, etc. That's okay, because the OS export isn't buggy anymore. --[[User:Iritscen|Iritscen]] 16:02, 3 June 2008 (CEST) | ::::Yes, the design is crappy (but don't tell them that, they have blinders on and can't see the appalling stupidity of things like no copy/paste command). Yes, the wiki-manual is crappy. But I think that we are actually close to a perfectly serviceable workflow. I used AETools this morning to export Griffin from the .oni file that Ed has up on his drop.io page, and it looks correct in Blender. I still have to test what happens when I edit the file (thus saving it in the .blend format), then export it to .dae from Blender, then import it into a .oni using AETools. It may very well work. Don't nay-say so much, geyser. Griffin in specific has had issues that will not ever come up again in the future. I still have to discuss him here because I need to fix the model for further work going forward, but our discussion here about workflow is somewhat a separate topic because it assumes that the OniSplit export is not buggy, etc. That's okay, because the OS export isn't buggy anymore. --[[User:Iritscen|Iritscen]] 16:02, 3 June 2008 (CEST) | ||
:::::Blender is irredeemable beyond any complaint to developers. But I'll help you out if you choose to stick with it. | :::::Blender is irredeemable beyond any complaint to developers. But I'll help you out if you choose to stick with it. | ||