Hi Sergio,
Thank you for the details!! I looked through the SR3D files (I saw all of the patch files) and have thought a bit about the mathematics of connections; one thing is not clear to me.
For the axle and peghole, does your system know how _long_ the axle is? For example, is there a requirement that the length of the vector [ox oy oz] be the length of the axle?
I do have another question: I noticed the "tire manager" file that appears to associate wheels with tires. Does SR3D know the correct position for the tires on the wheels? Or does this come from the part connection data?
I like the idea of exporting the connection DB into files that could then become the beginning of a shared connection DB. And I am very glad that your system leverages the part-subpart relationship; without this managing connections would be impossible, I think.
cheers
Ben
Thank you for the details!! I looked through the SR3D files (I saw all of the patch files) and have thought a bit about the mathematics of connections; one thing is not clear to me.
For the axle and peghole, does your system know how _long_ the axle is? For example, is there a requirement that the length of the vector [ox oy oz] be the length of the axle?
I do have another question: I noticed the "tire manager" file that appears to associate wheels with tires. Does SR3D know the correct position for the tires on the wheels? Or does this come from the part connection data?
I like the idea of exporting the connection DB into files that could then become the beginning of a shared connection DB. And I am very glad that your system leverages the part-subpart relationship; without this managing connections would be impossible, I think.
cheers
Ben