Thanks Seeadler, I think this relates to the same bug reported to me about 2-3 months ago via another forum. I will test this scenario in my local build when I can, but I think it is fixed already for next release (whenever that is!?). Unfortunately I'm horribly tied up IRL right now. Haven't touched S3D since January, my goals for final release have been postponed, and postponed... and postponed... Anyway, you get it...
But, at least there's a positive note to add that things are somewhat stabilizing so hopefully in some weeks...
