It should definately be faster - most Vicky3 issues (with Poser5) seem to be cured by installing her directly in the Poser5 Runtim so that people don't get huge delays. I'm not aware of the algorythm being used at present (it isn't the original unpublished algorythm) for searching the runtim folders, but let's imagine the following: A charatcer in a PZ3 file (in "My Documents" folder) that has several materials that point to a "relative" texture address of "Runtime:Textures:My New Textures:V3HeadFishTex" Let's assume just 3 runtimes... Poser 5 Poser 4 Victoria3 ONE way for the program to search for the texture would be to check the folowing locations in order: My Documents Poser 5:Runtime:Textures:My New Textures:V3HeadFishTex Poser 4:Runtime:Textures:My New Textures:V3HeadFishTex Victoria3:Runtime:Textures:My New Textures:V3HeadFishTex Possibly searching all other subfolders of the various "Textures" folders in each Runtime too (either as it does that Runtime, or at the end if all the "exact" relative addresses fail). That's a fair bit of searching. Withj all programming there's a balance between speed and ease-of-use. This function has been "adjusted" towards what people have requested once so far - but a number f issues are outstanding. For example, if you press cancel that's probably interpreted as "Cancel" for that search. The next group that needs that material is likely to search for it again... unless code is in place to remember "cancelled" texture searches. ...and so on and so forth. But, fairly blatantly, if you HAVE only 1 runtime then it'll be faster because in the case of missing textures there'll be less work to do. If you have 7 Runtimes but think you're only using 2 at any given time then I suggest that while you INTEND to only use 2, any missing textures or geometry will likely cause all 7 Runtimes to be searched. Cheers, Cliff PS SR3 pulled a nasty on me last night - about 30 frames into a 141 frame animation it started rendering blank, black bitmaps instead of the glorious groundbreaking animation I thought it'd finished. It'd be rather nice if, after rendering an animation, Poser didn't auto-close the last frame - to give an indication of what it had rendered.