My experiences with PB3D quickly failed. :( Obviously the current workflow and stability around PB3D leaves a lot to be desired - hopefully this will be sorted soon.
Coupled to this is the fact that any output from PB3D won't, currently, directly sit with Away3D 4. The current framework does a lot under the hud in management of AGAL code and especially registers used in the code. As PB3D will generate it's own code, it will need to be further translated into Away or somehow implemented in a different way. As such, I thought I'd go straight for AGAL - which wasn't too bad really, in the end. Too be honest, though, I didn't really give PB3D a good enough tryout - maybe I should next time ;) Greg
