User talk:Iritscen: Difference between revisions

Line 70: Line 70:
This is the place where EdT tells me what was wrong with that Griffin model I gave him. :-) What did you have to do to get it imported? (I know you already told me some of this, but let's state it here to lay the groundwork for the discussion.)
This is the place where EdT tells me what was wrong with that Griffin model I gave him. :-) What did you have to do to get it imported? (I know you already told me some of this, but let's state it here to lay the groundwork for the discussion.)
:--[[User:Iritscen|Iritscen]] 15:59, 2 June 2008 (CEST)
:--[[User:Iritscen|Iritscen]] 15:59, 2 June 2008 (CEST)
::General note 1: please provide links to every file you "cite" as an example (I'll mark them in '''''bold italics'''''), because "I extracted Motoko from the files you posted" or "geyser's earlier copy had triangles connected" just isn't informative enough. "Help us help you help us all."
::General note 2: please stop guessing and start looking for systematic ways of investigating problems, because stuff like
:::"Its hard to say where the problem is, it could be Cheetah3D or it could be FBXConverter. All I know, is that the model's triangles are disconnected once I have it in Cheetah3D"
::and
:::"Hmm, I guess Blender's exported DAE might have had a problem that Cheetah only noticed upon exporting; that almost sounds more like a Cheetah problem, though. Maybe it's both program's faults, technically."
::(also marked in '''''bold italics''''') is just not good for you.
:::[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)


Where do I start? :-)
Where do I start? :-)
Line 79: Line 87:
::Interesting. Griffin was always standing up, but when I extracted Motoko from the files you posted, and brought her into Blender, she had her legs behind her head! (Get your mind out of the gutter!) All her limbs were pointing up above her head. Have you seen that happen? What does that indicate? --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::Interesting. Griffin was always standing up, but when I extracted Motoko from the files you posted, and brought her into Blender, she had her legs behind her head! (Get your mind out of the gutter!) All her limbs were pointing up above her head. Have you seen that happen? What does that indicate? --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::That's how the body looks like when the rotation of all the body parts is set to 0 on the x,y,z axis, also this is known as the default orientation. I believe that when a body part is selected and you type "n" a window appears showing the properties such as position, scale, rotation.  [[User:EdT|EdT]]
:::That's how the body looks like when the rotation of all the body parts is set to 0 on the x,y,z axis, also this is known as the default orientation. I believe that when a body part is selected and you type "n" a window appears showing the properties such as position, scale, rotation.  [[User:EdT|EdT]]
:::For further reference, see [[TRTA|HERE]] and [[OBD:TRAM/raw0x34#Origin_and_direction_of_the_angles|HERE]]. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
::::Okay, I thought that might be what zero rotation looks like. Now, are you saying that if a model imports like that, I shouldn't rotate the parts to more normal angles? Because I did that for Motoko. Did that cause a problem when you went to import her into Oni? --[[User:Iritscen|Iritscen]] 22:06, 2 June 2008 (CEST)
::::Okay, I thought that might be what zero rotation looks like. Now, are you saying that if a model imports like that, I shouldn't rotate the parts to more normal angles? Because I did that for Motoko. Did that cause a problem when you went to import her into Oni? --[[User:Iritscen|Iritscen]] 22:06, 2 June 2008 (CEST)
:::::Yes, so I just copied the head from your files and pasted into my original one. Also, the head's center point was off, so I had to correct it. [[User:EdT|EdT]]
:::::Yes, so I just copied the head from your files and pasted into my original one. Also, the head's center point was off, so I had to correct it. [[User:EdT|EdT]]
:::::Actually, everything but Griffin's head is untouched ''and 100% correct'', so you can work with Iritscen's file, without pasting the head elsewhere. [[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:Make the changes.
:Make the changes.
:Export from Blender, Collada 1.4, options: triangles, disable physics, current scene. (I'm doing this from memory, I do not have access to Blender at work. will correct if necessary)
:Export from Blender, Collada 1.4, options: triangles, disable physics, current scene. (I'm doing this from memory, I do not have access to Blender at work. will correct if necessary)
Line 88: Line 98:
:Each body part has a center point, when exporting from Oni as Collada, these center points are at the correct location.  However, if new parts are added, then the center point must be set. To set the center point, position the cursor at the correct location on the body part, you will need to adjust it on all 3 axis. Then go to the menu Object: Transform: Set to cursor. (from memory)
:Each body part has a center point, when exporting from Oni as Collada, these center points are at the correct location.  However, if new parts are added, then the center point must be set. To set the center point, position the cursor at the correct location on the body part, you will need to adjust it on all 3 axis. Then go to the menu Object: Transform: Set to cursor. (from memory)
:When replacing a body part, its important that its rotation matches the original part.  Also, the name must be exactly as the one replaced. Finally, the parent/child relationship must be re-established.
:When replacing a body part, its important that its rotation matches the original part.  Also, the name must be exactly as the one replaced. Finally, the parent/child relationship must be re-established.
 
::''The notion of rotation matching is a bit fuzzy here, there, and everywhere. You're not making it clear what to do about rotations that don't match. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)''
What went wrong with Griffin?
What went wrong with Griffin?
:It appears there is an additional object connected to the new head, which needs to be deleted.  The new head needs to be named correctly, it needs to be attached to the neck (parent/child). Finally the scale/rotation needs to match the previous head.
:It appears there is an additional object connected to the new head, which needs to be deleted.  The new head needs to be named correctly, it needs to be attached to the neck (parent/child). Finally the scale/rotation needs to match the previous head.
::I did in fact forget to establish a link to the new head (I realized after I had sent it to you). I will have to examine the issue of scale/rotation to make sure it is set properly in Griffin, I don't know that part of the program yet. I can probably figure that out. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::I did in fact forget to establish a link to the new head (I realized after I had sent it to you). I will have to examine the issue of scale/rotation to make sure it is set properly in Griffin, I don't know that part of the program yet. I can probably figure that out. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::The scaling is fine. As for the rotation, the head is supposed to be aligned with the neck. So the only things that need to be done (apart from deleting the garbage object) are as follows: rename to "head"; reparent to "neck"; move/rotate into place; set center from cursor; "Object|Clear/Apply|Apply Scale/Rotation to ObData". --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:Perhaps, since I was working with the .dae version, and not the original Blender file, I was not able to export to Collada, it kept failing on me. Not sure why...
:Perhaps, since I was working with the .dae version, and not the original Blender file, I was not able to export to Collada, it kept failing on me. Not sure why...
::Afraid you lost me here. DAE *is* Collada, but you said you couldn't export it to Collada.... --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::Afraid you lost me here. DAE *is* Collada, but you said you couldn't export it to Collada.... --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::All I know is that after importing your .dae file, I could not export it out as .dae. [[User:EdT|EdT]]
:::All I know is that after importing your .dae file, I could not export it out as .dae. [[User:EdT|EdT]]
::::Hmm, I guess Blender's exported DAE might have had a problem that Cheetah only noticed upon exporting; that almost sounds more like a Cheetah problem, though. Maybe it's both program's faults, technically. Well, in the future I will send you the .blend file if I need help, but hopefully I can make my own imports from now on. --[[User:Iritscen|Iritscen]] 22:06, 2 June 2008 (CEST)
::::'''''Hmm, I guess Blender's exported DAE might have had a problem that Cheetah only noticed upon exporting; that almost sounds more like a Cheetah problem, though. Maybe it's both program's faults, technically.''''' Well, in the future I will send you the .blend file if I need help, but hopefully I can make my own imports from now on. --[[User:Iritscen|Iritscen]] 22:06, 2 June 2008 (CEST)
:::::Actually, the exporting error came from Blender itself, you can try it yourself.  Import the .dae file you sent me into Blender, now try to export that file as Collada. [[User:EdT|EdT]]
:::::Actually, the exporting error came from Blender itself, you can try it yourself.  Import the .dae file you sent me into Blender, now try to export that file as Collada. [[User:EdT|EdT]]
 
::::::Just to clear things up: Iritscen, Ed's DAE->DAE problem has ''nothing'' to do with Cheetah3D. He's just importing your .dae into Blender and trying to export it as .dae from Blender afterwards. I'm not sure why he's having trouble doing so, because for me that same operation works fine.
::::::Still, I'd have a piece of advice as for exporting COLLADA from Blender: disable physics, use ''relative'' texture paths, ''and'' export selection only (select all body parts before exporting). The latter is to avoid accumulating layers of irrelevant and confusing metadata in the COLLADA file format.
:::::::[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:What did I do? I used Cheetah3D.  I exported ONCCgriffin_generic as Collada, used FBXConverter to convert the file to .fbx.  I also converted your new model to .fbx.  I then copied the new griffin head to the griffin_generic fbx file, replaced the original head, set the correct rotation and parent/child relationship. Exported it out as .fbx, converted it to .dae using FBXConverter, then imported into Oni.  Also, regarding the triangles not being connected in my model, I did not Optimize the model in Cheetah3D before exporting.  
:What did I do? I used Cheetah3D.  I exported ONCCgriffin_generic as Collada, used FBXConverter to convert the file to .fbx.  I also converted your new model to .fbx.  I then copied the new griffin head to the griffin_generic fbx file, replaced the original head, set the correct rotation and parent/child relationship. Exported it out as .fbx, converted it to .dae using FBXConverter, then imported into Oni.  Also, regarding the triangles not being connected in my model, I did not Optimize the model in Cheetah3D before exporting.  


Line 103: Line 116:
::When you say you did not optimize the model... was that supposed to connect the triangles? Does Cheetah otherwise disconnect the triangles? That would be very odd. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::When you say you did not optimize the model... was that supposed to connect the triangles? Does Cheetah otherwise disconnect the triangles? That would be very odd. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::Optimize in Cheetah3D connects the triangles, and a couple of others things, I don't remember right now. [[User:EdT|EdT]]
:::Optimize in Cheetah3D connects the triangles, and a couple of others things, I don't remember right now. [[User:EdT|EdT]]
::::See, I just don't get that, because geyser's earlier copy had triangles connected. It concerns me that Cheetah would disconnect the triangles unless you specifically tell it not to. When you're working with the file in Cheetah, are the triangles already disconnected, or is that only happening when it exports? --[[User:Iritscen|Iritscen]] 22:06, 2 June 2008 (CEST)
::::See, I just don't get that, because '''''geyser's earlier copy''''' had triangles connected. It concerns me that Cheetah would disconnect the triangles unless you specifically tell it not to. When you're working with the file in Cheetah, are the triangles already disconnected, or is that only happening when it exports? --[[User:Iritscen|Iritscen]] 22:06, 2 June 2008 (CEST)
:::::What can I say? I didn't know there was a problem, until you pointed it out. Its hard to say where the problem is, it could be Cheetah3D or it could be FBXConverter.  All I know, is that the model's triangles are disconnected once I have it in Cheetah3D [[User:EdT|EdT]]
:::::What can I say? I didn't know there was a problem, until you pointed it out. '''''Its hard to say where the problem is, it could be Cheetah3D or it could be FBXConverter.  All I know, is that the model's triangles are disconnected once I have it in Cheetah3D''''' [[User:EdT|EdT]]
 
::::::You could shed some light on this mystery by uploading the FBX file output by FBXConverter. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:'''it's important that its rotation matches the original part''' Conceptually, this has to do with the "center point": you have to define not only a position for it, but also a rotation, and thinking of it as a "point" can be misleading. I have no idea how Blender handles this exactly, but I'd be surprised if it was working with ill-defined frames of reference. Therefore the "center point" mentioned by Ed ''must'' have an adjustable orientation property.
:'''it's important that its rotation matches the original part''' Conceptually, this has to do with the "center point": you have to define not only a position for it, but also a rotation, and thinking of it as a "point" can be misleading. I have no idea how Blender handles this exactly, but I'd be surprised if it was working with ill-defined frames of reference. Therefore the "center point" mentioned by Ed ''must'' have an adjustable orientation property.
::Hmm, not sure I get this, but do I need to get it? As long as I alter polys and don't add new parts (which, yes, I did do for Griffin, but only to get his new head on the old body that was un-importable), do I need to worry about center points and rotations? As long as I don't change either of those? --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::Hmm, not sure I get this, but do I need to get it? As long as I alter polys and don't add new parts (which, yes, I did do for Griffin, but only to get his new head on the old body that was un-importable), do I need to worry about center points and rotations? As long as I don't change either of those? --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::That is correct [[User:EdT|EdT]]
:::That is correct [[User:EdT|EdT]]
:::'''do I need to get it?''' That's entirely up to you. Stuff like "bastardizing" can indeed be done without "worrying about center points and rotations". But without a solid notion of the "reference frames" (a.k.a. "systems of coordinates") involved, a major screw-up is only a matter of time. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:::'''only to get his new head on the old body that was un-importable''' Er? I'm confused again: what old body are we talking about, how was it un-importable, and how does this all fit in with you eventually combining that supposedly un-importable body with the new head? --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:'''What went wrong with Griffin?''' If that's of any help, you can let ''me'' (or Neo) try and import him ''any time at all''. When in trouble, there's nothing wrong with asking those familiar with OniSplit and/or the COLLADA format to have a look. What kind of masochist are you? If you're scared of me, try and "use" Neo. He may not help you all the way out, but he won't bite, that's for sure.
:'''What went wrong with Griffin?''' If that's of any help, you can let ''me'' (or Neo) try and import him ''any time at all''. When in trouble, there's nothing wrong with asking those familiar with OniSplit and/or the COLLADA format to have a look. What kind of masochist are you? If you're scared of me, try and "use" Neo. He may not help you all the way out, but he won't bite, that's for sure.
:: *shrug* Ed just seemed to be the person to ask. We're using the same programs, and he had clear experience in importing models already. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:: *shrug* Ed just seemed to be the person to ask. We're using the same programs, and he had clear experience in importing models already. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::From what I have seen, Ed was quick to turn away from Blender and has since been working with Cheetah3D. No to say that he can't be of any help at all, but when it comes to Blender's COLLADA plugin and possible issues with ''that'', the right person to ask is Neo, who has taken the time to look at the plugin's (buggy) source to make sure Blender is decently compatible with the flavor of COLLADA used by OniSplit. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
:Oh, and I'm also very confused about '''work on Griffin began so long ago that OniSplit had some model exporting issues, which are now a part of the model, so the model is not able to be imported as is''' ... No bug report at all? Just what "issues" could we be talking about? Are those ''assumptions'', maybe? Well?
:Oh, and I'm also very confused about '''work on Griffin began so long ago that OniSplit had some model exporting issues, which are now a part of the model, so the model is not able to be imported as is''' ... No bug report at all? Just what "issues" could we be talking about? Are those ''assumptions'', maybe? Well?
::[[User:Geyser|geyser]] 20:16, 2 June 2008 (CEST)
::[[User:Geyser|geyser]] 20:16, 2 June 2008 (CEST)
::The reason I didn't attempt a bug report was that I suspected the problems were extensive (wrong part names, for one thing, but probably more), and it was pointless to analyze the Griffin model I was working with as long as the head could be stuck on a new export of the original body. I knew I was going to do that so I never asked anyone to analyze the body I was working with (after all, only the head was changed and only the head mattered). Then, I *did* ask for a bug report from Ed by sending him my model, since I didn't know enough to find those bugs myself. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::The reason I didn't attempt a bug report was that I suspected the problems were extensive (wrong part names, for one thing, but probably more), and it was pointless to analyze the Griffin model I was working with as long as the head could be stuck on a new export of the original body. I knew I was going to do that so I never asked anyone to analyze the body I was working with (after all, only the head was changed and only the head mattered). Then, I *did* ask for a bug report from Ed by sending him my model, since I didn't know enough to find those bugs myself. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
 
:::Meta-sigh. There is ''nothing'' wrong with the Griffin model you were working on: it's ''100% consistent'' with "a new export of the original body". It is ''not'' corrupt in ''any'' way, except for the hierarchy of the head, and that one can be fixed in-place without sticking anything anywhere.
:::Either way, in the future it'll be great if you don't casually attribute non-existing "issues" to OniSplit as if that was a fact. We have respect for user error; in return, please ''at least'' give the benefit of the doubt to the tools at your disposal (it's about ''your credibility'', not about offense).
::::--[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)
::geyser, sorry my terminology is not correct.  What I called "center point" is the point where the body part will rotate around. I used "Rotation" as the orientation of the body part in 3D space.  When the rotation for all the body parts is 0 for x,y,z, then the pose of the model is the default orientation.  But since the pose in Blender is a standing pose, the rotation of the body parts is not 0,0,0. So if you replaced the head, with one that had a different rotation (even though it looked the same), the head will appear wrong in Oni.
::geyser, sorry my terminology is not correct.  What I called "center point" is the point where the body part will rotate around. I used "Rotation" as the orientation of the body part in 3D space.  When the rotation for all the body parts is 0 for x,y,z, then the pose of the model is the default orientation.  But since the pose in Blender is a standing pose, the rotation of the body parts is not 0,0,0. So if you replaced the head, with one that had a different rotation (even though it looked the same), the head will appear wrong in Oni.
 
:::''That's where the catch is, Ed: are you sure you understand how it is possible that 2 heads have "different rotations" even though they "look the same"? And in what sense is the rotation of the body parts not 0,0,0 for a standing pose? Think "local reference". --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)''
:::''Blender designers do a great job at confusing people, in the way only global orientations can be seen and edited, but it's the ''local reference'' of each body part that matters, and the ''local'' orientations of most body parts (e.g., the head) are 0,0,0. --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)''
::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
 
:::''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)''
::[[User:EdT|EdT]] 20:51, 2 June 2008 (CEST)
::[[User:EdT|EdT]] 20:51, 2 June 2008 (CEST)
::P.S. to geyser: I did offer these files to you by saying you could ask Ed for them... so, you can't accuse me of withholding them from you since I only just made them available to anyone at all, and you were included in that offer. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
::P.S. to geyser: I did offer these files to you by saying you could ask Ed for them... so, you can't accuse me of withholding them from you since I only just made them available to anyone at all, and you were included in that offer. --[[User:Iritscen|Iritscen]] 21:08, 2 June 2008 (CEST)
:::I wasn't accusing anyone of anything right there, but you have to admit that "oh, just go and ask Ed if you really wanna have a look at it, but I really wouldn't bother if I were you" is not the same as "here it is". Also, it's not just about "offering" stuff to ''me''; this is typically the case where I'd address ''Neo'' directly, at the first sign of trouble... "if I were you". --[[User:Geyser|geyser]] 07:01, 3 June 2008 (CEST)