Does anyone have issues with printing Aerial Imagery from a .pset?

Question

I have aerial imagery referenced into Model A in file A.dgn. 
 I reference Model A from file A.dgn into Model B in file B.dgn (Aerial Imagery Shows up). 
 I reference Model B in file B.dgn into Sheet C in file B.dgn (Nesting turned on, 99). Aerial imagery shows up on the sheet. 
 If I use ctrl+P to see a print preview, I can see the imagery. Using ctrl+P, I can print just one sheet and the aerial works properly. If I move the files into a .pset to use, the results are hit or miss. 
 I've had this issue for the past few months where when I use a .pset (that previously worked perfectly, all lines and aerial imagery printed properly) it would sometimes not work and print just the lines referenced in, but not the aerial imagery. In the cases of the aerial imagery not printing, the lines that are referenced in always print properly. Unsure what could be causing the same .pset to print differently on different days. 
 If this is relevant information, I can always tell when a print is going to come out with no aerial imagery because the print loads VERY quick. 
 Please let me know if you need more info. or have questions, thanks!

Lorys · Answer

what version of mst are you using? 
 does it fail on all psets and all imagery or only this pset? 
 We have found that sometimes psets get corrupted or stop working properly... our experience is to delete the pset and remake the pset.. 
 personally I prefer V8i ss10 with batchplt.ma it seems to be more robust, much faster and you can save the print job similar to the pset...but unfortunately its not available option in CE.

MaryB · Answer

I deal with this. I believe it has to do with the time it takes to load the aerial imagery when running the PSET. 
 As I understand it, print organizer opens its own, somewhat background, MicroStation process. When it is loading drawings, it may be printing before the entire aerial image loads. This is my working explanation why aerial image printing is unpredicatable - it depends on how much data loads up before printing happens. Sometimes all of it comes in, and sometimes it doesn't, and it's rarely ever the same portion of the image every time. 
 One of the things that I have found to help is to back the Raster Quality WAY down to about 15. This still produces a good enough result for most applications, and it seems to eliminate most (but not always all) of the image problems.