ati broke something very similiar in their drivers around 10.3.2

i was tracking the seeds and was in contact with an ati engineer trying to get the bug fixed.
i just about got it fixed in time.
i wasnt tracking 10.3.4 i was on the road.
i didnt expect it to get broken again - but these things happen.

to try and increase performance - i use newer features - these newer features arent quite stable - i hold off until i think they are stable - sometimes not long enough.