CompuServe Thread

#Is it possible?

5 messages in this thread
#144574From: Martin EnthedJan 2, 1995 5:29 AM
Is it possible to write an AXP IPAS that saves another objects mesh information to disk? I would like to save the mesh made by SKIN so I can load it as an ordinary object. -M.E
#144595From: Jonas Ruikis [ADESK]Jan 2, 1995 10:21 AM
Hi Martin, << I would like to save the mesh made by SKIN so I can load it as an ordinary object. >> If you were writing the AXP, I imagine that you could write the stand-in object's normalized values out to disk at render time. You could then have a PXP, read this data later and create a permanent object for you. However, none of us have the SKIN source code, so there is no automatic method. jonas
#144605From: Martin EnthedJan 2, 1995 11:53 AM
>>If you were writing the AXP, I imagine that you could write the stand-in object's normalized values out to disk at render time.<< Will an object have the same internal name after being processed by SKIN, or any other AXP, so I can get it with EXP_SELECT_INPUT_OBJECT? Then there will be no problem at all!! -M.E
#144870From: Jonas Ruikis [ADESK]Jan 3, 1995 9:40 PM
<< Will an object have the same internal name after being processed by SKIN, or any other AXP, so I can get it with EXP_SELECT_INPUT_OBJECT? Then there will be no problem at all!! >> If I understand you correctly, you'd like to call EXP_SELECT_INPUT_OBJECT from an AXP that you write, that is guarenteed to be called *after* the SKIN_i.axp at render time and it would query SKIN's created object. I asked an Autodesk engineer and he did not think that this was possible. Have you gotten any results from your experimentation with this? curious_jonas[adesk]
#144889From: Martin EnthedJan 3, 1995 11:26 PM
<<If I understand you correctly, you'd like to call EXP_SELECT_INPUT_OBJECT from an AXP that you write, that is guarenteed to be called *after* the SKIN_i.axp at render time and it would query SKIN's created object.>> This is correct. If 3DS goes through the AXP's when rendering from the top downwards in the objectlist, as it does for Auto-reflect calculation,in the keyframer it will work. Then I can put my object with my AXP on it as a child to the skin object I want to output. Then I know this will be processed afterwards. If I can use "kxp_get_parent" from an AXP I wouldn't even need to know the name of the skined object. <<I asked an Autodesk engineer and he did not think that this was possible.>> I think I have read somewhere that the object made by an AXP has a totaly different name (by random) than the original object. If this is the fact it won't work as I need to no the name for "EXP_SELECT_INPUT_OBJECT". <<Have you gotten any results from your experimentation with this?>> I havn't started as I'm in the investigation state of this idea. [even more curious] -M.E