Exporting projects that reference images in other projects

Question

Hello, all. I'm wondering if anyone out there has had luck exporting projects that reference images in another project. I've just given this a try, and I get empty images (dotted gray outlines that can't be multi-selected and can't be "managed" as referenced files, even though it knows where the original file should be).
Here's how I have things set up:
1. main project with referenced images
2. secondary project with an album that references images in the main project (secondary project shows 0 images, but album in secondary project shows N images)
I export the secondary project, and import it into another Aperture instance. All images show up as dotted outlines.
Furthermore, if I go into list view, the Activity Monitor does something bizarre. It shows the # thumbnails remaining as a moving target. See the video below for an example.
Any help would be greatly appreciated. Thank you!
Screen captures:
Missing images as dotted outlines:
http://echeng.com/temp/aperture-missing-images.png
Small video of thumbnail creating bug:
http://echeng.com/temp/aperture-thumbnail-bug.mov

Answer 1

I do this sort of thing constantly and things a whole lot more complicated. It works fine on all three of my laptops and my macpro. I actually just tried to simulate the exact conditions you describe and I will tell you what happened.
1)Create new empty project in library A called "export"
2)Create new empty album in that project.
3)Dragged multiple images from different projects (all referenced) into that new album.
4)Used file->export project with the consolidate images checked. Imported that project into a new/different library.
All of the images showed up and they all showed up as managed masters as expected. So I then relocated the masters from that project and did the same thing in reverse, back to the old library. I ended up with another project called "export (1)" with all of the images referenced and having nothing to do with the original project or the original referenced masters - as expected.
I did the testing not to figure it out but to validate that nothing had changed or broken since the last update.
You are either not doing what you think you are doing or your library/library is forked - you may want to try a rebuild or just create a brand new set of libraries and try to validate that it will work with a brand new set of libraries to try to isolate the issue to 1 - your existing libraries or 2 - your installation.
RB