CompuServe Messages

I am not with the Yost Group, but as a Forum Assistant hopefully I can answer some of your questions and save Gary and Co. some time… (My answers are based upon my impressions from the Autodesk booth at Siggraph, and may not be complete or fully accurate.) 1 & 2: <Acad transfers> I don't know. 3. <parametric booleans> I believe that was discussed at Siggraph as being just another object modifier in the stack. 4. <non-parametric imported objects> Set your message counter back a couple of days . There was a thread discussing this. Basically, the imported mesh becomes the starting point of the stack and all modifications in the stack act on it. Regarding the face count, I doubt the base object would have parameters to allow that. (It would be more-or-less a "dumb" mesh.) 5. <ACAD style blocks> At Siggraph they briefly discussed new options for instance copies. It looks like there will be several ways to copy an object and have updates affect all or certain copies. 6 & 7. <mapping> I haven't heard any discussion yet. 8. <sound properties> Cool idea. From what I saw, sound is present as mainly a reference on which to base your animation. Given the concept of the core-component-plug-ins though, I can't see why a sound generator couldn't be built. AVI and WAV technology is heavily used and documented in the Windows world. 9. <ray-trace> I haven't heard any announcements about the renderer. 10. <snap to 2D objects> Good Question! (no idea… <g>) 11. <2D primitives> From the Siggraph demonstration, it appears that all 2D shapes are just another step in the "stack". They all seem to be spline-based, and modifications to the base shape will effect a change through the whole stack. 12. <mesh distortions ala Bones> Don't know. 13. <"magnet" like stretching> Don't know for certain, but the parametric mesh modifiers and "space-warps" would appear to come pretty close. 14. < other CAD/drawing packages> Dunno. 15. <ref-maps> Dunno. 16. <developer stuff> It is my understanding that the Developer Kit will be part of the program, shipping to all customers. Microsoft Visual C++ will be the programming language required (I don't have version #'s noted). PharLap and Watcom are out of the loop. Hope this helps. – Dave