site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com It comes down to being able to recreate the scene in our own code, of course. Since we can't guarantee that our host has 3D capabilities, many of our 3D plug-ins offer a camera and a few directional lights. Therefore, if we don't get all of the above (say, just cameras), we'd still be ok - just not as functional as our AE counterparts (how's that for incentive). We like getting access to a 3D Layer's transform because we offer the ability to place our 3D objects at the same location/orientation as another object in the system. This lets the user animate a plane using the host's animation system and then "replace" that plane with one of our 3D objects. With Motion and FCP's realtime interaction, we'd love to have access to a layer's 3D info. Thanks a lot. Matt Rhodes Zaxwerks, Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... So, here's an open question to plug-in developers, to put this forum vehicle to the test... Of all of these concepts (camera matrix, focal length, lighting positions and properties, layer matrices, etc.), what would be the bare minimum feature set you would need in an API in order to do something interesting with 3D? What would you need in order to do more advanced 3D effects? For us (Zaxwerks), a minimum would be: - Camera - Transform matrix - Focal length/aperture/field of view (enough for lens definition) - Lights - Type (spot, point, etc.) - Color/intensity - Any other light-specific parameters (cone angle, falloff, shadow- values, etc.) - 3D Layers - Transform matrix - Size (width/height) - Layer Name or other way for a user to identify a particular 3D layer to us This email sent to site_archiver@lists.apple.com