I noticed from the Exocortex instructions that it has to do with ICE optimizations, the trick with forcing evaluation by displaying the attribute should work for the built-in exporter as well I guess? Thing is, I wanted to export a specific value per point, but I'm not re-using the value within ICE, so that's why they were ignored. At least there's a way to force the export, so it should be fine!
On Tue, May 6, 2014 at 4:06 AM, Ho Chung Nguyen <[email protected] > wrote: > Those attributes were not found or defined on the exported objects. > > It's not a problem if you don't use those attributes in your scene. > > The default list is comprehensive, including necessary attributes for the > built-in renderers and sample scenes. Therefore you sometimes gets these > warning if you don't use as many attributes. > Just remove those attributes from the list in the export dialogue if you > don't want to see the warnings. > > > Sent > > > On May 6, 2014, at 1:22 AM, "Arvid Björn" <[email protected]> wrote: > > > > Hey folks, > > > > I'm trying to export an Alembic with some custom properties, Exocortex > Crate doesn't seem to export anything other than the usual attributes, and > there are no options for it. Then I noticed that the new built-in exporter > has options for this, but when I export, I get this for just about every > attribute in the list: > > > > // WARNING : Attribute not exported: AngularVelocity > > // WARNING : Attribute not exported: ColorAlongStrands > > // WARNING : Attribute not exported: MaterialID > > // WARNING : Attribute not exported: Materials > > etc...... > > > > What's up what that? There are not clues as to why they aren't exported. > Is there anything I need to do to get this to work? > > > > Cheers! >
